Your logon on the server may be able to see the mapped drive letter to the NAS box, but the "NetBackup Client Service" that fires off "tar" to perform the restore cannot see the drive letter because it is almost private to your logon.
I'm not a Windows Admin, but I wouldn't use the master server for this. IMHO I'd find another quiet non-producton server to act as the NetBackup client for the restore. I say this because I think you'll need to do some reboots... One way I've accomplished this before was to create a Windows scheduled-task to run at startup on the client that maps the drive. Set the scheduled task to run at boot time, and the scheduled task basically ran a five line DOS batch script that never completed:
@echo off
sleep 300 (get a copy of sleep from the Windows resource kit)
net use ..... (map the drive as necessary)
pause
exit /b
...the sleep is o give the server enough time to boot up, get it's NIC in order and settle down.
...now the trick is to use the "pause" command so that the job never completes.
...and the reason for choosing another server is - WIndos being Windows - sometimes you have to reboot to force the mapping to re-form.
Like I said, I'm no Windows Admin, and I did the above years ago, so maybe there's a better way these days to achieve a "permanent" mapping that survives reboots. Anyone else got a solution?
