text: Veeam with two Hyper-V hosts - how best to use? - Veeam R&D Forums
  Veeam with two Hyper-V hosts - how best to use?
  Joined: Nov 05, 2020 10:25 am
  Full Name: Chris House
  Post by CH79 » Apr 26, 2021 1:43 pm this post
  We have two on-premises Hyper-V hosts. One host runs the live VMs and we use Hyper-V Replica to replicate the VMs to the second host.
  Veeam Backup and Replication is currently installed on host 1 and this backs up the VMs to a NAS as well as to the cloud via a separate copy job.
  If/when we fail over to host 2 (say for maintenance purposes etc.) and run the live VMs from there how would we go about using Veeam on the second host and doing our backups from there instead?
  Re: Veeam with two Hyper-V hosts - how best to use?
  Post by HannesK » Apr 26, 2021 2:19 pm this post
  backing up from a failed over machine would result in a new backup job / new full backup.
  Post by CH79 » Apr 26, 2021 3:50 pm this post
  So if we failed over to the second host for a couple of days say for maintenance purposes, Veeam on the second host would treat the replicated VMs as new files and do new full backups of them? What about the cloud backups?
  Then when we revert back to the first host it would start the whole process over again?
  Post by HannesK » Apr 26, 2021 4:19 pm 1 person likes this post
  a replicated VM is a different VM. different VM = different job. yes
  If you failback to the original VMs, then the backups of the original VMs will continue where they stopped. As everything is still the same like before failover, cloud backups also continue (backup copy jobs to cloud connect or SOBR with capacity tier)
  Post by PTide » Apr 26, 2021 4:31 pm this post
  Unless I am missing something about your use-case, it seems that you could stick with backing up only the replica VMs.
  Post by CH79 » Apr 27, 2021 2:44 pm this post
  HannesK wrote: ↑Apr 26, 2021 4:19 pm a replicated VM is a different VM. different VM = different job. yes
  Thanks. Understand it now.
  I think we will continue as at present with Veeam just on the primary host. We'd fail back to the primary host after maintenance anyway so it makes sense to do things that way.