How to extend the 21-day limit for replication jobs

[Yuya]

Hello,

The VMs are so large that the replication job did not complete within 21 days.
Is there any way to extend this limit?

"If a job is unable to complete within 21 days period, it will be stopped with the Failed status."
https://helpcenter.veeam.com/docs/backu ... ml?ver=120

Regards,
Yuya

[Mildur]

Hello Yuya

I assume your question is for the initial replication.
We have different methods which should help you to lower the time for the initial run. Have you considered replica seeding or mapping?
https://helpcenter.veeam.com/docs/backu ... ml?ver=120

Seeding: The replica job will use the most recent backup in the DR site to create the replica VM. After the restore as a replica VM, changes from the source VM will be synced to the replica VM

Mapping:
You can restore the source VM to the DR site environment. Then configure the replication job to use the restored VM as a source for your VM.

Best,
Fabian

[Yuya]

Hi,

No, the digest calculation is not completed.
VM size is 50TB.
Do you know how to extend the 21-day limit?

[Mildur]

Hi Yuya

I checked our registry key database. There is no key available to allow the replica job to run longer than 21 days.
May I ask what's the bottleneck in the replication session? I assume source if the digest calculation is still running.

Best,
Fabian

[TitaniumCoder477]

I recently had to seed a large replica that was over 10TB. It probably would have run into a similar issue as you given the ratio of IPsec speeds to VM size. The seeding to USB 3.0 for transport to the 2nd site went very well. Given the size you are talking about, you'd probably have to seed to a NAS. So assuming 1GbE throughput, i.e. 125MB/s, you would be looking at approx. 4 1/2 days local backup. Then probably about the same again when seeding from it. Not sure if this is viable, but just wanted to through out some theoretical numbers for you. Seeding definitely works.

Here's the link to my forum post where I was qualifying replica seeding from an Export, which also worked fine: veeam-backup-replication-f2/replica-see ... 91542.html

[tyler.jurgens]

I would assume if Yuya is already doing digest calculation, the seeding is not the issue.

I'm curious what support has to say about this - a 50 TB VM is substantial. It would be interesting to know what is causing the digest calculation to take so long in this environment.