CONTAP-639105: Fabricpool Mirror enhancements
Issue
Fabricpool data migration from one cloud tier into another is based these steps within the in ONTAP Fabricpool cluster:
- Mirror Primary object-store cloud-tier bucket to a fresh Mirror cloud tier
- Promote Mirror cloud tier to Primary
- Unmirror the original Primary (now Mirror) cloud tier
The challenges with this process are:
- Metrocluster already requires a Fabricpool mirror for protecting the DR-Partner node from Fabricpool cloud tier access loss during a site outage with Metrocluster Switchover
- Only one Fabricpool Mirror cloud tier can exist at one time, so the procedure to migrate data in a Metrocluster causes a longer time without protection as we cannot attach a 2nd mirror cloud tier
- The unmirror operation is not abort'able, even if the original cloud tier bucket is being decommissioned afterwards anyways. This can cause weeks of wait time during migration projects
