Backup Move

Veeam Backup & Replication allows you to move all backups of a backup job to another repository or to move specific workloads and their backups to another job.

Moving backups to another repository can be helpful if you are running out of free space on a repository and want to move all backups created by a backup job to another repository, target the backup job to this repository and continue the backup chain.

Moving workloads and their backups to another backup job can be helpful if you want to separate one backup job into multiple backup jobs or if you want to change backup settings for specific workloads. Also, you want to continue the existing backup chains for the workloads.

How Moving to Another Repository Works

When moving backups to another repository and targeting the job to this repository, Veeam Backup & Replication performs the following:

  1. Disables the backup job.
  2. Copies backup files to a new location.
  3. Targets the backup job to the new location.
  4. Deletes source backup files.
  5. After the successful move, Veeam Backup & Replication enables the backup job. The enabled backup job continues the backup chain for the existing and moved backups.

Note

The described algorithm is common. Nuances, requirements and limitations are described further in this section.

How Moving to Another Job Works

When moving backups to another job, Veeam Backup & Replication performs the following:

  1. Disables the source and target jobs.
  2. [For Veeam Backup & Replication versions prior to 12.1 (build 12.1.0.2131)] Copies backup files of selected workloads to the repository where the target job saves backups.
  3. [For Veeam Backup & Replication version 12.1 (build 12.1.0.2131) and later] If backups are moved within one repository without immutability, Veeam Backup & Replication invokes the native move method of the file system. This applies if the repository is Windows, Linux, CIFS, NFS, deduplicating storage appliance or a scale-out backup repository of one of the listed types. In other cases, Veeam Backup & Replication copies backup files of selected workloads to the repository where the target job saves backups.
  4. Excludes the selected workloads from being processed by the source job.
  5. Includes the selected workloads to be processed by the target job.
  6. After the successful move, Veeam Backup & Replication enables the source and target jobs. The target backup job continues the backup chain for the existing and moved backups.

Note

The described algorithm is common. Nuances, requirements and limitations are described further in this section.

Requirements and Limitations

This section describes the requirements and limitations for different types of jobs and different types of repositories where backups can be stored.

Common Considerations

Consider the following:

  • You can move individual workloads and their backups only if backups are per-machine backups with separate metadata files and only to repositories with the Use per-machine backup files check box enabled.
  • You can move backups between repositories with the Use per-machine backup files check box selected and not selected. However, the move operation does not change the backup chain format (single-file backup, per-machine backup with single metadata file or per-machine backup with separate metadata files). The job will continue the backup chain of the original backup chain format. If you want to change the backup chain format of the chain, use the detach from job operation. For more information, see Upgrading Backup Chain Formats.

[For moving to object storage repositories] You can move only per-machine backups with separate metadata files.

  • After you move workloads and their backups between jobs, you must adjust the guest processing settings for the moved workloads. After move, Veeam Backup & Replication uses the default guest processing setting. For more information on guest processing settings, see Guest Processing.
  • You cannot move a workload and its backups to a job that already processes this workload.
  • You cannot move backups of workloads after they were migrated between standalone Hyper-V hosts that are not a part of one cluster or SCVMM server registered in Veeam Backup & Replication. That is because Veeam Backup & Replication considers the migrated workload as new and the "old" workload as deleted. To create backups of the migrated workload in another repository, add the migrated workload to the dedicated backup job. After that, Veeam Backup & Replication will create full backups for these workloads.
  • You cannot move backups from encrypted jobs to unencrypted jobs and vice versa.
  • You cannot move backups imported without the metadata (.VBM) file.
  • You cannot launch the restore operation for backups being moved at the moment.
  • You cannot move backups from an HPE StoreOnce repository used as a target for backup copy for HPE StoreOnce repositories.
  • You cannot move backups created by backup copy jobs in the legacy periodic copy mode. To move backups, you first need to upgrade the backup format as described in section Upgrading Backup Chain Formats.
  • After you move backups between backup copy jobs, Veeam Backup & Replication does not include and exclude workloads from the backup copy jobs. You should do that manually.
  • You cannot move backups created by Veeam plug-ins for Enterprise applications, Veeam Cloud Plug-ins (Veeam Backup for AWS, Veeam Backup for Google Cloud, Veeam Backup for Microsoft Azure), Veeam Backup for Nutanix AHV, Veeam Backup for OLVM and RHV and Kasten K10.
  • You cannot move backups created in Veeam Cloud Connect repositories. For more information on Veeam Cloud Connect repositories, see the Cloud Repository section in the Veeam Cloud Connect Guide.
  • To use the move to another repository functionality and move backups to an object storage repository, check that defragment and compact full backup file, reverse incremental backup method and synthetic full backup are disabled for the job. As an alternative, you can use the move to another job functionality and move backups to a job already targeted to an object storage repository.
  • Before moving workloads and their backups to a deduplicating storage appliance, Veeam Backup & Replication checks whether such move can damage the backup chain. If so, Veeam Backup & Replication prohibits the move operation. After Veeam Backup & Replication completes the move operation, it checks that the target backup job is configured correctly. However, you must change the settings manually. You can find which backup settings need to be changed in the move session or in this Veeam KB article. For more information on how to view session statistics, see Viewing Job Session Results.
  • You can move VMware Cloud Director backups of a whole job or individual vApps. You cannot move backups of VMs.
  • If you move workloads and their backups between jobs linked to the same tape job, the tape job continues to create incremental backups within the existing backup chain. Otherwise, the tape job will create an active full backup for the moved workloads.
  • Traffic throttling is not supported for backup move operations.

Backup Jobs with Linked Backup Copy Jobs

If you move workloads and their backups from a backup job which is linked to a backup copy job, the following applies:

  • If the source and target backup jobs are linked to backup copy jobs, Veeam Backup & Replication also moves backups and workloads between backup copy jobs. Note that Veeam Backup & Replication performs move only if each backup job is linked to one backup copy job only. For example, Backup Job 1 processes VM1 and VM2 and is linked to Backup Copy Job 1. Backup Job 2 processes VM3 and VM4 and is linked to Backup Copy Job 2. You move VM1 and its backups to the Backup Job 2. Veeam Backup & Replication will also move the VM1 and its backups from Backup Copy Job 1 to Backup Copy Job 2. As a result, Backup Job 2 and Backup Copy Job 2 will process VM3, VM4 and VM1.

If a backup job is linked to multiple backup copy jobs, you need to move workloads and backups between the backup copy jobs manually. To do that, use the move to another job operation as described in section Moving Backups. If you do not move workloads between backup copy jobs, the backup copy job linked to the target backup job will create active full backup copies for the moved workloads.

  • If the source backup job is still in progress, the move operation fails.
  • Before moving backup copies, Veeam Backup & Replication waits till the source move backup process finishes successfully. Only then, Veeam Backup & Replication disables the linked backup copy job and moves backup copies.

Log Backups

If you move workloads and their backups from a backup job for which log backup is configured, the following applies:

  • Veeam Backup & Replication moves log backups along with workloads.
  • Veeam Backup & Replication disables the log backup jobs gracefully before moving log backups.
  • [For SQL server Always On availability groups] You cannot move individual nodes from a job.
  • [For Oracle Data Guard] You must move all servers from the job. If you move only one server, application item restore stops working. To repair the application item restore functionality, you will need to move the server back to the original job.
  • If guest processing is disabled in the target job, log backups are moved, however they will not be processed by the target job. To process log backups, make sure that guest processing is enabled for the target job as described in section Specify Guest Processing Settings.

Backups with GFS Flags

If you move backups from a backup or backup copy job where long-term (GFS) retention is configured, the following applies:

  • When you move all backups to another repository, Veeam Backup & Replication preserves all backups with GFS flags.
  • When you move a workload and its backups to another job, Veeam Backup & Replication starts to retain backups according to the settings configured in the target job. Veeam Backup & Replication deletes all GFS backups that do not comply with the retention policy in the target job. For example, if yearly backups are not configured in the target job, Veeam Backup & Replication will remove them after the move operation finishes.

Agent Backups

For more information on moving Veeam Agent backups, see the Moving Backups section in the Veeam Agent Management Guide.

Immutable Repositories

If you move workloads and their backups from a repository for which immutability is enabled, the following applies:

  • During the move operation, Veeam Backup & Replication copies the whole backup chain. After the move operation finishes, original backups stored in the immutable repository are moved to the node with the (Orphaned) postfix. Other original backups are deleted.
  • Veeam Backup & Replication retains backups moved to the (Orphaned) node according to the retention period specified in the job from which the backups were moved. If the retention period is shorter than the immutability period specified in the repository settings where the backups were stored, Veeam Backup & Replication sets the retention period as equal to the immutability period.

If the retention period is set in days, Veeam Backup & Replication deletes a backup after its retention period ends. If the retention period is set in restore points, Veeam Backup & Replication does not delete backups. You can delete these backups manually after the retention period ends.

Scale-Out Backup Repositories

If you move workloads and their backups from a scale-out backup repository, the following applies:

  • Veeam Backup & Replication moves backups only from the performance tier. If you want to move data from the capacity tier, you must first download it to the performance tier. For more information, see Downloading Data from Capacity Tier.
  • Veeam Backup & Replication does not support moving backups between extents of a scale-out backup repository. To learn how to manage backups within the scale-out backup repository, see Scale-Out Backup Repositories.
  • Backups stored in the capacity and archive tiers are moved to the node with the (Orphaned) postfix. The backups are retained according to the retention settings of the job from which the backups were moved. If the retention period is set in days, the Veeam Backup & Replication retains the backups according to the configured retention and deletes the backups from the repository after the retention period ends. If the retention period is set in restore points, Veeam Backup & Replication leaves backup files in a backup chain. The minimum number of backup files left equals the current retention period. You can delete these backup files manually as described in section Deleting Backups from Disk.
  • Veeam Backup & Replication does not move backups from extents in the Maintenance mode. These backups are deleted once the extents exit the Maintenance mode.

Related Topics

Page updated 4/15/2024

Page content applies to build 12.1.2.172