This is an archive version of the document. To get the most up-to-date information, see the current version.

Removing Backups from Capacity Tier

To remove moved or copied backups from the capacity 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-VM method, the associated blocks of data will be removed from the capacity extent altogether.

For more information about Per-VM backups, see Per-VM 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:

For more information, see Immutability.

If the capacity extent has been put into maintenance mode, the removal of data from such a repository is not be possible until it is switched back to normal.

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 (<repository_folder_name>) 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 extent. Therefore, the offloaded blocks of data will continue to remain in cloud storage. To remove such blocks, use your cloud platform abilities.