We have to do this all the time, (Katrina event), and it doesn't take
that long, maybe 10 - 15 minutes (or less) on something under 1GB. It
does do some kind of indexing event AFTER the data has been restored.
Again, unless you are short on disk space, or have an older system, it
shouldn't take long. Our 15-20GB indexes would take a while - as long
as 45 minutes or more.
Sometimes our indexes require 3 tapes to restore, depending on how far
away from the FULL backup it was. Is it waiting for another tape?
I assume you are running this from the command prompt, if so, hit enter,
and see if that does anything. Sounds silly, but I've had a few
"stick" in between loading a full and non-full tape, or at the very end.
David M. Browning Jr.
LSUHSC Enterprise Network Operations/Help Desk
(504) 568-4364 (Direct)
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of George Sinclair
Sent: Tuesday, November 28, 2006 4:09 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] Recovering an older index?
Hi,
I want to recover an instance of a directory that is older than the
browse policy for the given client. The client
is only able to browse back to 09/26/06, and I need it from 09/14/06.
I'd do a save set recover, but the save set
is huge, and I only need a small directory. Also, there would be a bunch
of instances to have to piece back
together, many of which, while not huge, are fairly large.
I ran 'nsrck -L7 -t 09/20/06 client' to merge in an older index
(size=620 MB, level=9) with the current one. What I should have probably
done is picked the previous one from 09/23/06 which was a level full
(size=1022 MB), but I missed that one.
Anyway, it requested an older volume with a full index from 05/15/06
(size=923 MB). That was the previous level full. Not sure
why it wanted that volume when I specified 09/20/06? Well, it recovered
that older index, and now it's just sitting. No prompt back yet.
I ran truss against the nsrck process, and it's cranking away, not idle.
I would guess that it's performing some kind of update at this point,
but it certainly
has been running for a while now. The size of the index for this client
prior to this escapade was about 977 MB.
1. Any ideas why it wanted to recover from the older full?
2. Does running 'nsrck -L7' also run 'nsrck -L6'?
How long can I expect this to take?
George
--
George Sinclair - NOAA/NESDIS/National Oceanographic Data Center
SSMC3 4th Floor Rm 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
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
|
