Correct - your environment should be updated. But let's see what you have:   -  How have you setup the cloning? - Scripted cloning or automatic cloning (a clone action after the backup action has finished) or by a special clone workflow?   -  Is it possible that the jobs take even longer than the interval when they will be started next?   -  Are there issues with the tape libraries/drives. Any errors or media alerts?   -  Before you look at the logs, which you can find in ...\nsr\logs\policy\policy_name\workflow\... may I suggest that you run nsrclone manually first to verify whether there is a general issue. nsrclone has a lot of options - please read the Command Line Reference for full details. Remember that you can setup another system and backup to 2 disk devices to familiarize with the general functionality. NW will run 90 days in eval mode by default.  
Hello everyone. I am new to NetWorker but skilled in NetBackup. And I hope you will point me to some details of cloning troubleshooting. Our environment (quite old): NetWorker 9.2 on Windows 2008R2 2 Data Domain DD990 6.0.2.30 and 2 TLs. According to design, cloning should run from DD to TL. We have some clone jobs configured. Some of them run for days and never finish. Details of those jobs are full of messages like: 22.07.2020 16:51:26 nsrclone command has retried 2522 times. 23.07.2020 18:18:03 Error trying to match clone ID and save set ID, removing erroneous save set(s) and continuing. 21.07.2020 18:33:10 07/21/20 18:33:10.532491 Removing recyclable save set from original clone list 3254933032 ss_flags 1304   I suspect that cloning is trying to duplicate wrong save set list. Or we faced lack of tape resources (drives are too busy).   I have some questions: How can I get a list of save sets within this jobs? Which CLI command I can use to debug cloning jobs? Where can I find logs of these jobs? Details are useless atm.   Regards, Yuri.
Stuck cloning operations NW9.2 + DD990 + TL