Take over from the destination ONTAP S3 bucket on the remote cluster
Suggest changes
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.
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.
Although SnapMirror S3 replicates objects from the source bucket to a destination bucket, it does not replicate users, groups, and policies from the source object store to the destination object store.
Users, group policies, permissions, and similar components must be configured on the destination object store so that clients can access the destination bucket during a failover event.
Source and destination users can use the same access and secret keys provided the source keys are manually provided when the user is created on the destination cluster. For example:
vserver object-store-server user create -vserver svm1 -user user1 -access-key "20-characters" -secret-key "40-characters"
Failover from the unavailable bucket and begin serving data:
-
Click Protection > Relationships, then select SnapMirror S3.
-
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 statusExampledest_cluster::> snapmirror failover start -destination-path dest_svm1:/bucket/test-bucket-mirror