We have a large copy job with WAN accelerator which get cancelled while the run time is not yet ended (set to 9 days, cancelled within 1 day). Looking at the job log it states cancelled by user, but we are sure nobody did. The debug log shows it's cancelled right on the scheduled time of it's backup job.
Could this be because the backup job is reversed incremental and the source file needs to be released from the copy job so the backup job may start? Would switching to forward incremental solve this?
Regards,
Bastiaan
======================================================
Veeam ProPartner, Service Provider and a proud Veeam Legend
Exactly, the backup copy job pauses its activities when the regular backup job starts and continues after it is finished. This is not the case with forward incremental mode, though.