Hi Bobby, thanks for your reply, i ran those commands and they were successful from both server and client.
Annoyingly however, the tape i had used to store the backup was removed from site this morning, so to save having to wait for it to be returned (as its only testing) i rebuilt the box manually with a new name and performed the steps required again and this time things have gone smoothly.
Odd that it didnt work previously as i've not done anything different this time around and i'm using the exact same hardware still with nothing changed, so i'm going to be testing this further to ensure its reliable.
coganb
736 Posts
0
January 25th, 2012 06:00
Hi,
Check with nsrinfo & mminfo to see if the data has been backed up correctly and that the savesets are present
in the NetWorker indexes:
nsrinfo -s [NW server name] -N "DISASTER_RECOVERY:\\" [NW client-name]
mminfo -s [NW server name] -q "client=[NW client name],name=DISASTER_RECOVERY:\\" -ot
If this looks ok when run on the NetWorker server, try running them on the NW client itself. There could be a
communication problem between the client and server that is preventing it accessing the data it needs in the
NetWorker mediadb or indexes.
-Bobby
Lagerstars
9 Posts
0
January 25th, 2012 07:00
Hi Bobby, thanks for your reply, i ran those commands and they were successful from both server and client.
Annoyingly however, the tape i had used to store the backup was removed from site this morning, so to save having to wait for it to be returned (as its only testing) i rebuilt the box manually with a new name and performed the steps required again and this time things have gone smoothly.
Odd that it didnt work previously as i've not done anything different this time around and i'm using the exact same hardware still with nothing changed, so i'm going to be testing this further to ensure its reliable.