I have a policy which ran but failed on the last action.
action 1 - backup
action 2 - clone to DDR at another site
action 3 - clone to tape
So the clone to tape action failed due to the destination storage node not being specified. Is it possible just to run this step again?
I doubt that.
Although you may specify the action from the command line, like ...
nsrworkflow -p <policy> -w <workflow> -A "'<action>'"
... it will be rejected due to a missing 'override action'.
Hovewer, if you use ...
nsrworkflow -p <policy> -w <workflow> -A "'<clone_action> -l full'"
... it will actually run a backup.
That's why we rely on scripted cloning where you can actually use even more parameters to check existing clones for each save set, like 'validcopies'.
Thanks bingo. You say it will run a backup? That's not what I want to do as it's a monthly job, hence why I just want to run the clone to tape action.
EMC support told me to run just the clone action and gave me a link to a KB article
So it's not possible at all to just run that one action?
Hhm - good point.
Yes, you can define a workflow which will only run a clone action. And it will work.
However, my personal favorite is scripted cloning
- easy to configure
- easy to change
- much more flexibility
- you can use much more mminfo parameters to select your save sets precisely
- you can specify a storage node (load balancing)
- you can add other criteria as a specific retention date
- and it is valid for all NW versions 😉
Then schedule such script via in cron/task scheduler. Done.
We have used this method for years.
It will depend on which version of NetWorker are you using. If 91.1.2 or before in the 9.1 series then you might observed that restarting the backup workflow does not restart/start the clone action. But the latest version of NetWorker does not have this issue, so inc ase you have not upgraded, then best to plan an upgrade.
I am using NetWorker 22.214.171.124 currently. I haven't noticed if it just restarts at the last failed action.
I do need to plan an upgrade though as it appears this version has a lot of bugs.