In this brief blog post, we'll talk about creating a storage policy that defines storage requirements for a VM and its virtual disks.
There are a few requirements that must be satisfied before creating storage policy.
Verify that the vSAN storage provider is available by navigating to vCenter Server > Configure > Storage Providers.
Required privileges: Profile-driven storage.Profile-driven storage view and Profile-driven storage.Profile-driven storage update.
If you are certain that all the requirements have been met, you can proceed to create a storage policy.
1. Navigate to Policies and Profile and then click on VM Storage Policies.
2. Click on CREATE.
3. Type a name and a description for the storage policy and click Next.
4. On the Policy structure page, select Enable rules for "vSAN" storage, and click Next.
5. On the vSAN Availability page, define the Site disaster tolerance and Failures to tolerate.
Availability options define the rules for failures to tolerate, Data locality, and Failure tolerance method.
Site disaster tolerance defines the type of site failure tolerance used for virtual machine objects.
Failures to tolerate defines the number of host and device failures that a virtual machine object can tolerate, and the data replication method.
For example, if you choose Dual site mirroring and 2 failures - RAID-6 (Erasure Coding), vSAN configures the following policy rules:
Failures to tolerate: 1
Secondary level of failures to tolerate: 2
Data locality: None
Failure tolerance method: RAID-5/6 (Erasure Coding) - Capacity
Next, on the Storage rules tab, define the encryption, space efficiency, and storage tier rules that can be used along with the HCI Mesh to distinguish the remote datastores.
Encryption services: Defines the encryption rules for virtual machines that you deploy with this policy. You can choose one of the following options:
Data-At-Rest encryption: Encryption is enabled on the virtual machines.
No encryption: Encryption is not enabled on the virtual machines.
No preference: Makes the virtual machines compatible with both Data-At-Rest encryption and No encryption options.
Space Efficiency: Defines the space saving rules for the virtual machines that you deploy with this policy. You can choose one of the following options:
Deduplication and compression: Enables both deduplication and compression on the virtual machines. Deduplication and compression are available only on all-flash disk groups. For more information, see Deduplication and Compression Design Considerations.
Compression only: Enables only compression on the virtual machines. Compression is available only on all-flash disk groups. For more information, see Deduplication and Compression Design Considerations.
No space efficiency: Space efficiency features are not enabled on the virtual machines. Choosing this option requires datastores without any space efficiency options to be turned on.
No preference: Makes the virtual machines compatible with all the options.
Storage tier: Specifies the storage tier for the virtual machines that you deploy with this policy. You can choose one of the following options. Choosing the No preference option makes the virtual machines compatible with both hybrid and all flash environments.
All flash
Hybrid
No preference
Next on the Advanced Policy Rules tab, define advanced policy rules, such as number of disk stripes per object and IOPS limits.
On the Tags tab, click Add Tag Rule, and define the options for your tag rule.
6. On the Storage compatibility page, review the list of datastores under the COMPATIBLE and INCOMPATIBLE tabs and click Next.
7. On the Review and finish page, review the policy settings, and click Finish.
That's it, a new Test Policy has been successfully added to the list.
Now that we have created a new test policy, we can assign this policy to the VM's which we are going to deploy on this vSAN Datastore. vSAN places the virtual machine objects according to the requirements specified in this policy.
Thank you for reading!
*** Explore | Share | Grow ***
Comentários