Requirements and limitations when using Data ONTAP in a MetroCluster configuration

Job schedules in a MetroCluster configuration
Because job schedules are not replicated between the MetroCluster clusters, if you create, modify, or delete a job schedule, you must perform the same operation on the partner cluster. This ensures that job schedules on both clusters are identical.

Cluster peering from the MetroCluster sites to a third cluster
Because peering configuration is not replicated, if you peer one of the clusters in the MetroCluster configuration to a third cluster outside of that configuration, you must also configure the peering on the partner MetroCluster cluster. This ensures peering can be maintained in the event of a switchover.

Volume creation on a root aggregate
The system will not allow the creation of new volumes on the root aggregate (aggregates with an HA policy of CFO) of a node in a MetroCluster configuration.

Networking and LIF creation guidelines for MetroCluster configurations
You should be aware of how LIFs are created and replicated within the MetroCluster configuration, and you must also know about the requirement for consistency so you can make proper decisions when configuring your network .

Volume or FlexClone command VLDB errors
If a volume or FlexClone volume command (such as volume create or volume delete) fails and the error message indicates that the failure is due to a VLDB error, you should manually retry the job.

Modifying volumes to set NVFAIL in case of switchover
You can modify a volume so that, in event of a MetroCluster switchover, the NVFAIL flag is set on the volume. The NVFAIL flag causes the volume to be fenced off from any modification. This is required for volumes that need to be handled as if committed writes to the volume were lost after the switchover.

Monitoring and protecting database validity by using NVFAIL
The -nvfail parameter of the volume modify command enables Data ONTAP to detect nonvolatile RAM (NVRAM) inconsistencies when the system is booting or after a switchover operation. It also warns you and protects the system against data access and modification until the volume can be manually recovered.

Requirements and limitations when using Data ONTAP in a MetroCluster configuration

More information