Skip to content

Commit b62ae64

Browse files
Update vSphere Storage vMotion FAQ
Co-authored-by: Rene van den Bedem <[email protected]> Co-authored-by: Ricky Perez <[email protected]>
1 parent 8ae5fec commit b62ae64

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/azure-vmware/faq.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -271,8 +271,8 @@ sections:
271271
- question: What is the RAID configuration of the disk groups?
272272
answer: The disk groups aren't RAID configured. Instead, they're just a bunch of disks (JBOD) and are [directly controlled by vSAN](https://core.vmware.com/vsan-learn-and-evaluate).
273273

274-
- question: Why does a storage vMotion take an extended period of time from Azure NetApp Files to another datastore?
275-
answer: When performing a storage vMotion from an external file based datastore such as Azure Netapp Files to another datastore the task may run for an extended period of time. This is due to the use of the Software Datamover in the ESXi kernel. This datamover requires that all the blocks in the vmdk being read and transferred to the ESXi host regardless of content. This causes the entire size of the vmdk to be transferred from the external array through the ESXi host in and then to the destination datastore. The entire disk must be read in order to create a complete replica at the destination. The destination format and consumed space depends on the destination datastore capabilities, protocol and format. Since all blocks must be read from the source datastore the time to complete this operation may be longer than expected.
274+
- question: Why does a vSphere Storage vMotion from Azure NetApp Files (ANF) to another datastore take an extended period of time?
275+
answer: This is due to the use of the Data Mover agent in the ESXi kernel. The Data Mover agent requires that all the blocks in the VMDK (Virtual Machine Disk) file be read and transferred to the ESXi host regardless of content. This results in the entire size of the VMDK to be transferred from the external array through the ESXi host to the destination datastore. The entire disk must be read in order to create a complete replica at the destination. The destination format and consumed space depends upon the destination datastore capabilities, protocol and format. Since all blocks must be read from the source datastore, the time to complete this operation may be longer than expected.
276276

277277

278278
- name: Hosts, clusters, and private clouds

0 commit comments

Comments
 (0)