Skip to main content

Nutanix Move + VEEAM

  • November 24, 2025
  • 3 replies
  • 60 views

Hi Everyone,

 

Just throwing this out there and was wondering how others have experienced this.

We use VEEAM as our backup solution and were having some issues trying to move from ESXI to AHV. Every time we started a move using Nutanix Move we’d have an error about CBT not being enabled. Our resolution? Disabling CBT (yes disabling not enabling) using the following PowerCLI script!

After we ran the script the move completes succesfully! (Make sure to run it before creating your migration plan)

No clue if anyone has the same issues as us but if you do this might be a solution!

Import-Module VCF.PowerCLI
Connect-VIServer -Server YOUR.VCSA.SERVER
$vm="YOUR.VM.NAME"
$vmtest = Get-vm $vm| get-view
$vmConfigSpec = New-Object VMware.Vim.VirtualMachineConfigSpec
$vmConfigSpec.changeTrackingEnabled = $false
$vmtest.reconfigVM($vmConfigSpec)

 

Regards,
Westy Weijts
Den Hartogh Logistics

3 replies

BartDonders
Forum|alt.badge.img+3
  • Outrider
  • November 25, 2025

Hi Westy,

I assume that after disabling CBT, it is enabled by Move again?


  • Author
  • Voyager
  • November 25, 2025

Hi Westy,

I assume that after disabling CBT, it is enabled by Move again?

Hi Bart,

Indeed. Move enables CBT again and the move completes succesfully. It feels very double to disable it via PowerCLI and have Move enable it again but this has worked for us!


Chris-32
Nutanix Employee
  • Nutanix Employee
  • November 26, 2025

Veeam is specifically called out in the Move documentation with respect to CBT: https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Move-v6_0:top-vm-backup-during-migrations-c.html