Error Migrating from VMware to HCI

LuckLuciano Lv1Posted 21 Jun 2024 11:54

When I try to migrate from VMware I have thir error:

Failed to reset reset CBT. Failed to enable CBT. Please check network connection or status of VMware vCenter server.

Any idea ?

thank you !
Luciano

By solving this question, you may help 543 user(s).

Posting a reply earns you 2 coins. An accepted reply earns you 20 coins and another 10 coins for replying within 10 minutes. (Expired) What is Coin?

Enter your mobile phone number and company name for better service. Go

LuckLuciano Lv1Posted 21 Jun 2024 12:00
  
If I disable CBT I have this error: Error copying disk data.
fuadmahbubun Lv1Posted 21 Jun 2024 21:53
  
hi, try migrate by using clone VM to HCI. some case will remove CBT during cloning VM.
i ever do with this methode.

if still failed, try clone and after running 5 or 10 % cancel the task. then clone again until finish.
Enrico Vanzetto Lv3Posted 21 Jun 2024 22:20
  
hi, your hci and your vcsa are in the same subnet? are you experiencing this CBT issue on a single vm or all vm on this vcsa? Please try to power off on your vcsa a vm that you have this CBT error and reset the CBT. Here the steps:

Reset CBT: If the network connection and server status are fine, you might need to reset CBT for the specific virtual machine (VM). Here’s how you can do it:

- Power off the VM.
- Right-click the VM in the vSphere Web Client and select “Edit Settings”.
- Select the “Options” tab and go to “General” under “Advanced”.
- Click “Configuration Parameters”, click “Add Row”, and add ctkEnabled as the name and false as the value.
- Power on the VM, then power it off again.
- Remove the ctkEnabled row that you added.
- Power on the VM.
Enable CBT: After resetting, you’ll need to enable CBT again. You can do this by following the same steps as above, but in step 4, set ctkEnabled to true.
Prosi Lv2Posted 24 Jun 2024 11:03
  
Hi,

You need to connect first your HCI to VMware vCenter so that Sangfor HCI can detect it. Once VMs are detected in the Sangfor HCI, right clicking the VM will give you an option "migrate to Sangfor HCI"
Cristian Rugo Lv1Posted 24 Jun 2024 22:05
  
Hi,
in HCI go to Nodes -> Physical Interface and in Other set the same DNS as Vmware. Do this operation for every node in the cluster
Sutan Makmur Lv1Posted 27 Jun 2024 07:33
  
Here are steps to troubleshoot:

1. Check Network Connection: Ensure stable connectivity between the backup server and vCenter server.
2. Verify vCenter Server Status: Confirm the vCenter server is operational and check for errors in the logs.
3. Verify VM Settings: Ensure CBT is enabled in the VM's settings.

You can enable CBT manually by following these steps:
- Power off the VM.
- Edit the VM's settings and add the following lines to the VM's configuration file (.vmx file):
Copy code:

ctkEnabled = "true"
scsi0:0.ctkEnabled = "true"

- Power on the VM.
4. Check VMware Tools: Ensure VMware Tools are installed and up-to-date on the VM.
5. Restart Management Agents: Restart the management agents on the ESXi host.
- You can do this through the ESXi host client or via SSH using the command:
/etc/init.d/hostd restart
/etc/init.d/vpxa restart

6, Review Permissions: Ensure the backup user account has the necessary permissions.
7. Check for Snapshots: Ensure there are no existing snapshots that might interfere.
8. vSphere API and Compatibility: Confirm the backup solution is compatible with your VMware version and using the correct APIs.
vesogi7900 Lv1Posted 28 Jun 2024 15:10
  
I found a few potential solutions to your problem on the Sangfor community forum1:

Migrate using clone VM to HCI: Some users have reported success by migrating using the clone VM to HCI method. In some cases, this will remove CBT during the cloning of the VM. If the migration still fails, try cloning and after running 5 or 10%, cancel the task, then clone again until it finishes1.
Reset and Enable CBT: If the network connection and server status are fine, you might need to reset CBT for the specific virtual machine (VM). Here’s how you can do it:
Power off the VM.
Right-click the VM in the vSphere Web Client and select “Edit Settings”.
Select the “Options” tab and go to “General” under “Advanced”.
Click “Configuration Parameters”, click “Add Row”, and add ctkEnabled as the name and false as the value.
Power on the VM, then power it off again.
Remove the ctkEnabled row that you added.
Power on the VM. After resetting, you’ll need to enable CBT again. You can do this by following the same steps as above, but in step 4, set ctkEnabled to true1.
Check DNS Settings: In HCI, go to Nodes -> Physical Interface and in Other set the same DNS as VMware. Do this operation for every node in the cluster1.
Connect HCI to VMware vCenter: You need to connect your HCI to VMware vCenter so that Sangfor HCI can detect it. Once VMs are detected in the Sangfor HCI, right-clicking the VM will give you an option "migrate to Sangfor HCI"1.
Please try these solutions and see if they resolve your issue. If the problem persists, I recommend reaching out to Sangfor’s support for further assistance. Good luck!

I Can Help:

Change

Moderator on This Board

3
4
3

Started Topics

Followers

Follow

2
2
0

Started Topics

Followers

Follow

0
1
0

Started Topics

Followers

Follow

Board Leaders