This process includes several stages.Ī copy job restarts every time at the defined Copy every interval setting (default is 12:00 AM daily) and monitors for new restore points of the selected VMs to appear in the specified sources. Backup Copy Job Schedulingīy design, a backup copy job is a process that runs continuously. Important Note: Jobs with WAN acceleration enabled will process VMs sequentially, while jobs using direct mode will process included VMs in parallel according to free task slots availability on backup repositories. Limitations of backup copy jobs are described in Veeam Backup & Replication User Guide at. The backup copy process will resume from the last full data transaction during the next synchronization interval. This might be caused by precedence of the backup task over the backup copy task. If a backup copy job cannot process all requested VMs before the end of an incremental execution interval (by default 24 hours), the job will still create a backup file on the target backup repository (or multiple files if per-vm chains have been enabled), but some VMs will be left inconsistent or unprotected. If you plan to use Grandfather-Father-Son (GFS) retention, refer to the “ GFS Retention Policy” section for details.īackup copy jobs file chains layout will depend on the repository option: "Per VM backup files" will generate one file chain per each VM, otherwise a chain will be generated per each job. Once created, a backup copy job will immediately start processing the latest existing restore point for all VMs included in the job, as long as it has been created less than one synchronization interval before the start of the backup copy job.īy default, Veeam Backup & Replication keeps 7 restore points on the target backup repository in case of simple retention policy (see the “ Simple Retention Policy” section of the User Guide for details). The folder has the same name as the backup copy job. You can store VMs from multiple backup jobs in the same backup copy job, or you can select a subset of VMs from a bigger backup job as source if you do not want to backup all VMs to the backup copy job destination.Įvery backup copy job creates its own folder on the target backup repository and stores its data in this location.
The second chain is independent from the first chain and adds therefore an additional level of protection. Backup copy jobs read specific VM restore points from backup files and store them as a new backup file chain on the destination. Instead of just copying backup files to a second destination, Veeam uses a more intelligent and secure way of bringing restore points to a second backup target.
Sizing Targets for WAN Accereration Relationship Protecting Veeam Backup & Replication Configuration
Veeam Backup & Replication Best Practices
0 kommentar(er)
