This seems like a slick idea, and if it works, this would be exactly
what I'd like to do so as to avoid having to read through the entire
parent saveset (file system) to get what I want, but I've never tried
this before, so let me ask one question. The host in question is
currently unavailable, but there is still an entry for it in the client
listing, and it's index still exists on the primary server. I can use
nwrecover to view this client's data from another client, so I would
assume there should be nothing to preclude me from merging in the old
index with the new even though the client is not available?
If for some reason the nsrck command doesn't work or maybe the index
from that day is not around then I could just continue trying different
days until it works, correct? Also, does this business of merging in
older indexes in anyway effect the currently browsable index entries?
Just don't want to corrupt of damage the current index.
Thanks for the tip.
George
Davina Treiber wrote:
>
> On Wed, 17 Sep 2003 11:11:07 -0400, George Sinclair
> <George.Sinclair AT NOAA DOT GOV> wrote:
>
> >The data I need to recover is beyond the browse period so nwrecover is
> >no good. I thought that the 'recover' command was just the command line
> >version of nwrecover in which case it's likewise useless. We're running
> >NetWorker 6.1.1 under Solaris 8 on primary server and NetWorker 6.1.1
> >unde Red Hat Linux on storage node server.
> >
>
> recover is the command line version, but it includes the -S option, for
> save set recoveries, if that helps.
>
> What are you really trying to achieve? Would you prefer a standard recovery
> if only your save set was still browsable? Have you considered repopulating
> your index in order to do this?
>
> Remember that in NetWorker 6, nsrck is a very good friend. If you have an
> index for the client still on tape and the save set still in the media
> database, you can merge this old index into your current index using nsrck -
> L7. Say for example your non-browsable backup of client fred was written on
> Jan 1st, and you backed up the index at the same time, you could run:
> nsrck -L7 -t "Jan 2" fred
> and your index for that backup will re-appear.
> I'm sure many users forget about this wonderful feature of NetWorker.
>
> --
> Note: To sign off this list, send a "signoff networker" 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.
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
--
Note: To sign off this list, send a "signoff networker" 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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
