Unsolved
1 Rookie
•
27 Posts
0
3106
February 1st, 2021 05:00
Networker concurrent cloning action
Hi,
I am relatively new to Networker, so I am pretty sure this question can be answered easily. I am running Networker 19.2.
My workflow backs up all my VMware VMs to a DataDomain daily. Once a month, we clone the latest backup to LTO tapes drives for offsite backups. So I have 2 pools (DataDomain and LTO7 tapes drives).
Currently, this workflow is configured as the following :
- First step is Backup daily to DataDomain.
- Second step is clone to tapes drives, but it is only set to "exec last friday every month". All other days of the month are set to Skip.
The problem that I am facing is that the cloning process takes 3-4 days and when it is cloning, it is not doing anything else. The workflow does not start again until the cloning process is finished. So my daily backups are not running until my cloning is finished. This is causing my daily backups to be skipped for a few days. I'm pretty sure I could run these actions concurrently since it is 2 different pools.
Looking at the Policy Action wizard for the cloning action, I found a Concurrent option. Reading the Admin guide, from what I understand if the Concurrent option is checked, the cloning action would start at the same time as the Backup action, which is not exactly what i want to achieve. I would like my cloning action to start after the last friday's backup, but just run concurrently/in the background so that my daily backups can run in the next days while the cloning is running.
Should the cloning action be part of another workflow to achieve this ?
Thank you,
Guillaume.

