Administrator Guide

NOTE: When applying a VM Storage Policy containing rules for the ScStorageProfile capability, the vCenter administrator
can ignore the datastore compatibility warning Datastore does not satisfy required properties.. The
VASA provider overrides the datastore's configured value and applies the user-provided value of ScStorageProfile for
VVols of the VM.
Expected Behaviors for Data Reduction Scenarios
The settings specified in both the storage container Data Reduction options and in the VMware Storage Profile determine the
results of VM and VVol creation. If the storage container Data Reduction settings conflict with the settings in the VM Storage
Profile, creation of VMs and virtual volumes could fail.
The following table describes the expected behavior for new VM creation with the Compression option.
Table 6. Expected Behavior for New VM Creation with Compression
VM Storage Policy = None
Specified
VM Storage Policy =
Compression Enabled
VM Storage Policy =
Compression Disabled
Storage Container
Compression Enabled
Volumes created with Default
Data Reduction profile value
from storage container
Volumes created with
Compression Data Reduction
Profile
Volumes created with the
Data Reduction Profile set
to None
Storage Container
Compression Disabled
Volumes created with Default
Data Reduction profile
value from storage container
VM creation fails because
user is trying to set an
unsupported capability
Volumes created with the
Data Reduction Profile set
to None
The following table describes the expected behavior for new VM creation with the Deduplication option.
Table 7. Expected Behavior for New VM Creation with Deduplication
VM Storage Policy = None
Specified
VM Storage Policy =
Deduplication Enabled
VM Storage Policy =
Deduplication Disabled
Storage Container
Deduplication Enabled
Volumes created with Default
Data Reduction profile value
from storage container
Volumes created with Dedup
with Compression Data
Reduction Profile
Volumes created with the
Data Reduction Profile set
to None
Storage Container
Deduplication Disabled
Volumes created with Default
Data Reduction profile
value from storage container
VM creation fails because
user is trying to set an
unsupported capability
Volumes created with the
Data Reduction Profile 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.
Table 8. Expected Behavior for VM Storage Policy Update on Existing VMs
Old VM Storage
Policy
New VM Storage
Policy
Expected Behavior
Compression Enabled Compression Disabled Data Reduction Profile of associated VVols changes from Compression to
None. Data is uncompressed at the next data progression cycle.
Compression Disabled/
None Specified
Compression Enabled Data Reduction Profile of associated VVols changes from None to
Compression. Data is compressed at the next data progression cycle.
Deduplication Disabled Deduplication Enabled Data Reduction Profile of associated VVols changes to Deduplication
with Compression. Data is deduplicated at the next data progression
cycle.
Deduplication Enabled Deduplication Disabled Data Reduction Profile of associated VVols changes from Deduplication
with Compression to None. Data is rehydrated at the next data
progression cycle.
The following table describes the expected behavior for existing VMs when a storage administrator selects or clears the
Compression and Deduplication checkboxes on a storage container.
Managing Virtual Volumes With Storage Manager
181