Backup Copy Jobs schedule as chain

[d-con.net_thomas]

Hello Everybody.

Is there a specific reason why it´s not possible to start backup copy jobs one after another as a chain?

It would be very helpfull for our usage.

Thank you and BR.

Thomas

[david.domask]

Hi Thomas,

Backup Copies work within the Backup Copy Window and follow the workflow depending on if you use Immediate (all points processed) or Periodic (most recent point processed) mode. Basically, Backup Copy waits until its selected backup window, then will begin processing the source backups and copying the relevant points. This isn't really a "one-off" job run, it's a continually running process to ensure the backup copies are created as soon as allowed by the backup window.

Consider staggering the backup windows for your backup copy jobs to reach the same outcome as job chaining.

May I ask what the use case for job chaining in your scenario as opposed to letting the backup copies run normally or with restricted backup windows?

[d-con.net_thomas]

Hi David.

Thank you for your reply.

We are now using pereodic backup copy jobs which are chained to the backup jobs. Because of the backup copy job engine was renewed in version 12 i can use pretty the same job schedule options as for the backup jobs. And when the backup copy job has finished it´s stopped and is not idle as in the older Veeam versions.
That´s why it´s not clear for me and we can´t define the second backup copy job should start when the first one is finished in a chain.

BR

Thomas