Administrator Guide

NOTE: The advertised capabilities only apply to VVols datastores and are not supported on legacy VMFS datastores.
NOTE: Any change to a storage container's Data Reduction prole might cause future fast cloned VMs to be created with
mismatched Data Reduction proles for the cong and data VVols. A fast clone VM shares history with the VM from which it was
created. Hence its data VVols inherit the settings of the data VVols of the original VM. There is another side eect of this shared
history — if a user applies a VM Storage Policy to the original VM, the same changes apply to the data VVols of the fast clone
VM and conversely.
NOTE: When applying a VM Storage Policy containing rules for the ScStorageProle capability, the vCenter administrator can
ignore the datastore compatibility warning Datastore does not satisfy required properties.. The VASA provider
overrides the datastore's congured value and applies the user-provided value of ScStorageProle for VVols of the VM.
Expected Behaviors for Data Reduction Scenarios
The settings specied in both the storage container Data Reduction options and in the VMware Storage Prole determine the results of
VM and VVol creation. If the storage container Data Reduction settings conict with the settings in the VM Storage Prole, creation of
VMs and virtual volumes could fail.
The following table describes the expected behavior for new VM creation with the Compression option.
Table 4. Expected Behavior for New VM Creation with Compression
VM Storage Policy = None
Specied
VM Storage Policy =
Compression Enabled
VM Storage Policy =
Compression Disabled
Storage Container Compression
Enabled
Volumes created with Default
Data Reduction prole value
from storage container
Volumes created with
Compression Data Reduction
Prole
Volumes created with the Data
Reduction Prole set to None
Storage Container Compression
Disabled
Volumes created with Default
Data Reduction prole
value from storage container
VM creation fails because user is
trying to set an unsupported
capability
Volumes created with the Data
Reduction Prole set to None
The following table describes the expected behavior for new VM creation with the Deduplication option.
Table 5. Expected Behavior for New VM Creation with Deduplication
VM Storage Policy = None
Specied
VM Storage Policy =
Deduplication Enabled
VM Storage Policy =
Deduplication Disabled
Storage Container Deduplication
Enabled
Volumes created with Default
Data Reduction prole value
from storage container
Volumes created with Dedup
with Compression Data
Reduction Prole
Volumes created with the Data
Reduction Prole set to None
Storage Container Deduplication
Disabled
Volumes created with Default
Data Reduction prole
value from storage container
VM creation fails because user is
trying to set an unsupported
capability
Volumes created with the Data
Reduction Prole set to None
The following table describes the expected behavior for existing VMs when a vCenter user changes the associated VM policy. This table
assumes that both Compression and Deduplication are enabled on the storage container.
Managing Virtual Volumes With Storage Manager
193