After a Hyper-V environment is added in Portal, you can create a backup job that protects VMs in the cluster or standalone host. The backup job specifies virtual machines (VMs) to back up, specifies where to save the backup data, and includes schedules for running the backup job.
Each VM in a Hyper-V environment can only be included in one backup job at a time. If a VM is already included in a backup job, you cannot add it to another job.
For best practices when creating and running backup jobs, see Best practices for backing up Hyper-V VMs. For best practices when seeding VM backups, see Best practices for seeding Hyper-V VM backups.
To create Hyper-V backup jobs, see Add a Hyper-V backup job or Add a Hyper-V backup job by selecting VMs.
When you run a Hyper-V Agent backup job, each VM in the job is backed up as a separate job (task) on the vault. This differs from jobs created using traditional Agents, where each backup job is associated with a single task on the vault. This Hyper-V Agent backup job design provides a number of benefits:
•VMs in a single job can be backed up concurrently.
•Backup processing for individual VMs can be distributed across multiple nodes in a Hyper-V cluster.
•The Hyper-V Agent is scalable in large Hyper V environments.
•A VM can be moved to another job without reseeding (if encryption credentials are the same in both jobs).
•A protected VM can be restored even if its backup job has been deleted.
•If a protected VM has been deleted from your environment, and is no longer associated with a backup job, you can still see the VM in Portal in the protected view, and restore the VM from the vault. After restoring the VM, you can add the VM to a new job with the same encryption password, and continue to back up the VM without reseeding.
All Hyper-V backup data is protected using AES 256 encryption.