Consider the following best practices when creating and running Hyper-V backup jobs.
Include more than one VM in a backup job
Avoid creating a separate backup job for each VM. The Agent is optimized for backing up multiple VMs concurrently in one job.
Include VMs on the same CSV in the same backup job
Where possible, include VMs on the same CSV in the same backup job. If multiple jobs are needed to back up VMs on the same set of CSVs, stagger the job schedules so that the jobs do not run at the same time.
Avoid reseeds
After the first backup for a Hyper-V VM, the Agent only sends data that has changed since the last backup to the vault. However, under some circumstances, “reseeds” can occur. In a reseed, all data for a VM is sent to the vault even though the VM was previously backed up.
The following list describes situations when backups reseed:
•VM backups in a job reseed if the job is directed to a different vault.
•VM backups in a job reseed if the job’s encryption password changes.
•If a VM is backed up as part of one backup job, and is then moved to a job with a different encryption password, the amount of data sent to the vault is equivalent to a seed backup. If a VM is moved to a different backup job with the same encryption password, the VM backup does not reseed.
•After storage migration, snapshot (AVHD) files reseed. Hard disk VHD(x) files do not reseed after storage migration.