You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-vmware/faq.yml
+4-1Lines changed: 4 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ metadata:
4
4
description: "Get answers to common questions about Azure VMware Solution."
5
5
ms.topic: faq
6
6
ms.service: azure-vmware
7
-
ms.date: 1/16/2025
7
+
ms.date: 1/24/2025
8
8
title: Common questions about Azure VMware Solution
9
9
summary: This article answers commonly asked questions about Azure VMware Solution.
10
10
@@ -271,6 +271,9 @@ sections:
271
271
- question: What is the RAID configuration of the disk groups?
272
272
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).
273
273
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.
0 commit comments