Networker

Re: [Networker] Indexes disappearing ..

2011-09-30 13:08:39
Subject: Re: [Networker] Indexes disappearing ..
From: Yaron Zabary <yaron AT ARISTO.TAU.AC DOT IL>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Fri, 30 Sep 2011 20:06:37 +0300
Is the time on the client OK ? The time of the saveset is taken from the client, so that can cause early expiry of savesets of even an error message.

On 09/27/2011 08:55 PM, Michael Leone wrote:
Here's a weird one .. I have 2 clients (both virtual cluster clients),
both with browse and retention policies of 2 months, who have their
indexes either completely deleted (i.e., the index sub-folder for that
client is 0K),  or it only has the previous day's activity. These are both
backups made with the SQL Module. Neither client nor job has changed in at
least months, perhaps longer.

Even weirder - this seems to happen on every weekday. The index backup (we
do "savegrp -O") on Sat morning - which would have the index from the
Friday backup - would be there. And that would be the only index backup
that wasn't empty.

mminfo -avot -q
"client=networker-server,name=index:client,savetime>09/01/2011" -r
volume,client,ssid,name,level,savetime(22),totalsize(2)

  volume        client     ssid       name                             lvl
   date     time total
006792         networker-server 1667207181 index:client full 9/1/2011
10:00:45 AM 32 KB
006872         networker-server 1298192353 index:client full 9/2/2011
9:19:29 AM 32 KB
006872         networker-server 2825005238 index:client full 9/3/2011
9:16:38 AM 10 MB

I wouldn't have noticed it, except that I needed to do a recover, and I
couldn't because it said there had been no files backed up (which I knew
to be false).
(that snippet is for earlier in the month, but it's the same all month)

"nsrls" shows the total size of the index to be zero
"nsrck -L6" shows no errors, and a total size of zero
"nsrck -L7" reads back in zero (unless I specify one of the Saturday
backups, like 9/3/2011 above)

Note that the groups that these 2 clients are in are set to "no index
save", like all our groups. I have 130 clients, and am only seeing this
problem on these 2. One client is a clone job, one is not.
EMC seems to be confused, as well. :-)

Thoughts, anyone? I am going to uncheck the "No index save" temporarily on
these groups. Can anyone suggest something else to diagnose?

Thanks


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 with 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