SnapMirror active sync setup workflow
ONTAP SnapMirror active sync data protection enables business services to continue operating even through a complete site failure, supporting applications to fail over transparently using a secondary copy. There is no manual intervention or custom scripting required to trigger a failover with SnapMirror active sync.
While the System Manager procedures for configuring SnapMirror active sync are different on ASA r2 systems than NetApp FAS, AFF, and ASA systems running the unified ONTAP personality, the requirements, architecture and operation of SnapMirror active sync is the same.
On ASA r2 systems, SnapMirror active sync supports symmetric active/active configurations. In a symmetric active/active configuration, both sites can access local storage for active I/O.
Learn more about symmetric active/active configurations.

To prepare to configure SnapMirror active sync on your ASA r2 system you should review the configuration prerequisites, confirm support for your host operating systems, and be aware of object limits that might impact specific configuration.

Before you configure SnapMirror active sync, you should confirm that your ASA r2 clusters are in the proper peering relationships and meet other configuration requirements.

You can use ONTAP Mediator or ONTAP Cloud Mediator to monitor the health of your cluster and enable business continuity. If you are using ONTAP Mediator, you must install it on your host. If you are using ONTAP Cloud Mediator, you can skip this step.

You must configure ONTAP mediator or ONTAP cloud mediator before you can begin using it with SnapMirror active sync for cluster monitoring.

Configure SnapMirror active sync to create a copy of your data at a secondary site and enable your host applications to automatically and transparently fail over in the event of a disaster.