replication from backup source resume upon failure?

[isolated_1]

Case # 05851796

If a VM in a replication job configured to use source backup files fails/errors because it didn't have enough time to finish before the backup job runs, will the replication job resume where it left off and continue to look for new data blocks to replicate over to make up the initial full? I've read that this is how backup copy jobs behave and I've seen it in action as well.

Some VM's we are replicating using the backup files as the source is too large to complete within one replication cycle. Obviously, when the backup job runs, the replication job will stop as the backup job has a higher priority. Rather than using replica seeding and mapping, we're actually okay with continuing to let the replication continue for as long as it takes to eventually complete if it behaves similarly to backup copy jobs in that it is smart enough to track the status and only transfer the required data upon each run.

[HannesK]

Hello,
I remember that only the backup copy job has the feature for the initial copy to resume. So your idea won't work and on needs to finish the replication before sending new backups.

Which transport mode do you use for the replication restore (maybe the problem can be solved by making the replication faster)? HotAdd would probably be the fastest (if you are not using it already).

Best regards,
Hannes

[isolated_1]

Hello Hannes,

So good news on our end. We left the replication job going as is. It actually completed after 2-3 days of failing. It is now replicating normally for the incremental and takes a lot less time to complete. Basically, this is what we were experiencing with our backup copy jobs over the Internet to a third party datacenter.

We've uploaded a screenshot to the Veeam support case ID. It shows that the replication job has failed for three nights in a row. On the fourth night, the job was completed after 9 hours. On the subsequent two nights, the job was completed in less than 30 minutes.

At the moment, the replication job is using backup files as the source. This is due to us not wanting to cause any unnecessary impact on the production workload via snapshots.

Are you able to help us clarify if this is expected behavior regarding the 'replication on resume' feature? The replicated VM also powers on without issues. Thanks!

[HannesK]

Hello,
yes I will verify and ask to update the documentation accordingly (this can take some time, because currently the focus is on getting everything ready for V12).

Thanks for brining it up,
Hannes

[HannesK]

Hello,
it's confirmed as feature. "resume" works for the first full and also for incremental runs if the snapshot still exists.

Best regards,
Hannes

[isolated_1]

thanks hannes! you guys are the best!