"Copy interval has expired", behavior at next run?

[jgar]

Hi,

running a backup copy job to offsite location, with interval set to 1 day, starting at 00:00
On average, 50 to 200 GB are transferred every day, taking just a few hours.

Among the VM's processed, the biggest one is a Windows 2012r2, with a dedup-enabled volume of 1,2TB
From time to time, we presume that as a result of some dedup-related scheduled tasks (optimization and garbage collection for ex.), a massive amount of blocks can be changed suddenly on that volume.

The most extreme sample that we had was last weekend, with around 680 GB of change for that one VM. (looking at the report of the normal backup job).
So in this case, the backup copy job was unable to complete in the allowed 24h interval, and failed with "Copy interval has expired".
And as expected the last restore point for that VM in the backup copy repo is marked as "incomplete".

Now, in regard to that particular VM and to the few hundreds of GB already copied until copy interval expiration:
Will the next run of the job be able to do some kind of resume, or will it be a full start over since last previous good point?

Thanks,
JG.

[DavoudTeimouri]

As my experience, the next start will be full and machine and last completed backup will compare.
Also taking full backup is recommended.

[veremin]

Will the next run of the job be able to do some kind of resume, or will it be a full start over since last previous good point?

It will resume where it left off. Missing blocks from previous interval will be copied along with new ones.