Removing Backups from Capacity or Archive Tier
To remove moved or copied backups from capacity or archive extent, use the Delete from disk feature, as described in Deleting Backups from Object Storage Repositories.
Consider the following:
- When removing offloaded backup files from the backup chain that was created with the per-machine method, the associated blocks of data will be removed from the capacity or archive extent altogether.
For more information about per-machine backups, see Per-Machine Backup Files.
- When removing offloaded backup files from the backup chain that was created as a single storage backup file, then nothing will be removed until either of the following occurs:
- All the VMs were removed from the backup.
- The backup itself was removed.
- Immutable backups cannot be removed.
For more information, see Immutability.
- If the capacity or archive extent has been put into the maintenance mode, the removal of data from such a repository is not be possible until it is switched back to normal.
For more information, see Switching to Maintenance Mode.
- [For capacity tier] When backup is removed from the capacity extent, associated indexes will be removed as well.
For more information, see Indexes.
- During data removal, not only will blocks be removed, but also the entire folder structure starting from the repository folder (<backup_id>) will be completely purged.
For more information on how Veeam stores data in the capacity extent, see Capacity Extent Structure.
- If backup files with metadata that are located on your extents have been removed locally in any way other than by using the Deleting from Disk feature, Veeam will not be able to synchronize the backup chain state with that of the capacity or archive extent. Therefore, the offloaded blocks of data will continue to remain in cloud storage. To remove such blocks, use your cloud platform abilities.