On Fri, 20 Sep 2002, Tim Mooney wrote:
>
> I leave the Windows restores to our Windows and Netware guys, but if this
> were a UNIX box and I needed to recover a "large" filesystem and I knew it
> would only take two savesets to do it, I would use a saveset recover, not
> browsing via the recover command.
>
> I don't even know if that's an option for Windows though.  Is that
> available under windows?  You've been on the NetWorker list as long as
> I have, so I know you know NetWorker as well as I do (probably better!).
> I'm guessing you didn't mention saveset recovery because it's not an
> option, but I had to ask.

Yes it is an option, but I only wanted a narrow set of files from
that saveset so and the target volume was barely large enough to hold
the files of interest.

> I agree that it would be better if recover just worked (and didn't take
> days to figure out which files it needed off which tapes, but it's hard to
> know how much that could be improved), but saveset recovery generally is
> much faster than browsing and recovery.
>
> The downside of saveset recovery is that you don't necessarily get an
> exact picture of how the filesystem was when it was last backed up.  Any
> files that were deleted since either of the backups took place will come
> back.

Fortunately, the actual disk where the files in question reside is
still readily accessible. I missed my window of opportunity for doing this
restore. The folks who manage the client in question will most likely
set up the source volume as a Windows share and just copy the desired
files to a new volume on a different system via our local network. This
was my original proposal in the first place.

In the meanwhile, just to verify the integrity of the backup, I have
iniated a saveset restore to a secondary disk drive in the PC in my
office. My PC sits on a slow network segment and the target drive is a
rather slow device too so I am not setting any speed records with this; I
am just trying to assure myself (and management) that if the original
volume did fail, we could eventually get back all the data from tape. So
far, that saveset restore has been chugging along for the past five hours
without incident.

In the meanwhile, a Legato tech consultant suggested to me that the index
entries for the source client in question might be corrupt. When my test
restore ends, I plan to reboot the backup server here and use "nsrck -L6"
to fix any problems, then try a test directed restore just to see if that
works.

--
Note: To sign off this list, send a "signoff" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=