Skip to main content
Pure1 Support Portal

Site Recovery Manager Protection Groups

SRM Protection Group Overview

Site Recovery Manager offers a grouping mechanism for related datastores and/or RDMs to be failed over together called a Protection Group. SRM protection groups can be one of three types:

  1. Datastore Groups. This is a related group of datastores or RDMs. Currently the FlashArray does not enforce that any particular volumes be failed over together. Therefore, datastores and RDMs are only required to be failed over together if there is one or more virtual machines that span multiple volumes (e.g. a VM that has a virtual disk on a VMFS and also uses an RDM--the volume underpinning the VMFS and the volume underpinning the RDM will be grouped by SRM).
  2. Individual VMs. This is not relevant when using FlashArray replication and is only for VMs protected by vSphere Replication. While it is supported to use vSphere Replication on virtual machines hosted on Pure Storage, SRM does not support protecting VMs in SRM with both options. So the best practice is to use either vSphere Replication or FlashArray replication, not both.
  3. Storage Policies. This is a grouping of replicated datastores via storage policies. This provides for the ability to move VMs between datastores without breaking SRM protection.

clipboard_ef520cb3897f3a681fbe47c92640ea10c.png

Replicated volumes are added to a protection group via one (and only one) of the above mechanisms. In order for a volume to be added to a protection group, they must be discovered as replicated from a replication array pair. Furthermore if they are to be protected by the stretched storage feature of SRM, they must also be protected with a storage policy.

An SRM protection group is then included in one or more SRM recovery plans. A protection group defines what datastores/RDM are related, which then in turn dictates what virtual machines are related. All VMs that use a datastore or RDM in a protection group must be failed over together. A recovery plan then describes how a VM is to be recovered (should it be powered-in, what order should it power-on in, should a script be run, an IP be changed, etc.). To have the ability to fail over the same VMs in different ways, add the protection group that protects that virtual machine to different recovery plans.

Creating an SRM Protection Group

To create a protection group, click the Protection Group link at the top of the SRM web interface:

clipboard_e49031598a40c514ae963c30bf4df68fa.png

Then click New.

clipboard_e3a9c163b7986b72adeb7d97895fbbef2.png

Give the protection group a name and optionally a description. Choose the direction for the protection group. A protection group can only protect datastore/RDMs that are being replicated in the same direction. In other words, a protection group cannot have datastores/RDMs being used in vCenter A and replicated to vCenter B as well as datastores/RDMs that are in use in vCenter B being replicated back to vCenter A. Only one direction or the other is supported at once.

Click Next.

clipboard_e8c262cd8cb0108f5959692e4bfc20e59.png

Now choose the type of protection group. Once selected, available array pairs will be listed. Choose an array pair that is enabled (green checkmark). If the array pair is not listed, ensure the array manager is configured correctly and/or the arrays have a replication connection between them.

Click Next.

clipboard_e9c30ec6129e962003d89fa8cce26c827.png

The wizard will then list all of the valid replication devices for that array pair. If the devices are grouped it means that one or more VMs are using multiple devices at once, therefore SRM is enforcing their grouping.

clipboard_e5d4d3d2604c8d589ff7e6908dc62f0de.png

You can select one or many groups (and you can add or remove more later as needed) to add them to this protection group. The last step is to add the protection group that will be created to a recovery plan. You can add to an existing one, or create a new one, or skip this step for now. Just remember that in order to failover a protection group it must eventually be added to at least one recovery plan.

 

clipboard_efa38caf73b067432f85e7da2bf9cea27.png

Click Next then Finish.

 

SRM Protection Groups vs. a FlashArray Protection Groups

People who are familiar with Pure Storage FlashArray terms, would recognize this name--the FlashArray also uses the term Protection Groups. It is important to note that these are related mechanisms (in that they both have to do with replication) but they are not the same.

An SRM protection group includes one or more volumes that must be failed over together. A volume can only be in one SRM protection group at a time.

clipboard_e7a2f00571ce728ea45b69fd4dcf886d5.png

A FlashArray protection group is a replication and/or local snapshot policy that can be assigned to one or more volumes on a FlashArray. Many volumes can be assigned in a FlashArray protection group and a volume can be in many FlashArray protection groups.

clipboard_e889e2e14185e0473ab45bd12fa47eb41.png