Takeover and serve data from the destination bucket (local cluster)
If the data in a source bucket becomes unavailable, you can break the SnapMirror relationship to make the destination bucket writable and begin serving data.
When a takeover operation is performed, source bucket is converted to read-only and original destination bucket is converted to read-write, thereby reversing the S3 SnapMirror relationship.
When the disabled source bucket is available again, S3 SnapMirror automatically resynchronizes the contents of the two buckets. You don’t need to explicitly resynchronize the relationship, as is required for standard volume SnapMirror deployments.
If the destination bucket is on a remote cluster, the takeover operation must be initiated from the remote cluster.
System Manager procedure
Failover from the unavailable bucket and begin serving data:
Click Protection > Relationships, then select S3 SnapMirror.
Click , select Failover, then click Failover.
Initiate a failover operation for the destination bucket:
snapmirror failover start -destination-path svm_name:/bucket/bucket_name
Verify the status of the failover operation:
snapmirror show -fields status
clusterA::> snapmirror failover start -destination-path vs1:/bucket/test-bucket-mirror