Restorepoint for BackupCopy jobs too old??

[hgrams]

Hi,
We have the problem at a new customer that some VMs were last backed up over a year ago. These VMs are now also to be copied with 2 Restorepoints into the Cloud. When I select these VMs in the BackupCopy job, they are initially displayed with its volume, after a few seconds, the volume goes to zero, and when the job is run, only the VMs are copied to the cloud, which the restorepoints are younger, i.e. 1, 2 or 3 days.

My question: Is there a max. days limitation for backup copy jobs in Veeam from which a restore point is no longer considered?

Thanks in advance
Harald

[Shestakov]

Hi Harald,
There is no such a thing that if restore point is old it will not be copied. In your case the target repository may have same restore points, so backup copy job doesn`t process it.
Thanks!

[hgrams]

Hello Nikita,

Thanks for your info. Then something is wrong. We are during a proof of concept process, everything is new regarding backup copy jobs and in the cloud.
For your information, I created a support case "02215044".

Best regards
Harald

[Shestakov]

In this case it`s better to keep investigating with the support team as behavior looks unexpected.
Thanks!

[hgrams]

Just for interest, the limit for the BackupCopy job window is max. 100 days into the past. More can not be set in the BackupCopy dialog.

[foggy]

Most likely those restore points were just too old and didn't fit into the specified backup copy job interval, hence skipped. What copy interval setting does the job have?

[hgrams]

The customer wanted to copy VMs, which had the last restore point more than a year ago. Whether that makes sense is a completely different question. We have now explained to him that older than 100 days is not possible. He accepted and good.