Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Merging multiple Networker Servers into one.

Status
Not open for further replies.

zebort

Technical User
May 11, 2001
22
US
Currently I have 3 SGI Networker servers. Each storage node is combined on each server. I'd like to change to one SUN server with three SGI or SUN storage nodes. Is there any way of merging indexes to one server and splitting off storage nodes off those servers? Has anyone ever accomplished this? Can it be done?
 
Hi,

From my experience I recon that if you choose on e machine as a Server,then scann in all relevant volumes from the other 2 machines - Legato will create a client name for both extra to the server name,and will nmanage the indexes properly.
Also you will have to define an alias for the SERVER to be able to access the other 2 clients (in the client setup - detailed view).

After that the definition of the storage nodes on the other 2 machines wil be normal Legato storage node definition. "Long live king Moshiach !"
h
 
There is no iron clad way of merging two legato servers without the chance of great error. The reason is this: When a backup is sent to the server, the actual data is sent to tape while control data (info about the data) is written to the index and media database. These records on both databases are tied together by a unique identifying number. This number (ID) is unique to this machine only. If you merge databases from varying installations, you run the chance of duplicate ID references in the databases. This WILL cause corruption in the database.

This is a gamble my friend and though the other response is accurate in logistics, the concept is simple--corruption is not an option.

Hope this helps.

Matthew
 
mkkeane,

I have done it severall times - scanning in other system made tapes,thus adding a new client name to my server.

There was never a problem.

Possibly "nsrck -L6" is a good idea right after. "Long live king Moshiach !"
h
 
The duplication is not an absolute and is only a possibile result of trying to merge the databases. This is the "supported" documented stance of Legato Support Providers (that i have had experience with). This is a gamble as to whether this will happen to you or not. Most people choose not to gamble with the integrity of their backups.

nsrck -L* will not take care of duplicate ID's in the database. The maintenance processes that take place in nsrck are documented in the man pages of the product.

There are "many ways to do many things" within NetWorker, but my philosophy is "the supported way is the only way".

The only exception to the rule is "If willing to live with the consequence, then go for it."

Matthew
 
Thank you!
This helps a lot. It doesn't appear to be a good idea to attemp to merge. Scanning wouldn't work for me, because I have like 1000 20GB tapes per server, but thanks anyway.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top