Skip to main content

We recently did some rebalancing on our Hyper-V cluster and I’m wondering what actions I need to take in Metallic if any. Most of the machines that were moved are still using the hypervisor and VM group that they were previously on. I tried moving one of the smaller low priority machines to the new hypervisor as a test and it appears that it had to do a full backup after the move, but that may be my fault because I couldn’t find any documentation for the process and had to wing it. One of the machines still using the old hypervisor is the file server so I would really prefer to not have to do another full image on it again.

 

My main questions are:

  1. Do they need to be moved to the corresponding hypervisor?
  2. If so, how do I do that without causing a full image backup?
  3. If not, are those backups still using the previous host in some way?

Hi @Patrick Kelley 

 

As long as the new node is a part of the Hyper-v Cluster and the VMs reside on cluster shared volume, the backups will continue as before the Cluster Rebalancing.