Storage Policy Groups

User Guides for VMware Solutions

Audience
Public
Content Type
User Guides
Source Type
Documentation

Note:

It is not REQUIRED to use Storage Policies for VMFS with SRM unless you are using the SRM stretched storage feature. If configuring SRM to leverage protection group-based periodic replication (from a pod or not) for VMFS datastore recovery, the storage policy implementation is optional.

In Site Recovery Manager 6.1, VMware introduced the concept of Storage Policy-based discovery of datastore groups. Traditionally, storage was only discovered via the SRA- the SRA would discover array pairs and then any devices that were replicated between said pairs. The limitation to this approach was that if a VM was migrated to another datastore by an administrator or via some automated process (e.g. Storage DRS), protection in SRM could break if that datastore was not replicated and specifically not replicated between that array pair. There was no way to ensure that a migration occurred to an appropriate datastore. Even if it did, if the datastore was not part of the SRM protection group the VM could not be protected.

To resolve for this, SRM now offers a new mechanism to discovery storage: tag-based storage policies. With this, SRAs still need to discover devices as replicated. This part does not change. Instead of adding datastores to an SRM protection group, a storage policy can be added:

Inside of vCenter, since VMs placement and configuration is controlled via tags, VMware administrators can make sure they make correct decisions when moving virtual machines, or creating new virtual disks. If they move or create a disk that is under the VM's policy that is not on compatible storage the administrator will be warned.

The process is:

  1. Configure FlashArray replication on a VMFS volume
  2. Ensure the array managers are configured to discover the replication array pair and see the discovered device
  3. Create a datastore-type tag category
  4. Tag the datastore with that tag category
  5. Create a storage policy that ensures the datastore has that tag
  6. Assign that storage policy to one or more VMs
  7. Add that storage policy to a protection group