

The backup copy job defines when, what, how and where to copy. To copy backups, you need to configure backup copy jobs. The backup copying process does not affect virtual and physical infrastructure resources, does not require creation of additional VM snapshots or VSS snapshots and does not produce load on machines whose backups are copied.īackup copy is a job-driven process. When the backup copying process starts, Veeam Backup & Replication accesses backup files in the source backup repository, retrieves data blocks for a specific machine from the backup file, copies them to the target backup repository, and composes copied blocks into a backup file in the target backup repository. If it was recreated (all restore points have been deleted and created anew), you must create a new backup copy job with a new chain of backups. In this case, make sure the source chain for the backup copy job was not recreated.

Backups created with Veeam Backup for RHVĬonsider the following for copying backups created with Veeam Backup for AWS, Veeam Backup for Microsoft Azure or Veeam Backup for Google Cloud :.Backups of VM instances created with Veeam Backup for Google Cloud.Backups of Microsoft Azure virtual machines created with Veeam Backup for Microsoft Azure.Backups of Amazon EC2 instances created with Veeam Backup for AWS.

File share backups created with Veeam Backup & Replication.Backups stored in an HPE StoreOnce backup repository.Backups of Oracle, SAP HANA and Microsoft SQL Server databases created with Veeam Plug-ins for Enterprise Applications.Backups of Nutanix AHV virtual machines created with Veeam Backup for Nutanix AHV.Backups of virtual and physical machines created with Veeam Agent for Microsoft Windows, Veeam Agent for Linux, Veeam Agent for Mac, Veeam Agent for Oracle Solaris or Veeam Agent for IBM AIX.

