Networker

Re: [Networker] Backups not reported in MMINFO

2005-10-05 12:04:37
Subject: Re: [Networker] Backups not reported in MMINFO
From: Tim Mooney <mooney AT DOGBERT.CC.NDSU.NODAK DOT EDU>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Wed, 5 Oct 2005 10:56:24 -0500
In regard to: [Networker] Backups not reported in MMINFO, Steve Law said...:

One of the servers backs up fine according to the details in the group AND
according to the Volume entry when I click on it, but not in the MMINFO
report.

What about when you check the "Indexes" for that client, in the GUI.  Is there
anything there?

This includes both a flat-file and SQL db backup. As I use mminfo
every morning to collate stats and confirm all's gone well, this is a bit of
a pain.

Why would this one server not appear in mminfo output? I've tried to force
it with an MMINFO -T "Last 1 Day" -c server.uk.ourcompany , but nothing's
found.

I'm assuming you've verified that the pool this client is writing its
data to has "Store Index Entries" set to "yes", and that the (hidden)
attribute "Index path" for this client hasn't been pointed somewhere
unexpected.

I had a similar problem happen once at our site, and it took quite a while
to figure out what was going on.  In my case, the problem was happening for a
multi-homed client with several DNS aliases (a node in a Beowulf cluster).
The NetWorker client had been configured so that one of the DNS aliases was
listed in the "Aliases" section.  When our research group reorganzied some
of the services their hosts provide, they had the DNS updated so that some
of the DNS aliases (CNAMES) pointed to different systems.

Once that happened, the index entries for the problem client started going
into the client index for the new system, not into the client index
I expected them to be in.

In other words, you might have better luck finding where the index entries
are going if you don't use the `-c' option.

You should be able to verify if the index entries are going to the wrong
spot by getting the properties (number of files and disk space used) for
all your client index directories, and then do a backup of just the problem
client.

Then get the properties again, and see what client index changed, if any.

If no indexes changed, then the client index data isn't being stored, and
debugging the problem will have to proceed along a different path.

Tim
--
Tim Mooney                              mooney AT dogbert.cc.ndsu.NoDak DOT edu
Information Technology Services         (701) 231-1076 (Voice)
Room 242-J6, IACC Building              (701) 231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

To sign off this list, send email to listserv AT listserv.temple DOT edu and type 
"signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu 
if you have any problems
wit this list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

<Prev in Thread] Current Thread [Next in Thread>