We are using Hyper-V 2012R2 with hyper-v replication. When Veeam starts with a back-up of a VM the hyper-v replication stops and we need to start it again manually. Does anybody has the same problem and perhaps a solution
Hello Erwin and welcome to the community!
The solution is to plan backup and replication jobs schedule accordingly.
I`m curious why do you use Hyper-V replication having Veeam B&R?
Thanks!
You mean to plan the back-up and the replication after each other?. We are using the Hyper-V replication as a service for our costumers, that they have a standby machine with data-lose of 5 minutes. So in a disaster that something happens with the Data-center we can fall-over to another Data-center.
On the moment we are using Veeam only for the back-up of the machines.
Yes, both backup and replication need to take VM`s snapshot so they can not work simultaneously.
I would suggest trying new Veeam feature Remote Replica from Backup so you don`t need to take 2 snapshots and transfer data twice.
Thanks!
Thank's for the answer, but Remote Replica from back-up is not a solution for our problem, this because we want a replication with a interval of 5 minutes. That when we do a fail-over the customer has 5 minutes data lost.
On the moment we use the on-host method for the back-ups when we change this to the off-host method will this be a different ?
As Nikita's already mentioned Veeam triggers a VSS snapshot during backup job so the replication job behaviour that you see comes directly from Hyper-V logic of handling a creation of VSS snapshot when there is a replication already in progress. I suggest you to try taking a VSS snapshot of that VM manually during replication job in order to exclude Veeam from the equation.
Please also take a look at this post describing some benefits of using Veeam replication vs Hyper-V 2012R2 native one.