How does this work with for example StoreOnce Catalyst? If the free space is never freed, the Catalyst housekeeping jobs will never have an opportunity to un-reference the blocks and delete no-longer-used unique blocks?If both conditions are true for some VM, Veeam Backup & Replication removes data for this VM from the backup. When Veeam Backup & Replication removes data for deleted VMs, it does not free up space on the backup repository. It marks the space as available to be overwritten, and this space is overwritten during subsequent job sessions or the backup file compact operation.
-
- Expert
- Posts: 176
- Liked: 30 times
- Joined: Jul 26, 2018 8:04 pm
- Full Name: Eugene V
- Contact:
Retention policy for deleted items behavior
From the documentation:
-
- Veeam Software
- Posts: 21069
- Liked: 2115 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Retention policy for deleted items behavior
It is basically the same as for any other repository, e.g. NTFS - a block marked as free inside a backup file is not considered free from a file system perspective. It still contains data until it gets reused by Veeam B&R or entire backup file is deleted (such blocks will not be copied over to the new full backup file during synthetic full or compact operation). On Catalyst though, you must use per-VM backup chains, so when you remove a VM from backups or it is not backed up anymore, the entire backup chain for this VM should be deleted after the specified amount of days.
Who is online
Users browsing this forum: Google [Bot] and 184 guests