|
Re: [Networker] after nsrck -L7, still can't browse older savesets
2008-08-06 12:06:33
Tim Mooney wrote:
In regard to: Re: [Networker] after nsrck -L7, still can't browse older...:
I would make sure that the browse/retention policy of the clients cover
the time period and then run nsrck -L3
Ok, good idea. I just tried that, and it unfortunately doesn't make a
difference. I changed the browse and retention policy for that client
to "Quarter" yesterday, and I just tried the -L3. Still no luck.
I also now just completely removed the index for that client by doing a
rm -rf /nsr/index/backupclient.nodak.edu
on our backup server, followed by a
nsrck -L7 -t 05/31/08 backupclient.nodak.edu
I can see that the tape devices load two tapes (one for the full 05/04/08
and one for the level 9 of the index on 05/31/08) and read them. The
nsrck completes with:
# nsrck -L7 -t '05/31/08' backupclient.nodak.edu
nsrck: checking index for 'backupclient.nodak.edu'
9343:nsrck: The file index for client 'backupclient.nodak.edu' will be
recovered.Recover completion time: Fri Aug 1 14:50:50 2008
nsrck: /var/nsr/index/backupclient.nodak.edu contains 0 records
occupying 0 KB
nsrck: Completed checking 1 client(s)
The /var/nsr/index/backupclient.nodak.edu is recreated, along with the
the files inside that directory and the files inside the db6 directory,
but none of the savesets come back:
#ls -lR backupclient.nodak.edu
backupclient.nodak.edu:
total 8
-rw-r--r-- 1 root root 970 Aug 1 14:48 README
drwx------ 2 root root 4096 Aug 1 14:56 db6/
-rw------- 1 root root 0 Aug 1 14:48 v6ck.lck
backupclient.nodak.edu/db6:
total 4
-rw------- 1 root root 48 Aug 1 14:56 v6hdr
-rw------- 1 root root 0 Aug 1 14:50 v6hdr.lck
-rw------- 1 root root 0 Aug 1 14:56 v6journal
I'm was somewhat suspicious that this has something to do with the fact
that
these indexes were saved under NetWorker 7.2.2. We did our upgrade to
7.4.2 in mid June, some time around the 18th. However, I can use nsrck
-L7 to load the index from 06/01/08 (which was a full backup) and I do
get records back when I do that.
I'm going to try running scanner for the full index saveset from 05/04/08
and the level 9 from 05/31/08, to see if I can extend the browse time that
way.
I'll report back when I scanner completes.
Any solutions yet? Did you find the culprit? This whole business of
merging in older indexes from pre 7.4.2 releases (lets say, for example,
7.2.2) really makes me nervous. Has anyone else had this problem?
I need to upgrade to 7.4, and this scares me.
George
Thanks again for the suggestions!
Tim
--- On Thu, 7/31/08, George Sinclair <George.Sinclair AT NOAA DOT GOV> wrote:
From: George Sinclair <George.Sinclair AT NOAA DOT GOV>
Subject: Re: [Networker] after nsrck -L7, still can't browse older
savesets
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Thursday, July 31, 2008, 10:31 PM
Have you checked the size of the index after recovering with -L7? Check
the size before and after. I wouldn't be surprised if the entries are
there but just not showing up. If the index is larger after recovering,
try specifying the exact hours, min. and sec in the nwrecover window?
George
Tim Mooney wrote:
All-
I'm having a problem with nsrck -L7 for a particular client, and I
can't
figure out what I'm doing wrong. I've used nsrck -L7 dozens of
times
over the years, and I don't believe I've ever encountered this
particular
issue.
The NetWorker server in question is running 7.4.2 build 431 on Red Hat
Enterprise Linux (RHEL) 5.2. It was upgraded from NetWorker 7.2.2 +
security patches on RHEL 4.x in mid-June.
I need to make a particular client browseable as far back as possible.
The client does monthly fulls, and has a 1 month browse and 1 month
retention policy. If I run mminfo to see what's available for the
filesystem I care about on the client in question, I see
$mminfo -ot -q 'client=backupclient.nodak.edu,name=/home' -r
'ssid,savetime,nsavetime,ssflags,level'
ssid date save time ssflags lvl
2300354885 05/03/08 1209835659 vrEF incr
2401083268 05/04/08 1209900932 vrEF full
2954948539 05/06/08 1210118075 vrEF incr
3156361666 05/07/08 1210204611 vrEF incr
3424883546 05/08/08 1210291042 vrEF incr
3693404862 05/09/08 1210376902 vrEF incr
3576050683 05/10/08 1210463226 vrEF incr
3978790056 05/11/08 1210549416 vrEF incr
2368324781 05/13/08 1210696877 vrEF incr
3744082439 05/13/08 1210722823 vrEF incr
3140189003 05/14/08 1210809165 vrEF incr
2989289701 05/15/08 1210904795 vrEF incr
2536382245 05/16/08 1210982011 vrEF incr
1647276730 05/17/08 1211069094 vrEF incr
674312893 05/19/08 1211183621 vrEF incr
1748117596 05/19/08 1211246616 vrEF incr
1077109850 05/20/08 1211327461 vrEF incr
1026865244 05/21/08 1211414620 vrEF incr
1194723712 05/22/08 1211500736 vrEF incr
976706027 05/23/08 1211586849 vrEF incr
406366199 05/24/08 1211672569 vrEF incr
339397221 05/26/08 1211812439 vrEF incr
1211845526 05/26/08 1211845527 vrEF incr
1480367775 05/27/08 1211932188 vrEF incr
1648226091 05/28/08 1212018484 vrEF incr
2185185332 05/29/08 1212106805 vrEF incr
2537592207 05/30/08 1212192120 vrEF incr
2923553268 05/31/08 1212277236 vrEF incr
2504209457 06/01/08 1212363826 vF full
3326380107 06/02/08 1212450901 vF incr
and so on, with everything from 06/01/08 onward still being browseable
right now. I want to be able to browse back to 05/04/08.
Here's what I see when I make a query about the index: saveset for
that
client:
mminfo -ot -q
'client=backupserver.nodak.edu,name=index:backupclient.nodak.edu'
-r
'ssid,savetime,nsavetime,ssflags,level'
ssid date save time ssflags lvl
1880928342 05/03/08 1209839702 vrEF 9
35506666 05/04/08 1209911786 vrEF full
3005118368 05/04/08 1209956256 vrEF full
2602630204 05/06/08 1210121276 vrEF 9
2837597668 05/07/08 1210207716 vrEF 9
3223560138 05/08/08 1210294218 vrEF 9
3458526868 05/09/08 1210379924 vrEF 9
3223730397 05/10/08 1210464477 vrEF 9
3626469722 05/11/08 1210550618 vrEF 9
1999231918 05/13/08 1210702766 vrEF 9
3391763579 05/13/08 1210725499 vrEF 9
2838202360 05/14/08 1210812408 vrEF 9
2804743547 05/15/08 1210908027 vrEF 9
2184063411 05/16/08 1210984883 vrEF 9
1328510980 05/17/08 1211070468 vrEF 9
321992770 05/19/08 1211185218 vrEF 9
1278358464 05/19/08 1211249600 vrEF 9
875786226 05/20/08 1211330546 vrEF 9
808764223 05/21/08 1211417407 vrEF 9
959845139 05/22/08 1211503379 vrEF 9
808935893 05/23/08 1211589077 vrEF 9
70822980 05/24/08 1211673668 vrEF 9
70962992 05/26/08 1211813680 vrEF 9
842747787 05/26/08 1211846539 vrEF 9
1144825346 05/27/08 1211934210 vrEF 9
1446901338 05/28/08 1212020314 vrEF 9
1866420345 05/29/08 1212108921 vrEF 9
2185272571 05/30/08 1212194043 vrEF 9
2571232919 05/31/08 1212278423 vrEF 9
2822986913 06/01/08 1212374177 vrF full
3141832738 06/02/08 1212452898 vrEF 9
3527794933 06/03/08 1212539125 vrEF 9
3561497286 06/05/08 1212687046 vrEF 9
155747110 06/05/08 1212711718 vrEF 9
4048210651 06/07/08 1212861147 vrEF 9
3796611691 06/08/08 1212920427 vrEF 9
843871550 06/08/08 1212970302 vrEF 9
1229834522 06/09/08 1213057306 vrEF 9
1498356630 06/10/08 1213143958 vrEF 9
911240577 06/11/08 1213230465 vrEF 9
1246873481 06/12/08 1213319049 vrEF 9
1448286243 06/13/08 1213405219 vrEF 9
1851025415 06/14/08 1213491207 vrEF 9
2236985626 06/15/08 1213575450 vrEF 9
2606171623 06/16/08 1213662695 vrEF 9
2975358398 06/17/08 1213750718 vrEF 9
257634899 06/19/08 1213936211 vrEF 9
878465535 06/20/08 1214009855 vrEF 9
1516081979 06/21/08 1214092091 vrEF 9
2120149487 06/22/08 1214179823 vrEF 9
2673884814 06/23/08 1214267022 vrEF 9
3009515160 06/24/08 1214353048 vrEF 9
3177373908 06/25/08 1214439636 vrEF 9
3764662978 06/26/08 1214526146 vrEF 9
3462759933 06/27/08 1214612989 vrEF 9
577163712 06/28/08 1214697920 vrEF 9
711523948 06/30/08 1214840428 vrEF 9
1634301676 06/30/08 1214871276 vrEF 9
1953155425 07/01/08 1214957921 vrF 9
2339118053 07/02/08 1215044581 vrF 9
2741857371 07/03/08 1215130715 vrF 9
2540681938 07/05/08 1215281874 vrF 9
2188437923 07/06/08 1215359395 vrF full
and so on.
I basically want nsrck -L7 to merge in indexes so that I can browse back
to 05/04/08, where right now I can only browse back to 06/01/08.
I've tried several nsrck -L7 runs, such as
nsrck -L7 -t 1212278423 backupclient.nodak.edu
and
nsrck -L7 -t 1209956256 backupclient.nodak.edu
and
nsrck -L7 -t 1212277236 backupclient.nodak.edu
In every case, the nsrck -L7 completes and I get a message similar to
Recover completion time: Wed Jul 30 18:58:26 2008
nsrck: /var/nsr/index/backupclient.nodak.edu contains 732968 records
occupying 139 MB
nsrck: Completed checking 1 client(s)
However, I'm still not able to browse any further back than 06/01/08.
I've even tried changing the (current) browse and retention policy for
this client to "Quarter" and then doing the nsrck -L7, thinking
that
perhaps the -L7 was succeeding but the records were just being purged
again immediately, but that didn't make a difference.
It seems like I must be missing something obvious, but I can't figure
out
what it is.
Any suggestions?
Thanks,
Tim
--
George Sinclair
NOAA/NESDIS/National Oceanographic Data Center
SSMC3 E/OC3 Room 4145 | Voice: (301) 713-3284 x210
1315 East West Highway | Fax: (301) 713-3301
Silver Spring, MD 20910-3282 | Web Site: http://www.nodc.noaa.gov/
- Any opinions expressed in this message are NOT those of the US Govt. -
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
|
|
|
