The configuration of array managers to support failover from a stretched pod is almost identical to configuration for an unstretched pod, with one major exception: there are now two local arrays, not one. So both need to be specified in the appropriate place in the local array manager and the remote array manager.
While it is not technically required to specify both FlashArrays that host a stretched pod in the array manager it is advisable to do so. If only one array is registered and that array fails--the SRA will not be able to perform a planned migration. Instead an SRM disaster recovery operation will need to be started instead. This will still result a successful failover, but the source side will not be fully brought down which will then require eventual manual cleanup. Therefore, an SRM failover from a stretched pod requires that both FlashArrays be specified in the array manager to provide the most resilient experience..
Below there is a pod named srmPod that is stretched across two FlashArrays; flasharray-m50-1 and flasharray-m50-2:
This pod has a protection group called srmProtectionGroup that replicates to a 3rd FlashArray called flasharray-m20-1 every 10 minutes:
Therefore, flasharray-m50-1 and flasharray-m50-2 should be seen as the local array manager sources and flasharray-m20-1 should be seen as the local array manager peer. So log into Site Recovery Manager:
Click Add. Ensure you are using the 3.1 or later release of the SRA in the first screen. Click Next.
For the local array manager, double check you are configuring the array manager for the correct side of the vCenter pair. To make things simpler, it is best to be on the SRM server that is paired with the vCenter that currently hosts the datastores you want to protect (the one that has access to the volumes in the pods). You can verify the vCenter name at the top of the Local array manager window:
vCenter-01 is the vCenter that has access to my stretched-pod datastores, so I am on the right side. If you are logged into the opposite side, you can still follow these instructions, just do this in reverse order (3rd array as local first, stretched pod arrays as peer, then the opposite).
In my local array manager (which I will call vc01-local), I will put in my flasharray-m50-1 and flasharray-m50-2 FQDNs in the local array address, and the remote FlashArray (flasharray-m20-1) FQDN in the peer array address.
Currently all arrays specified in a single address entry (local or peer) must share the same credentials. In other words, while the local array(s) can have one set of credentials and the peer array(s) can have different credentials, all arrays specified in local arrays must have the same credentials, and all arrays specified in the peer arrays must have the same credentials. So in the example below, flasharray-m50-1 and flasharray-m50-2 must have the same credentials, while flasharray-m20-1 can then either also be configured with those same credentials or can have its own unique credentials.
When complete, click Next.
Now configure the array manager that is local to the other vCenter in the pair. In the below case, my "target" vCenter is called vcenter-02.purecloud.com.
I will call this array manager vc02-local.
For the local array(s) address entry I only need to enter in my 3rd array, the one I am periodically replicating to from my stretched pod, which in my case is the FQDN of the FlashArray named flasharray-m20-1.
For the peer arrays, I will enter the FQDNs of the arrays that host the stretched pod, the arrays named flasharray-m50-1 and flasharray-m50-2. Add in the respective credentials for both the local and peer connections.
Click Next.
The array managers will be configured in SRM and identified array pairs will be listed. SRM will automatically select array pairs that it can immediately enable. Select and de-select as needed. In this case. select the pod and target FlashArray pair to be enabled (and any other pair you would like to enable).
In my case I will keep on the array pair that reflects my pod to array replication pair (srmPod to flasharray-m20-1).
You can also enable or disable array pairs at a later time. If you have no intention of using a specific array pair, the suggestion would be to not enable it. This will shorten device discovery by not having the SRA query unneeded array pairs for replication details.
Confirm the selections and click Finish.