Skip to main content
Pure Technical Services

SRM User Guide: Configuration of Replication for SRM with the FlashArray Plugin for the vSphere Client

Currently viewing public documentation. Please login to access the full scope of documentation.

KP_Ext_Announcement.png

Creating Datastores

Note this requires the 4.3.0 release or later of the FlashArray Plugin for the vSphere Client.

To create a new VMFS datastore the simplest option is through the use of the FlashArray Plugin for the vSphere Client. Instructions for installation can be found here.

To create a new datastore, right-click on a vSphere Cluster, choose Pure Storage > Create Datastore.

clipboard_ee9d0256e7e7319ccc5a732259850ddbc.png

Choose VMFS and the version (recommended is version 6).

clipboard_e1822ae9a5c3821d72357ca6b8e7b0808.png

Then a name and a size.

clipboard_e8912a8b133a2d4b32b51d0d1ed326029.png

Choose a cluster.

clipboard_e49c1254f57d8ce63d9b149faf83074af.png

Then choose the FlashArray. You can either choose a FlashArray or a pod. FlashArrays and available unstretched pods will be listed under Local.

clipboard_e4287abc3cc15253dc536cc1a46fbe148.png

Stretched pods will be listed under Clustered.

clipboard_e3d82657b51256aa080371d16daa7de45.png

ActiveDR-enabled pods will be under Continuous replication (this requires vSphere Plugin 4.4.x+).

clipboard_ed20aaba4a11199a99bf6a839dbab15af.png

This will show you all available promoted ActiveDR-enabled pods on that array. If there is an info notice next to the remote pod, it general means the target pod is promoted (in a test state) too.

clipboard_e0a2391d1c83f824c78a1c28a5c474ae8.png

The ActiveDR table will list source and target arrays, source and target pods, and the current lab (how far behind the data on the target is from the source).

If a standalone array or a non-ActiveDR pod has been chosen, enabling periodic replication is an option; if they are available, that choice will be marked with a green check in the Async column. If choosing an option without a green check (and also want asynchronous periodic protection), it means that configuring a protection group on the pod or FlashArray prior to SRM management is required.

Choose a protection group.

clipboard_e36354e2603b641d2cc6874cf333caf9e.png

And finally optionally QoS configuration or volume group.

clipboard_e42442a8a76faacbe74cccfa3e6748e4f.png

This will create the datastore.

clipboard_e752800af5e76552b8710a7dfacd3fd06.png

Viewing Replication Configuration

To see how a datastore is protected, click on the datastore in the vSphere Client and choose the Summary tab.

clipboard_e96a143cb191bb4081a99b2414f0bfe52.png

The summary view will show if the datastore is in a pod, how many arrays that pod is protected by. Looking at the bottom of the table, the number (if any) of protection groups that volume is in will be listed as well.

clipboard_e06f7ee5c585b74d7115a971b05032148.png

To view the protection group a volume belongs to, right-click the datastore and choose Update Datastore Protection.

clipboard_eb0bd113059768cc9ebab026ce056afea.png

This will list (if any) the protection groups and their high-level configuration that include the specified volume.

clipboard_e957c67899fdbec46e197db1aa821a3f1.png

 

Changing Replication Configuration

To change the protection group a volume belongs to, right-click the datastore and choose Update Datastore Protection.

clipboard_eb0bd113059768cc9ebab026ce056afea.png

This will list (if any) the protection groups and their high-level configuration that include the specified volume.

clipboard_e957c67899fdbec46e197db1aa821a3f1.png

Then select the protection groups to add the volume to (and keep any groups that should stay in selected) and deselect the protection groups the volume should be removed from.

clipboard_e6368120cd3cd6edbf0360610ae9b1c5f.png

The same volume can exist in more than one protection group at one time. Click Update Protection to commit the changes.