In the first of the SPBM series, we talked about Tag based Storage Policy Based Management (SPBM). Next, in the series, we will review how you can manage Virtual Volumes (VVols) using SPBM. If you are unfamiliar with VVols, take a look at Storagehub for an overview and more details on what and how VVols revolutionizes standard external storage.
With VVols, the capabilities of the storage array are published via the VASA provider. Each array vendor has different implementations of their VASA. Subsequently, the capabilities of each vendor and array can have different storage policies and functionality. For example, one array may have a performance tiering capability and a QoS IOPs limit or control while another vendor may have application specific page/block size to optimize application performance. Other capabilities may include deduplication, compression, encryption, array snapshot protection, or performance service levels.
Virtual Volumes and SPBM Capabilities
Let’s look at some of the more common capabilities and how, with VVols and SPBM, management becomes significantly easier by not requiring storage administrator involvement. With VVols, you are able to setup different performance or quality of service policies within a single VVol datastore. This is possible with VVols because now the array manages capability via the SPBM policies you create. By using SPBM to manage performance, you no longer must create separate datastores for different performance tiers or other functionality.
In the image below, you see the different service levels you can choose for the same VVol datastore. A separate policy can be created for each service level and used within the same VVol datastore. When a specific policy is applied to a VM or object, the array manages the service level and ensures the VM gets the resources chosen. By being able to use different policies on the same VVol datastore, you save time, reduce complexity and cost of your storage infrastructure. No more separate LUN’s with different capabilities, it’s all managed via policies, and the array handles the work.
Below is an example of an array that lets you chose the criticality for the policy. By choosing Mission critical, in this example, you ensure the VM is given resources above all others VMs. Within that same VVol datastore you can have a non-critical policy, say for dev VMs. Because the array is aware of all the policies applied to the different VMs on that VVol datastore, it manages the allocation of resources based on those policies and ensures QoS accordingly.
More examples of some of the capabilities arrays may offer when creating SPBM policies.
Here is a video showing the creation of SPBM policies with VVols and some of the capabilities available.
One of the more advanced capabilities, with vendors using the latest VASA, is replication. This functionality allows you to create storage policies to protect a VM by replicating the VM to another array without interacting with the arrays themselves! No need to setup array volume level replication and replicate more data then is required. This can greatly reduce storage usage and WAN utilization, in turn, reducing complexity and cost of VM data protection. This gives you the granularity of using a policy for single VM or multiple VMs. Additionally, if needed, you can apply the policy to a single VMDK! Imagine needing to protect critical VMs, and by simply applying an SPBM policy, those VMs are now replicated to a secondary array based on parameters you have chosen!
In the video below are a few ways you can apply SPBM policies on VVols datastores including setting up replication for a single virtual machine.
There are numerous ways you can use SPBM policies with Virtual Volumes. With SPBM and VVols, you no longer waste space, time and resources provisioning specific resources for individual datastores. A single Virtual Volume can have several different policies with different configurations and resource allocation for different VM requirements. You can similarly apply different policies to a single VM with different disk requirements; say for example an SQL server. VVols and vSAN work complementary with SPBM policies as well. With VVols and vSAN the published capabilities are managed by the array or vSAN themselves and do not require advanced or custom storage allocations. As a result, VVols and SPBM can save you money, storage space and free up time for more important responsibilities.
- Storage Policy Based Management
- Populating the VM Storage Policies Interface
- Assign Tags to Datastores
- Storage DRS Integration with Storage Profiles
Stay Tuned for the SPBM Blog Series
- Using Tag-based SPBM Policies to Manage Your Storage
- Storage Capabilities and Services
- Virtual Volumes
- Data Services SPBM Policies
- I/O Filters
Related SPBM Posts
- How is SPBM different to Tag-Based Placement?
- SPBM, because not all applications are created equal
- vSAN Operations: Use separate SPBM policies for VMs in stretched clusters