The Web Client can assign a storage policy to a new VM or virtual disk when it is created, deployed from a template, or cloned from another VM. A VMware administrator can change the policy assigned to a VM or virtual disk. Finally, a VM’s storage policy can be changed during Storage vMotion.
Assigning a Storage Policy to New VM
A VMware administrator can assign a storage policy to a new VM created using the Deploy from Template wizard. (The procedure is identical to policy assignment with the Create New Virtual Machine and Clone Virtual Machine wizards.)
Right-click the target template in the Web Client inventory pane’s VMs and Templates list, and select New VM from This Template.
|
|
|
New VM from Template Command |
From the Storage selection page there is a section for VM Storage policy that allows the selectin of any policies that have been created.
|
|
|
Select Storage Step of Template |
Setting a Policy for an Entire VM
In the Select Storage pane, select Thin Provision from the Select virtual disk format dropdown (FlashArrays not running on Purity//FA 6.2.0 or later only support thin provisioned volumes; selecting other options causes VM creation to fail), and either select a datastore (VMFS, NFS or vVol) from the list or a policy from the VM storage policy dropdown.
Selecting a policy filters the list to include only compliant storage. For example, selecting the built-in vVol No Requirements Policy, would filter the list to show only vVol datastores.
Selecting the FlashArray-15MinReplication-Component policy filters out datastores on arrays that do not have protection groups with those properties.
|
|
|
Selecting a Storage Policy |
A storage policy that includes local snapshots or remote replication requires a replication group. An existing group can be assigned, or, if Automatic is selected, VMware directs the array to create a protection group with the specified capabilities.
Whichever option is chosen, the VM’s config vVol and all of its data vVols are assigned the same policy. (Swap vVols are never assigned a storage policy.) Click Finish to complete the wizard. The VM is created and its data and config vVols are placed in the assigned protection group.
|
|
|
Assign an Existing Replication Group |
BEST PRACTICES: Everpure recommends assigning local snapshot policies to all config vVols to simplify VM restoration.
All FlashArray volumes are thin provisioned, so the Thin Provision virtual disk format should always be selected. With FlashArray volumes, there is no performance impact for thin provisioning.
The screenshot below shows the FlashArray GUI view of a common storage policy for an entire vVol-based VM.
|
|
|
FlashArray GUI View of a VM-wide Storage Policy |
Assigning a Policy to Each of VM's Virtual Disks
In most cases, VMware administrators put all of a VM’s volumes in the same protection group, thereby assigning the same storage policy to them.
Alternatively, there is the option to apply the storage policy at a per virtual disk basis. Select configure Per Disk.
|
|
|
Configure storage policy per Disk |
In this view, a separate storage policy can be specified for for the VM’s config vVol as well as for each virtual disk (data vVol).
The Configuration File line refers to the VM’s config vVol. The remaining lines enumerate its data vVols (Hard Disk 1 in the example).
|
|
|
Configure Per Disk - Configuring the Configuration File |
The objects can be configured individual or by selecting multiple virtual disks or configuration file.
|
|
|
Configure Per Disk - Selecting one virtual disk |
|
|
|
Configure Per Disk - Selecting two virtual disks |
Selecting a policy from the VM storage policy dropdown filters the list to include only compliant datastores. For example, selecting the vVol No Requirements Policy lists only vVol datastores.
A storage policy that includes local snapshots or remote replication requires a replication group. An existing group can be assigned (for example, sn1-x70-c05-33:FlashArray-SPBM-15minReplication).
Alternatively, if Automatic is selected, the array creates a protection group with the capabilities specified by the policy. Whichever option is chosen, the policy is assigned to the vVol.
|
|
|
Select VM Storage Policy - Storage - Replication Group |
For example, a VM’s config vVol might be assigned a FlashArray-1hrLocalSnap storage policy, which uses Local Snapshot Protection rules. Whereas its the boot data vVol might be assigned the FlashArray-15minReplication policy, corresponding to the sn1-x70-c05-33:FlashArray-SPBM-15minReplication replication group.
|
|
|
Separate Storage Policies for Config and Data vVols |
Here are the screenshots from the Array that list the contents of the two protection groups that correspond to the policies chosen for the config and data.
|
|
|
Config vVol in the VASA managed protection group for the given Storage Policy |
|
|
|
Data vVol in the 15 Minute Replication Array Protection Group |
VMware does not allow a single VM to have different Replication Groups for different virtual disks. If a VM has objects in a replication group, then all objects that have a replication policy applied should use the same replication group.
Changing a VM's Storage Policy
To change a VM’s storage policy, a VMware administrator assigns a new policy to it. VMware directs the array to reconfigure the affected vVols. If the change makes the VM or any of its virtual disks non-compliant, the VMware administrator must adjust their policies.
To change a VM’s storage policy, select the VMs and Templates view in the Web Client inventory pane, (1) right-click the target VM, (2) select VM Policies from the dropdown menu, and (3) select Edit VM Storage Policies from the secondary dropdown to launch the Edit VM Storage Policies wizard.
|
|
|
Edit VM Storage Policies Command |
The VM Storage Policies can be edied a per disk level or all at the same time. Same with the replication group selection.
|
|
|
Edit VM Storage Policies Wizard |
|
|
|
Edit VM Storage Policy Replication Group |
To change the storage policy assigned to a VM’s config vVol or a single data vVol, select a policy from the dropdown in the VM Storage Policy column of its row in the table.
Selecting a policy that is not valid for the array that hosts a vVol displays a Datastore does not match current VM policy error message. To satisfy the selected policy, the VM would have to be moved to a different array (reconfiguration would not suffice).
A storage policy change may require that the replication groups for one or more vVols be changed.
|
|
|
One or More Replication Groups not Configured |
This warning typically appears for one of two reasons:
-
The new storage policy requires that vVols be in a replication group, and one or more vVols are not.
Note:
If no policy is shared by all of the VM’s vVols, the Replication group dropdown does not appear.
When the policy and replication groups (if required) are set then the Policy summary page will show the state and compliance for each object.
One or More Replication Groups not Configured
Assigning a Policy during Storage Migration
Compliance with an existing or newly assigned storage policy may require migrating a VM to a different array. For example, VM migration is required if:
- A policy specifying a different array than the current VM or virtual disk location is assigned
- A policy requiring QoS (or not) is assigned to a VM or virtual disk located on an array with the opposite QoS setting.
- A policy specifying snapshot or replication parameters not available with any protection group on a VM or virtual disk’s current array is assigned.
- Some of these situations can be avoided by array reconfiguration, for example by creating a new protection group or inverting the array’s QoS setting. Others, such as a specific array requirement, cannot. If an array cannot be made to meet a policy requirement, the VMware administrator must use Storage vMotion to move the VM or virtual disk to one that can satisfy the requirement. The administrator can select a new storage policy during Storage vMotion.
Here is what the process would look like when migrating a VM from VMFS to vVols. During the storage selection process you would be able to choose the storage policy and what compatible storage is available. After choosing to migrate the VM, select to change storage only.
Migrate VM - Storage Only
From the select storage page in the wizard the option to select storage policy is there. When selecting a storage policy the compatible storage will be shown at the top of the storage list. If choosing a policy that requires a replciation group there is a replication group selection box at the bottom.
Migrate VM - Storage and Policy Selection
Once the desired policy and replication group (if needed) is selected the migration wizard can be completed.
Note:BEST PRACTICE: Everpure recommends reselecting the same storage policy rather the Keep existing storage policy option in order to provide Storage vMotion with the information it needs to complete a migration.