Error migrating VM from vCenter to HCI

gkmanlangit Lv1Posted 16 May 2024 15:05

Last edited by gkmanlangit 17 May 2024 09:00.

Tried to migrate the created VM from vCenter to HCI but keep getting the error" error copying disk data" i already configure the dns of both of my host in the cluster in hci. What's the possible solution for this?

Newbie517762 has solved this question and earned 10 coins.

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

HiHi,

Are you referring to the "aCloud vCenter Migration Troubleshooting Guides"?
Please find the attached file for the Troubleshooting Guides link.
Sangfor aCloud vCenter Migration Troubleshooting Guides Linking.pdf (72.43 KB, Downloads: 60)
Is this answer helpful?
Newbie517762 Lv5Posted 17 May 2024 10:40
  
HiHi,

Are you referring to the "aCloud vCenter Migration Troubleshooting Guides"?
Please find the attached file for the Troubleshooting Guides link.
Sangfor aCloud vCenter Migration Troubleshooting Guides Linking.pdf (72.43 KB, Downloads: 60)
Rotring Lv2Posted 17 May 2024 11:26
  
Hi,
Encountering a "error copying disk data" message during VM migration from vCenter to HCI can be frustrating. Here are some possible solutions to troubleshoot the issue:

1.Verify Disk Compatibility:
-Ensure VM disks are in persistent mode or raw device mappings (RDMs). Storage vMotion (the technology likely used for migration) doesn't support snapshots or disks in non-persistent mode. Check your VM configuration in vCenter.

2.Check VM Snapshots:
-Storage vMotion cannot migrate VMs with active snapshots.
Try consolidating snapshots or powering off the VM and deleting any snapshots before migration.

3.Review Storage vMotion Requirements:
-Consult the VMware documentation for detailed requirements for Storage vMotion. This might include limitations on specific disk types or compatibility versions between vCenter and HCI.

4.Examine VM Logs:
-Look for detailed error messages in the VM's logs. These can provide specific clues about the cause of the disk copy failure. You might find entries related to "CBTMotion" which can indicate issues during the migration process.
5.Alternative Migration Methods:
If Storage vMotion continues to cause problems, consider alternative migration methods:
-Cold Migration: Power off the VM before migration. This might be slower but avoids potential issues with the running VM.
-P2V (Physical to Virtual): Convert the physical machine to a virtual machine directly on the HCI datastore.

I Can Help:

Change

Moderator on This Board

3
1
2

Started Topics

Followers

Follow

2
0
0

Started Topics

Followers

Follow

0
0
0

Started Topics

Followers

Follow

Board Leaders