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.
bingo.1
1 Rookie
•
2430 Posts
585
0
Posted July 24th, 2020 11:00
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.