Exam VMCE v12 topic 1 question 62 discussion

When a retention exception is enabled for a restore point in Veeam Backup & Replication, the data associated with that restore point (like a full backup) will not be automatically removed as part of the regular retention process. The retention exception prevents the backup data from being deleted, even if the backup job's retention policy would normally remove it.

https://helpcenter.veeam.com/docs/backup/vsphere/object_storage_block_generation.html?ver=120

D happens to me in real life issue The exception mentioned in the Veeam article refers to "retention exceptions" where certain restore points are excluded from the regular retention policy. This can happen if specific settings or conditions are applied that prevent these restore points from being deleted, even if they exceed the standard retention period. For instance, flagged restore points might be retained for compliance or recovery purposes beyond the usual retention timeframe.

Veeam Backup & Replication treats synthetic full backups as regular full backups. As well as any other full backup file, the synthetic full backup file resets the backup chain. All subsequent incremental backup files use the synthetic full backup file as a new starting point. A previously used full backup file remains on disk until it is automatically deleted according to the retention policy.

sorry, A is correct, from the point of view of backups not deleted for a long time there is no difference between active and syntetic full backups.

no comments

https://helpcenter.veeam.com/docs/backup/vsphere/backup_job_advanced_maintenance_vm.html?ver=120 https://helpcenter.veeam.com/docs/backup/vsphere/retention_deleted_vms.html?ver=120

I think it's C

When it is scenario A, then one full backup would not be the only backup that remains undeleted.

no comment