Deleting a Replication

Delete a File Storage replication resource.

Important

Deleting the replication resource also deletes its associated replication target. If the source file system and replication resource aren't available (such as in the case of an outage), then delete the replication target to make the target file system exportable for failover.

When you delete a replication resource, you can specify which delete mode you want to use. File Storage replication offers three modes to give you the most flexibility for your data recovery requirements. Delete modes aren't available when deleting a replication target. During a disaster recovery operation where the source availability domain isn't available, the replication resource isn't accessible, and the replication process stops.

Graceful delete
  • If the replication is capturing, transferring, or applying, finish and then delete the replication.
  • If the replication is idle, delete the replication immediately.
Best for data safety. This option is moderately fast depending on how much data is being replicated. This option is called finish_cycle_if_capturing_or_applying by the File Storage API.
Replicate and delete
  • If the replication is capturing, transferring, or applying, finish the current cycle, start and finish one more cycle, and then delete the replication.
  • If the replication is idle, start and finish one more cycle, and then delete the replication.
Best for testing failover. This option is slowest, depending on how much data is being replicated and whether a delta cycle is already in progress when you delete the replication. This option is called one_more_cycle by the File Storage API.
Apply and delete
  • If the replication is applying or transferring, finish and then delete the replication.
  • If the replication is capturing or idle, delete the replication immediately.
Best for data safety during disaster recovery. This option is moderately fast depending on how much data is being replicated. This option is called finish_cycle_if_applying by the File Storage API.