Note down one of the iSCSI data lif IP address from the local fault domain storage array.

On vSphere host iSCSI Storage Adapter, add that iSCSI IP under the Dynamic Discovery tab.

For Uniform access mode, need to provide the source and target fault domain iSCSI data lif address.

Repeat the above step on vSphere hosts for the other fault domain adding its local iSCSI data lif IP on Dynamic Discovery tab.

With proper network connectivity, four iSCSI connection should exist per vSphere host that has two iSCSI VMKernel nics and two iSCSI data lifs per storage controller.

Create LUN using ONTAP System Manager, setup SnapMirror with replication policy AutomatedFailOverDuplex, pick the host initiators and set host proximity.

On other fault domain storage array, create the SAN initiator group with its vSphere host initiators and set host proximity.

For Uniform access mode, the igroup can be replicated from source fault domain.

Map the replicated LUN with same mapping ID as in source fault domain.

On vCenter, right click on vSphere Cluster and select Rescan Storage option.

On one of the vSphere host in the cluster, check the newly created device shows up with datastore showing Not Consumed.

On vCenter, right click on vSphere Cluster and select New Datastore option.

On Wizard, remember to provide the datastore name and select the device with right capacity & device id.

Verify the datastore is mounted on all hosts on cluster across both fault domains.

The above screenshots shows Active I/O on single controller since we used AFF. For ASA, it will have Active IO on all paths.

When additional datastores are added, need to remember to expand the existing Consistency Group to have it consistent across the vSphere cluster.

Ensure NetApp ONTAP Tools is deployed and registered to vCenter.

If not, follow ONTAP Tools deployment and Add a vCenter server instance

Ensure ONTAP Storage systems are registered to ONTAP Tools. This includes both fault domain storage systems and third one for Asynchronous remote replication to use for VM protection with SnapCenter Plugin for VMware vSphere.

If not, follow Add storage backend using vSphere client UI

Update hosts data to sync with ONTAP Tools and then, create a datastore.

To enable SM-as, right click on vSphere cluster and pick Protect cluster on NetApp ONTAP Tools (refer above screenshot)

It will show existing datastores for that cluster along with SVM details. The default CG name is <vSphere Cluster name>_<SVM name>. Click on Add Relationship button.

Pick the target SVM and set the policy to AutomatedFailOverDuplex for SM-as. There is a toggle switch for Uniform host configuration. Set the proximity for each host.

Verify the host promity info and other details. Add another relationship to third site with replication policy of Asynchronous if required. Then, click on Protect.

NOTE: If plan to use SnapCenter Plug-in for VMware vSphere 6.0, the replication needs to be setup at volume level rather than at Consistency Group level.

With Uniform host access, the host has iSCSI connection to both fault domain storage arrays.

NOTE: The above screenshot is from AFF. If ASA, ACTIVE I/O should be in all paths with proper network connections.

ONTAP Tools plugin also indicates the volume is protected or not.

For more details and to update the host proximity info, Host cluster relationships option under the ONTAP Tools can be utilized.

Add all the ONTAP Storage Systems planned to use in SCV.

Create Policy. Ensure Update SnapMirror after backup is checked for SM-as and also Update SnapVault after backup for Async replication to third fault domain.

Create Resource Group with desiered items that need to be protected, associate to policy and schedule.

NOTE: Snapshot name ending with _recent is not supported with SM-as.

Backups occur at scheduled time based on Policy associated to Resource Group. Jobs can be monitored from the Dashboard job monitor or from the backup info on those resources.

VMs can be restored to same or alternate vCenter from the SVM on Primary fault domain or from one of the secondary locations.

Similar option is also available for Datastore mount operation.