1 Rookie
•
30 Posts
0
1276
September 25th, 2020 01:00
Networker Unable to clone to tape even when tape is mounted
Have a Networker environment, in which there's backup to Data Domain, and cloning to a tape library. The backup runs and completes successfully. However, when it comes to the cloning to tape, the backup hangs and doesn't start. The tapes are loaded and mounted successfully, but no writing is done. There are no visible error messages. The status stays on 'Ready for writing, done' . But no writing starts.
Have attempted restarting Networker services on the storage node, and the Networker server. Even reset the tape library. Still not able to write.
Any thoughts on how I can fix that.
It's Networker 18.2.
No Events found!
mr_robot
1 Rookie
•
30 Posts
0
October 19th, 2020 22:00
After attempting several things including restarting Networker services on storage nodes and Networker server. Disabling and Enabling tape drives. Depositing tapes into the tape drives and running a backup and even resetting tape library.
It turns out was the issue was with communication between the storage node and the Data Domain. It wasn't reading the data to be cloned. So after restarting the network service on the storage node, it was able to run and complete the cloning to tape.
bingo.1
2.4K Posts
0
September 25th, 2020 01:00
I have worked with exactly such solution for years. It has been used with NW 7.5/Windows up to NW 9.x before we decided to use an ECS as cloud media.
What we have used was 'scripted cloning' where we triggered the scripts using the Windows Task Scheduler. This had a bunch of advantages. The major ones were:
- There were no dependencies with respect to timing. The clone scripts started every day at thew same time. And they could be restarted whenever it was necessary.
- Due to the fact that we used a bunch of backup devices, we ran a separate script for each DDBoost device which could run in parallel (up to 14 at a time).
- Due to scripting we had full control over the process and changes could be implemented easily.
To investigate your problem, may I suggest that you start running the nsrclone command from a command line for just cloning a single save set and pipe the output to a text file for further investigations. Use the general command
nsrclone [-v] -s server [-J recover_snode] -d save_snode -b dest_pool -S ssid > file.txt
If you need more information, you can add more 'v's, if necessary.