VEEAM Agent for Hyper-V

[mphaneuf]

My company recently took on a new client and I am working on installation of Agents on their server. However, their server also has two VMs in Hyper-V. Do I need to install agents on both of the Hyper-V VMs or will the VMs get encapsulated if doing an entire backup of the host machine with an agent?

[Gostev]

The first approach is against best practice, and the second one is simply unsupported for Hyper-V VM backup.

The recommended way to do this is to create an image-based Hyper-V VM backup job with Veeam Backup & Replication.

However, if you're trying to avoid having a backup server due to the size of your client, then the first approach is the way to go.

[mphaneuf]

I should put a copy of Veeam Backup and Replication on the host then and then perform a backup of the VMs. Then use the Agent to send it to the Cloud Connect repository?

[wishr]

Hi Matthew,

I would recommend installing VBR separately - on a dedicated virtual (VM) or physical server at the customer side. This way the customer won't lose their backup server if the host dies for whatever reason thus would minimize the recovery time (RTO). Then, you may back up VMs using either VM backup or Agent backup (managed by backup server) capabilities, whichever fits best with their applications. In both of these scenarios, they will be able to choose Cloud Connect as a target for backups.

If the installation of a backup server at the customer is not desired, you may install standalone Agents on each VM and perform a backup to Cloud Connect.

Thanks