Skip to main content

Takeover and serve data from the destination bucket (remote cluster)

Contributors netapp-forry netapp-barbe netapp-aherbin netapp-lenida netapp-ahibbard
PDFs

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.

About this task

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 SnapMirror S3 relationship.

When the disabled source bucket is available again, SnapMirror S3 automatically resynchronizes the contents of the two buckets. It is not necessary to explicitly resynchronize the relationship, as is required for volume SnapMirror deployments.

The takeover operation must be initiated from the remote cluster.

System Manager

Failover from the unavailable bucket and begin serving data:

  1. Click Protection > Relationships, then select SnapMirror S3.

  2. Click Menu options icon, select Failover, then click Failover.

CLI

  1. Initiate a failover operation for the destination bucket:
    snapmirror failover start -destination-path svm_name:/bucket/bucket_name

  2. Verify the status of the failover operation:
    snapmirror show -fields status

    Example
    dest_cluster::> snapmirror failover start -destination-path dest_svm1:/bucket/test-bucket-mirror