foggy wrote:Do you mean it completes during the next copy interval?
My main backup starts at '22:00' and typically finishes at around '23:30' (for my incrementals Mon to Thurs). I then perform an 'active full' every Friday which takes around 16hrs (finishes at around 15:00 on Saturday).
My copy interval is set as 'every 1 day' starting at '22:30' each night 7 days a week. On the Saturday, the backup copy job reports as running successfully for a full 24hrs (with all VMs processed), but then I get a fail every Monday at the start of the new interval (job starting at 22:30 on the Sunday)... but weirdly the 'fail' says the job has been running for only 22 minutes. It then completes successfully at around 2am *head explodes!*. I usually don't mind... Monday morning when I check the logs, I see the 'fail' but then a 'completed successfully' straight after. But it would be nice not to see that fail!
foggy wrote:As an alternative, you can also use backups produced by your first backup copy job as a source for the second one. For this, you need to point the second one to a backup repository used by the first job to store its backups.
I like the sound of this. So I simply create a 'backup copy job' on the repository I use for my first backup copy? Would this be better than creating two backup copy jobs on my 1st backup server?