Networker

Re: [Networker] How to migrate a networker client to another networker server

2007-03-14 13:50:54
Subject: Re: [Networker] How to migrate a networker client to another networker server
From: Steffen <xy.0815 AT GMX DOT NET>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Wed, 14 Mar 2007 13:47:09 -0400
Hi Dirk :-)

have you taken a look into Knowledge Base article esg55456 yet?

----------------------- snip ---------------------------------

How to move a NetWorker client from one NetWorker (6.X\7.X) server to 
another and restore it's tapes


1. For the client being moved, obtain it's Client ID from it's Client 
resource by using the mminfo command, as follows: (assuming the client's 
name is volleyball)


# mminfo –av – q client=volleyball –r client, clientid | sort |uniq


The output of this command is similar to the following:


client client ID

volleyball 5225b7ba-00000004-40ebf557-40ebf556-00010000-89456792


Save the Client ID information for use later when creating the client on 
the other NetWorker (Server B).


2. Create this client on the other NetWorker (Server B) with exactly the 
name it appears as in Server A. i.e. if the client on Server A is created 
with fully qualified domain name (FQDN) then the client should be created 
on the other NetWorker (Server B) with the fully qualified name. For more 
details, refer to How to Create Clients from the Legato NetWorker 
Administrator's Guides for Unix or Windows. 


3. Make sure that the clientID for this client matches the client id for 
the client on the original NetWorker server by entering the original 
client's ClientID value in the Client ID attribute of the newly created 
client resource. For additional information on the Client ID attribute, 
refer to How to Access the Client ID in the Legato NetWorker 
Administrator's Guides for Unix or Windows. 


4. Create the pools on the NetWorker Server B that these tapes were 
assigned to originally in the NetWorker Server A


5. Assign this client to a group


6. Set it browse and retention browse and retention policy


5. Update the servers file on the client with the name of NetWorker Server 
B. After adding the NetWorker server B hostname to the servers file, you 
must restart the NetWorker client daemon (nsrexecd).


6. To enter the save set information from the tapes that the original 
client was saved to and to build (populate) the Client File Indexes for 
the client, run the scanner command as follows for each tape: 

scanner -i -c clientname devicename


5. Use nwrecover or recover commands to browse this client's indexes now 
on Server B.


6. Select desired files and then recover the files.


7. Since this client is now being backed up by a different NetWorker 
server, add the new NetWorker server hostname to the /nsr/res/servers 
file, or for Unix, if not using the servers file, modify the 'nsrexecd -s 
backup_server' statement in the NetWorker startup script for each 
NetWorker client. After adding the NetWorker server hostname to 
the /nsr/res/servers file, you must restart the NetWorker client daemon 
(nsrexecd).

----------------------- snip ---------------------------------

Pls. give me a call if you need more info regarding NetWorker.
.. or if you would like to offer a good cup of coffee ...

- Steffen -

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>