Broken backup chain with datastore copy

[filippoAdb]

Case #08140997
I have a backup job which uses a local HP storeonce repository. Then a backup copy job (datastore copy) creates the same backup files on a remote HP storeonce.
The retention for datastore copy doesn't consider full or incremental backups, it deletes files older than the fixed number of days, so the oldest restore point on remote repository may be an incremental backup. I can select it for restore but the operation clearly fails saying "Full backup file for this object is not present in the backup repository". From the user point of view Veeam is telling that there is a valid restore point, but if you select it you find out that the backup chain is broken, so it is completely useless and gives you a false security.

[david.domask]

Hi filippoAdb,

Yes, I see your point, but I was under the impression that such points would be marked as invalid in the Properties section, are you seeing differently? Basically my expectation is we should flag such points to avoid that "surprise" exactly as you found, so if you're seeing differently, let me know and will check internally on expected behavior.

The Catalyst Copy retention is a bit different, yes, and I find that this section explains how to best plan for the current implementation.