Moving AutoChanger to New Server

[Guest_imported]

Currently I have a DLT2500 on an old 200mhz server. I just bought a new server and a Mammoth2. I originally wanted to continue them separatly and still do restores for the last year on the old system and do new backups on the new system. After talking to Legato about licensing, it isn't going to work unless I cough up about $10,000. I would like to move the DLT2500 to the new server and do restores, is this possible? The servers have totally different names and ip addys.

Thanks!

 

[rgzimmer]

You would have to arrange for licensing on the new server for the old autochanger. You can then scan in tapes as they are needed, but you can potentially run into problems with overlapping saveset numbers from the old server.

 

[Guest_imported]

How will I know what tape something I want to restore is on? Will I have to just guess? What other options do I have?

Thanks

 

[rgzimmer]

You can write mminfo to a text file for each client:

mminfo -c (clientname) > c:\clientname.txt

Of course, you can use whichever switces you desire for the mminfo command. Otherwise, you can keep a log of what is on each tape. We keep critical servers on specific tapes and those tape labels are logged with date and time stamps into a permanent record.

 

[jgarmer]

If you're replacing the whole server and autochanger set it up on a private net. Put a workstaton in between so you can move the data to the public net. Don't install Networker on this workstation. Do directed restores to it from the old server, then pickup data from it or even better use unc pathing to a server on the public net.

joe

 

[Barks]

Do you want to move the media database, client indexes and resource files to the new server? If so, then a server to server move will work. This procedure also assumes a separate bootstrap and client index backup is done to one tape.
You will first need to temporarily rename the new server's hostname, run mmrecov and use the latest bootstrap tape from the old server to create the media database and resource files, recreate the jukebox and devices, run nsrck -L7 to create the client indexes, then rename the new server back to its original name. You will then want to get a bootstrap and client index save done as soon as possible on the new server. Now you should be able to do backups and restores with the new server as normal.
Hope this helps.
Kent