• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

why does Storage vMotion break CBT?

Thuleman

Supreme [H]ardness
Joined
Apr 13, 2004
Messages
5,833
Ultra annoying, backups work fine with CBT enabled, then you svMotion the VM and on the next backup run CBT fails and needs to be reset. In order to reset it the VM has to be power cycled a couple of times.

Is svMotion not a block based move? If the source and destination blocks are identical, why does every backup software under the sun drop svMotioned disks from CBT?

What am I missing?
 
This is totally news to me - don't have that problem here with VDP-A or Veeam... :confused:

What version of ESX are you on, and what backup solution? What type of device are they stored on (NFS/Block)?
 
Heh, the sweeping generalization was posted for dramatic effect. ;)

This is on 5.1.0 1612806, block storage.

I migrated a whole bunch of VMs off of a SAN to do maintenance on that array and the next thing is that both Veeam and Nakivo dropped CBT on the svMotioned disks. Meaning that I am currently running identical backup jobs using both Veeam and Nakivo and both experienced this issue.

I don't actually recall this being a frequent problem in the past, though when I was using Veeam only there certainly have been cases in the past where CBT was dropped and had to be reset, usually after svMotion. Most recently (couple of months ago, different ESXi patch level) this even happened for a single disk VM without that there was an svMotion event.
 
Are you backing the same guests up with two different backup solutions?
 
Are you backing the same guests up with two different backup solutions?

Well no, identical backup jobs from a source/destination perspective, not backing up the same VM with two different solutions.

Datastore1 holds VMs which are either backed up by Veeam or by Nakivo to Datastore2. All VMs on Datastore1 were moved to Datastore3, which resulted in broken CBT for all involved VMs regardless on whether they were backed up by Veeam or Nakivo.

Resetting the CBT per KB article fixed the issue for both backup solutions. I googled around for this a bit last night and it seems like the common perception is that this happens rarely enough to just reset CBT and not burn time on figuring out why it's actually happening.
 
Ok. Interesting. I've not had it happen with any of my migrations, but lord knows I don't do as many as some places. I'll do some digging to see what I find.
 
What are the two datastore types you migrated between? Array to local disk or to NFS?
I saw the datastore 1,2,3 listed but want sure about type of storage.

I could be mistaken but I remember CBT breaking between SAN and local storage migrations. Maybe that was just the incremental backup ability?

Guess I need to hit the Google.

Nicholas Farmer
 
I've not experienced issues with vMotion breaking CBT, but I have had extensive issues with CBT & virtualized backups. I don't think its just the combination doing it, but just CBT sucking overall.
 
Nice! Thanks ND40oz.

I knew I saw that KB but couldn't find it with some quick google thrashing.

Thuleman, let us know if you mean only incremental or all CBT functions stop until you manualy reset it.

Nicholas Farmer
 
while this is true, it shouldn't require manual intervention...

Yeah, I've only had to manually intervene once, usually you just wait for the non-CBT backup to run and then it resumes using CBT.
 
Nice find ND, thank you, I bumbled around Google for a bit and missed the KB article.

Thuleman, let us know if you mean only incremental or all CBT functions stop until you manualy reset it.

As far as I could tell it was only the backup software that complained. Those are indeed incrementals.
 
Back
Top