Skip to main content
  • EN

Guys

I am migrating my VMs from an old cluster to a new one. NO problem so far - 7 out of 8 VMs moved. Veeam continues to back them up. Great stuff.

The last one has a large VHDX drive - 4Tb

What will happen when the backup job tries to back that up whilst Hyper-V manager is moving the machine? With the old (1Gb) NICs in the source cluster this might take a while to copy (7h ish).

Does the backup job just fail (becasue the machine won’t quiesce, or perhaps because there is already a snapshot created by the move process) or will it get stuck in some horrible sort of a loop and eat up all the storage on the cluster with checkpoint files?

I ask because, back in the day (when I was new to Veeam), I did try to backup a machine that was the target of DFS-R and the results weren’t pretty. I realise this is a different scenario but I just want to be sure!

 

B.  

I would disable the job until the migration has finished. That way you are minimising any risk to the live VM.

I Agree with Mark, as the copy / move action locks the original file. Veeam cannot get an exclusive lock.
But just to be sure, disable the job.

In theory it should still back up during a move as I know in my homelab with VMware I was running backups then VMs started moving around but still backed up, just took longer.

But I would agree with the recommendations above to disable the job until the move is complete.

 
 
 

Excellent.

 

Disabling the job is what I thought would be the way to go - but it’s always good to talk!

 

Thanks guys.

 

B.

Yeah, I’d always err on the side of caution with this in order to prevent making a mess that you then have to figure out how to clean up and risk data loss/corruption/duplication.  

Comment


Terms & Conditions