When Veeam Backup & Replication removes data for deleted machines from per-machine backup chains, it does not mark the space as available but deletes backup files since they contain data for 1 machine only.It marks the space as available to be overwritten, and this space is overwritten during subsequent job sessions or the backup file compact operation. When Veeam Backup & Replication removes data for deleted machines from regular backup chains, it does not free up space in the backup repository.Veeam Backup & Replication does not remove data for deleted machines from weekly, monthly and yearly backups. The deleted items retention applies only to regular backup chains.At the next synchronization cycle, Veeam Backup & Replication will not remove data for the deleted machine from the target backup repository as the backup chain contains successful incremental restore points for this machine.

During the next 4 days, no successful restore points were created. The backup copy job has created 3 successful restore points - a full backup and two incremental backups. The retention period for deleted machine is set to 3 days.The retention for the backup copy job is set to 7.This approach helps ensure that data for deleted machines can be saved by the GFS retention. The backup chain in the target backup repository does not contain any successful incremental restore points for the deleted machine.Veeam Backup & Replication has not created a valid restore points for the deleted machine for the number of days specified in the Remove deleted items data after field.Veeam Backup & Replication removes data for deleted machine only if two conditions are met: With this option enabled, at the end of every synchronization cycle Veeam Backup & Replication will remove data for deleted machines from backup files in the target backup repository. To avoid keeping redundant data on disk, you can enable the Remove deleted items data after option in the backup copy job settings. You may also exclude VMs from the backup copy job that has already run for some time.īy default, when you remove a machine protected by Veeam Backup & Replication from the virtual infrastructure, exclude a machine from the backup copy job or stop protecting a machine with Veeam Agent, the copied data still remains in backup files in the target backup repository. For example, you may remove some virtual or physical machines or move VMs to another location. After you configure a backup copy job, you may want to change something in the virtual infrastructure.

Veeam 9.5 backup copy best practices