First of all you should use "nsr_render_log" to browse a *.raw logfile content. This way you sill see complete and all variables will be replaced with their current values. Do not forget that you must not necessarily view the whole log by specifying the relative start time like in this example:

    nsr_render_log -S "-1hours" daemon.raw

It could be that your volume is mounted ... but on a wrong device. Sounds weird but I would test that:

  -  stop the recover process

  -  unmount the volume

  -  restart the recovery

Now you should see an alert which shows where NW expects the volume to be mounted.

   !!! Be careful if you re-mount it - do not re-label it !!!

If you had previously attempted a restore and had to abort or kill it for some reason then I assume there might be an ansrd still running on that backup server. Go ahead and kill the ansrd on the backup server. Also, make sure that the NetWorker server is not overwhelmed with backup streams. How long have you left the restore to run before you decided that it was no use waiting ?

Checked that log and found this:

6211 1573158440 2 0 0 1332 1352 0 dal-backup.tccilaw.com winworkr NSR warning 2 %s 1 0 57 53365:winworkr: NSR server `dal-backup.tccilaw.com': busy
6211 1573158440 2 0 0 1332 1352 0 dal-backup.tccilaw.com winworkr NSR warning 2 %s 1 0 77 71739:winworkr: Warning: Required volume daldd250001.002's status is off-line
6211 1573158440 2 0 0 1332 1352 0 dal-backup.tccilaw.com winworkr NSR warning 2 %s 1 0 48 71740:winworkr: Waiting 30 seconds then retrying

I tried to mount the log but keep getting this error: Connecting to 'daldd2500-01' failed [5040] ([ 5976] [6888]

ddpi_connect_with_user_pwd() failed, Hostname: daldd2500-01 , Err: 5040-ddcl_ost_connect_internal() BN_hex2bn(public_key.e) error:00000000:lib(0):func(0):reason(0)).

o_O

It seems as if there is a 'connection issue' between the DD and your NW server/storage node. This could have a bunch of reasons:

  -  your DD has been filled up

  -  your user name/password has expired

  -  NW does not control the device properly any more.

You could kill all nsrmmds (be careful not to disturb a running job) and/or restart the NW server/storage node processes or even reboot the system(s). But this will not help in case of the first two issues.

So without a closer look at the whole environment it is hard to help you. You probably do better if you start an SR with Dell/EMC now.

We did have a similar error after upgrading from 8.2 to 9.2.1.5. not sure if you have the same issue, our issue is related to backups as well. Do let me know if your see similar issue on your server as well or if its just the restores.

At least from the error its looks like your DD is not communicating with the said storage node. Do you have more devices on the same DD on the same storage node that are working ?

I have 5 data domain devices connected in this system. We have permanently discontinued any backups jobs on this system. It is NW 8.2 and I am only trying to recover some files, but no matter what backup set or what data domain device I attempt to restore from, either I get server busy or I did deep and find access issues.

How would I go through the entire system and update all the admin access?

Would Dell still offer support on this legacy system and hardware?

I am sure someone will offer support - it could also be a partner. But they might charge extra.

BTW - your statement with respect to the NW version is confusing: is it now 8.2 or 9.2?

If it is NW 9.2, make sure that the server's property "Disable RPS Clone" (in the Configuration tab) will be checked. Even if it is, switch it back and forth. This guy might be responsible for a lot of other effects.

So sorry for the confusion. It was both 8.2 and 9.2. 

I had virtualized the server in order to play with it without destroying the server. I attempted to upgrade it and was setback a bit, so I went back to the physical server (8.2) to attempt the changes suggested here.

I will keep trying, and appreciate the suggestion and any future advice.