Cannot set new policy to Virtual Machine's Hard disk after migration to vSAN datastore.
Article ID: 392629
Updated On:
Products
Issue/Introduction
- Regarding the VM migration, the source was a non-vSAN datastore, and the destination was a vSAN datastore.
- The issue can be seen when the source and destination datastores are in the same cluster and/or in the same vCenter. However, it can also be seen if the source and destination are in different vCenters.
- The migration wasn't performed as SvMotion nor as Compute + Storage vMotion.
- The migration was performed by copying the VM's files from the source datastore to the destination datastore (via WinSCP, for example).
- The VM Namespace and the vswap file don't have the problem applying storage policies, only the hard disks.
Environment
VMware vSAN (All versions).
Cause
vSAN is a distributed, object-based storage system, different from other classic storage types as VMFS and NFS.
During the storage vMotion triggered on vCenter (or compute+storage vMotion) from a traditional to a vSAN datastore, the flat file gets converted into a vSAN object. However, the flat file is not converted if the VM files are manually copied from traditional storage to vSAN.
Resolution
Migrate the VM to traditional storage, then migrate it back to vSAN using storage migration (offline or SvMotion) from vCenter to ensure the conversion to vSAN objects occurs.
Or if in case it was a Cross vCenter copy and there is no traditional storage available in the destination vCenter, clone the VM to reside on the vSAN datastore, and this should also convert the flat file to a vSAN object.
Additional Information
Feedback
