DR Drill Problem with Networker Server ID

[Agamar]

I am doing a Disaster Recovery drill and have set up a test server with the same version of Legato as the production server: Networker 7.1.1 on Windows 2003.

This is what I have done:

-Installed networker to the exact same drive / folder as production server.
-Ran MMRECOV against the latest full tape bootstrap.
-Renamed the RES.R folder to RES.

Nsrck -L7 'nameofbackupserver" is failing to restore the index for my test backup server.

This is what I have found:
-The client id for the new server does not match that of the old server. I have created a new client with the FQDN of the old server (the test server is only using the short name, since I cannot add it to the domain). I have given this new client the ID of the production server. This worked, but I do not know where to go from here. I still cannot run nsrck -L7

The only thing I haven't yet tried is to do a save set recover of the backup server drive and then stop the services, copy over all the files, and restart the server.

 

[605]

The client ID should not create any problems as it is obvious to happen if you have a new machine. You may try to recreate the client using the original ID.

And do not forget to restart the server in between.

 

[Agamar]

Ok, I have reloaded the server and added it to the domain. (Since the server is not on the network, I just made it a Domain Controller temporarily, and it now has the correct FQDN of the production server).

Now, I have our cloned tapes from the full backup, but when I run the nsrck -L7 command, in the monitor window of the gui, It is asking for the full tape instead. How can I get it to take it from the cloned tape?

 

[milanvo]

You should mark original saveset as suspect, so on restore Networker ask for clone tape.

You can do it in Networker Administrator/Volumes, Show savesets and Shange status to Suspect.

For large number of savesets, i suggest get SSID/CLONEID by MMINFO amd change status by NSRMM command in batch file :

nsrmm -o suspect -S ssid/cloneid

 

[605]

Good point. This needs improvement.

nsrck should at least allow to specify the read pool. As you can not do this or specify the recover media directly, the only way is in fact to set the original media to suspect.

 

[Agamar]

That worked perfectly. Thank You!

BTW, does anybody know what Networker searches for when determining if you need to get an update license. My test box is complaining about it and has disabled the test server. I have the same server name and IP address, but vastly different hardware.

This disaster recovery test is becoming quite the pain. Glad I am doing it now rather than later : )

 

[605]

If you are updating the software, NW might ask you for an update enabler. This is needed if you install the next major release (i.e. if you update from 6.x to 7.x) but may also apply (rarely) if you stay in the same version (i.e 6.0 to 6.1.4 - This is an theoretical example only!!!).

The release notes should tell you when such is needed.

Please remember that it is recommended not to upgrade during a DR situation. Just recover the system as it was before.

 

[Agamar]

That is strange, I am restoring to the same version of NW, version 7.1.1

Seems to let me do restores for now, but shows an error.