Amazon FSx for NetApp ONTAP Snap Mirror Configuration Error

Question

I followed the below link to setup snapmirror successfully, but when I started a failover, it returned the following error.
FSXID**************::> snapmirror failover start -destination-path fsx:destVol Error: command failed: SnapMirror Failover is only supported for endpoint type Consistency group.

How do you setup a snapmirror failover?

mjinglis · Accepted Answer

The ‘snapmirror failover’ command is not supported within FSxN.
To perform a failover, you need to quiesce the source system, then break the snapmirror on the target location. Once you break the relationship the volume(s) on the target then becomes read/write.
https://docs.aws.amazon.com/fsx/latest/ONTAPGuide/migrating-fsx-ontap-snapmirror.html#cutover

If you need to reestablish a sync back to the original source, you should still see the snapmirror relationship (but in a broken status). Perform a resync with the source and destinations reversed from the original relationship.

re:Post Agent · Answer

The error you're encountering suggests that you're trying to perform a SnapMirror failover on a configuration that doesn't support it directly. SnapMirror failover is typically used for disaster recovery scenarios and is only supported for specific endpoint types, particularly Consistency Groups.

To set up a SnapMirror configuration that supports failover, you need to ensure you're using the appropriate type of SnapMirror relationship. Here's a general approach to resolve this issue:

1. First, you should verify that you're using a SnapMirror Synchronous relationship, which is required for failover operations.

2. Ensure that you have set up a Consistency Group. Consistency Groups are used to maintain write-order consistency across multiple volumes, which is crucial for failover scenarios.

3. If you haven't set up a Consistency Group, you'll need to create one and include the volumes you want to replicate and potentially fail over.

4. Once you have a Consistency Group set up, you can establish a SnapMirror relationship using this Consistency Group as the endpoint.

5. After setting up the correct type of SnapMirror relationship with a Consistency Group, you should be able to perform failover operations.

If you're not able to use Consistency Groups or if your current setup doesn't support them, you may need to consider alternative approaches for your disaster recovery or high availability needs. This could involve breaking the SnapMirror relationship and promoting the destination volume to take over operations, rather than using the failover command directly.

Remember that SnapMirror configurations can be complex, and the exact steps may vary depending on your specific FSx for NetApp ONTAP setup and requirements. If you continue to experience issues, it's advisable to consult with AWS support or a NetApp specialist to ensure your configuration meets your specific needs and supports the failover functionality you require.  
**Sources**  
[Migrating to FSx for ONTAP using NetApp SnapMirror - FSx for ONTAP](https://docs.aws.amazon.com/fsx/latest/ONTAPGuide/migrating-fsx-ontap-snapmirror.html)  
[Troubleshoot FSx for ONTAP SnapMirror issues | AWS re:Post](https://repost.aws/knowledge-center/fsx-ontap-troubleshoot-snapmirror)  
[FSx for NetApp ONTAP Features – Amazon Web Services](https://aws.amazon.com/fsx/netapp-ontap/features/)

Amazon FSx for NetApp ONTAP Snap Mirror Configuration Error

Relevant content