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 TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Upgrading Legato Server.

Status
Not open for further replies.

bse1969

IS-IT--Management
Dec 10, 2004
55
US
I am upgrading to a new server. I do not need to move any data from the old server. I am doing a new install and starting from scratch. Is there an easy way to move the licenses from the old server over to the new one?
 
Hi,

The licenses are connected to the host id of the server. You have to to a host transfer through legato or your service provider.

Hope this helps!

-Joe
 
I was hoping to avoid having to call Legato. Thanks
 
Ok new twist to the puzzle. I do need to migrate the old volumes over to the new server. I am running on Win2K and the new server will be Win2003. My setup on the new server will be different in terms of devices. The old system we setup up based on clients and the new system will be based strictly on devices and the pools will determine the client. Since I will be changing how the device are setup if the need arises how would I mount the older volumes so I could do a restore? I have not played with mounting older volumes but what little I have done usually results in the information in the volume being deleted when I mount it. Maybe there is a command line way to do this and I have just not found it yet?
 
Migrating the volumes is not a general problem. However, it will only work smoothly if you have not defined a device for a pool. In this case, you must not even do anything.

In general it does not matter which device NW will use for reading and writing. However, it stores this information in the volume's label. If you try to mount such media in another than one of the previously defined devices, you will receive a message like this: pool "name" cannot be mounted on this device.


Remember - not even the pool "Default" which you can not change at all, has a device defined.

 
What is the best method for moving the volumes to the new server? Just copy them over through the OS or use legato to move them?
 
If I were you...

I should use a:

scanner -m \\.\Tape0

for restoring the index and media database

and after I will use

nsrim -X

in order to check the MDB

You 'll be sure that infos were not corrupted by the OS
 
scanner -m will only restore the media data base

sorry for this mistake
 
Thinking about my previous statement .....

>>>>> In general it does not matter which device NW will use for reading and writing. However, it stores this information in the volume's label. If you try to mount such media in another than one of the previously defined devices, you will receive a message like this: pool "name" cannot be mounted on this device. <<<<<

..... i was concerned whether this is really true because such would really hurt NW's recover capabilites.


I have to admit that this is not the whole story. What i said is true. However, for a fast test, i just tested this on a file device by copying the contents to another device on the same system and leaving the existing pool behind. However, if you transfer the media to another system where the pool is unknown, the pool will not be recreated (the new system of course does not know the configuration - instead you will receive this message: scanner: create pool manually after scanner; continuing...)


You may recreate the pool after scanning. And if you do not specify any device, you will be able to mount the media on any (compatible) device.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top