Networker

Re: [Networker] Saveset Restore

2012-01-13 13:56:28
Subject: Re: [Networker] Saveset Restore
From: Tim Mooney <Tim.Mooney AT NDSU DOT EDU>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Fri, 13 Jan 2012 12:52:13 -0600
In regard to: Re: [Networker] Saveset Restore, Swartz, Jerome said (at...:

Also, the client has been deleted to recover the license.
This is all covered in the NetWorker documentation, which you should have,
so I'm not going to go into much depth with the steps.

Also, it's good form to give some information about your environment
(Networker version on your server, what platform it and the client in
question are), as some of the answers may depend on your environment.

You'll need to create the client again (don't add it to any groups when
you create it) and you'll need to be certain it's recreated using the same
client id that it had previously.  If you don't make the client id match
what you had previously, your job will be more difficult -- still
possible, but more than likely you'll have a harder time getting help.

If you didn't save the client id, you should have, but you can recover it
with the first mminfo command I show.

Hi folks,

I need to restore data from a client that has been decommissioned. We
still have the data as it's a 7 year retention and need to another
server to data to another server.
I can't grok that last bit, but it likely doesn't change the answers
anyway.

1. What is the command to check the valid savesets for that client?
Start with mminfo.  You probably want something like

        mminfo -ot -q client=your_client_name_here \
                -r 'clientid,volume,ssid,client,name,savetime,nsavetime,level'

Other report (-r) fields are described in the mminfo documentation. You
may also find fields like "totalsize" and "nfiles" interesting.

If you haven't already done so, create the client with the client id your
query returned.  Make certain the name exactly matches the previous name
too, even if you have to first create an /etc/hosts entry on your
NetWorker server or add a temporary record to your DNS.

You will *also* want to check to see if you still have the index savesets
for that client.  If you do, life will be easier.  That query would be
something like

        mminfo -ot -q 
client=your_networker_server_here,name=index:your_client_name_here \
                -r 'volume,level,nsavetime,name'

2. What steps need I follow to ensure I can restore the data to another server?
Once the client is created, the next steps depend on whether you have the
client file indexes and whether you need to recover just a few files or
want entire savesets back.

Either way, though, since you want to recover the data to a different
client, you'll need to modify the client entry you just (re)created to
allow "Remote access" for the client that will actually recover the data.
You do that by modifying the "Remote access" field, it's in the "Globals
(2 of 2)" tab of the admin gui.

You now have a four or five way fork in the road.  How you proceed depends
on a number of things.

If you need to browse the client and recover individual files whose paths
you don't know, then you need either 1, 2, or 3 below.  Alternately, if
you don't need to browse, either because you want to recover everything
or because you know the exact paths for the files, you can skip 1-3 and
just do 4 or 5.

1) you still have the client file indexes because they were never deleted
from disk on your networker server.  You can proceed right to running
recover on the client that will be recovering the data, telling it to
browse the index for the client you recreated by using the "-c
your_client_name_here" option.

2) you have the index savesets on tape.  You can recover them using nsrck
-L7, but there may be some annoying additional steps needed, depending on
what version of the server you're running.  Those steps used to be
documented in the knowledgebase article esg98649 on Powerlink, not certain
if that's still the most up-to-date one, but it's worth a look.

Once you have the client file index, you proceed with the recover -c
as described in 1.

3) you don't have the client file indexes at all, so they will need to
be rebuilt.  Run "scanner -i" on the savesets you want to recover from,
and when the client file index is rebuilt for those savesets, proceed
with recover -c.

4) you don't need the client file indexes because you're going to recover
entire savesets.  Use recover with the -c and -S <ssid> options, possibly
multiple -S <ssids> at once.

5) you don't need the client file indexes because you know the exact
path(s) of the file(s) you need to recover.   I always used to perform
this procedure through the old (green) NetWorker Administrator GUI, so
I'm not certain how it's done these days, but I believe the thing to try
is recover with the -c and -a options, to specify the exact path to the
file(s) you want.  If that doesn't work (because it turns out that -a
requires the client file index) then some additional research will be
required.

Good luck!

Tim
--
Tim Mooney                                             Tim.Mooney AT ndsu DOT 
edu
Enterprise Computing & Infrastructure                  701-231-1076 (Voice)
Room 242-J6, IACC Building                             701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

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

<Prev in Thread] Current Thread [Next in Thread>