When the primary cluster returns to service, you can return write access to data in the cloud to the primary cluster.
About this task
This procedure describes how to fail back to the primary cluster after a long-term failover. All of the steps in a fail back scenario are listed here for context, but only the steps specific to CloudPools are described in detail. For more information about data failover and failback with SyncIQ, see the
OneFS CLI Administration Guide.
Steps
Perform SIQ resync-prep <policy> on the original primary cluster.
Wait until the <policy>_mirror policy exists on the secondary cluster.
Perform SIQ sync of <policy>_mirror on the secondary cluster.
Perform SIQ allow-write of <policy>_mirror on the original primary cluster.
On the secondary cluster, remove write access to the cloud data.
# isi cloud access remove <GUID>
where <GUID> is the GUID of the cluster that originally archived the cloud data. For example: