The "merge" operation in this context refers to the process of updating metadata. Specifically, at this point, are we creating a new checkpoint, recording information about the restore points it consists of , and updating the references for these restore points (indicating that the oldest full now consists of specific blocks, etc.).But in my Backup Copy Job log there is an action "Full backup file merge completed successfully" and It takes some time. So does Veeam do merges or not?
Correct, the immutability prolongation occurs once in generation period, once in 10 days by default.And thanks to Block Generation, the extension is only done once every 10 days?
Exactly. If objects are not protected by immutability, you won't be able to restore from them once they are deleted. However, with immutability in place, even after restore points are removed from the UI according to the retention period, you can still revert to the previous backup chain state and restore from them during the immutability and generation periods. This is where the concept of actual retention comes into play.If the objects are not immutable, the retention policy deletes them and I cannot restore them.
Correct.In various tests, I manually deleted data after immutability ended. Retention Policy deletes Restore Points at least from the configuration. But on object storage, it waits for an immutability period + Block Generation longer?
Correct.Is it correct, that objects will be deleted automatically when Immutability ends?
Immutable restore points will be removed from the UI once their retention period expires, but they will remain in the object storage until the end of the immutability and generation periods.And in the case of an immutable backup, Veeam will not attempt to delete it and therefore no error will occur?
It is a cloud_backup_id that can be obtained from "backup.model.backups.directbackupinfos" table.Is the folder name really the backup ID?
Thanks!
Statistics: Posted by veremin — Feb 13, 2025 11:58 am









