Cross-Region Volume Replication

The Block Volume service provides you with the capability to perform ongoing automatic asynchronous replication of block volumes and boot volumes to other regions. This feature supports the following scenarios without requiring volume backups:

  • Disaster recovery
  • Migration
  • Business expansion

Limits and Considerations

  • Your tenancy must be subscribed to the destination region for cross-region replication. To subscribe to a region, see Managing Regions.
  • Cross-region replication is not supported for volumes encrypted using Vault encryption keys.
  • You cannot resize a volume with cross-region replication enabled. When resizing a volume, you need to disable cross-region replication, which deletes the volume replica. After the volume is resized, you can reenable cross-region replication for the volume, which starts the replication process starts from scratch.
  • When you enable cross-region replication for a volume, the process includes an initial sync of the data from the source volume to the volume replica. Depending on the volume size and amount of data written to the volume, this sync can take hours.
  • After the initial synchronization process is complete, the replication process is continuous, with the typical Recovery Point Object (RPO) target rate being less than an hour. However, depending on the change rate of data on the source volume, the RPO can vary. For example, the RPO can be greater than an hour for volumes with a large amount of write I/O operations to the volume.
  • The cross-region replication feature is complementary to the volume backup feature, not a replacement. Volume backups give you a point-in-time snapshot of a volume that enables you to return to a previous version of the volume. Volume replicas give you the current version of the data.

Cost Considerations for Cross-Region Replication

After you enable replication for a volume, the volume will be replicated in the specified region and availability domain. Your bill will include storage costs for the volume replica in the destination region. The volume replica in the destination region is billed using the Block Storage Lower Cost option price, regardless of the volume type in the source region.

Your bill will also include any applicable network costs for the replication process between regions. As part of the replication process, all data being updated on the source volume is transferred to the volume replica, so volumes with continual updates incur higher network costs.

You can see the amount of data transferred for a volume during replication in the Console.

To see the amount of data transferred from the replication process

  1. Open the navigation menu. Under Core Infrastructure, go to Block Storage and click Block Volume Replicas.
  2. Click the replica that you want to see the amount of data transferred for. On the Replicas Details page, the Total Data Transferred field displays the amount of data, in GBs, that has been transferred during the replication process for the volume. This number includes all data from the point that volume replication was enabled to now.

See Oracle Storage Cloud Pricing and Oracle Networking Cloud Pricing for information about pricing.

Replication Target Regions

When you enable replication for a volume, you select a destination region to replicate the volume to. The source region for the volume to replicate determines the target regions available to select as destination region. The following table lists the source region and target regions available for volume replication.

Note

If your tenancy is not subscribed to any of the target regions for the source region, no regions are displayed in the destination region list. To subscribe to a region, see Managing Regions.
Source Region Target Region
Australia East (Sydney)
  • Australia Southeast (Melbourne)
Australia Southeast (Melbourne)
  • Australia East (Sydney)
Brazil East (Sao Paulo)
  • US East (Ashburn)
  • Chile (Santiago)
Canada Southeast (Montreal)
  • Canada Southeast (Toronto)
Canada Southeast (Toronto)
  • Canada Southeast (Montreal)
Chile (Santiago)
  • Brazil East (Sao Paulo)
Germany Central (Frankfurt)
  • Netherlands Northwest (Amsterdam)
  • Switzerland North (Zurich)
  • UK South (London)
India West (Mumbai)
  • India South (Hyderabad)
India South (Hyderabad)
  • India West (Mumbai)
Japan Central (Osaka)
  • Japan East (Tokyo)
Japan East (Tokyo)
  • Japan Central (Osaka)
  • South Korea Central (Seoul)
Netherlands Northwest (Amsterdam)
  • Germany Central (Frankfurt)
  • UK South (London)
  • US East (Ashburn)
Saudi Arabia West (Jeddah)
  • UAE East (Dubai)
South Korea Central (Seoul)
  • Japan East (Tokyo)
  • South Korea North (Chuncheon)
South Korea North (Chuncheon)
  • South Korea Central (Seoul)
Switzerland North (Zurich)
  • Germany Central (Frankfurt)
  • UK South (London)
UAE East (Dubai)
  • Saudi Arabia West (Jeddah)
UK South (London)
  • Germany Central (Frankfurt)
  • Netherlands Northwest (Amsterdam)
  • Switzerland North (Zurich)
  • UK West (Newport)
  • US East (Ashburn)
UK West (Newport)
  • UK South (London)
US East (Ashburn)
  • Brazil East (Sao Paulo)
  • Netherlands Northwest (Amsterdam)
  • UK South (London)
  • US West (Phoenix)
US West (Phoenix)
  • US East (Ashburn)
  • US West (San Jose)
US West (San Jose)
  • US West (Phoenix)

Tagging Resources

You can apply tags to your resources to help you organize them according to your business needs. You can update the resource later with the desired tags. For general information about applying tags, see Resource Tags. Any tags applied to the source volume are replicated to the volume replica in the destination region.

Required IAM Policy

To use Oracle Cloud Infrastructure, you must be granted security access in a policy  by an administrator. This access is required whether you're using the Console or the REST API with an SDK, CLI, or other tool. If you get a message that you don’t have permission or are unauthorized, verify with your administrator what type of access you have and which compartment  to work in.

For administrators: The policy in Let volume admins manage block volumes, backups, and volume groups lets the specified group do everything with block volumes, backups, and volume groups.

If you're new to policies, see Getting Started with Policies and Common Policies. For reference material about writing policies for instances, cloud networks, or other Core Services API resources, see Details for the Core Services.

Cross Region Replication - Using the Console

Block Volume Replicas

Use the Console procedures in this section for block volume replicas.

To enable cross-region replication for a volume

Use the steps described in this procedure to enable cross-region replication on an existing volume. You can also enable cross-region replication when you create a volume, see Creating a Volume.

  1. Open the navigation menu and click Storage. Under Block Storage, click Block Volumes.
  2. Click the block volume that you want to enable replication for.

  3. Click Edit.
  4. In the Cross Region Replication section, select ON.
  5. Select the region you want to replicate the volume to, the availability domain to place the volume replica in, and then specify the name for the volume replica.
  6. Check CONFIRM to acknowledge the cost warning.
  7. Click Save Changes.

To update the destination region or availability domain replication settings for a volume

To change the destination region or availability domain for cross-region replication you need to first turn cross-region replication off for a volume. Then specify the new region and availability domain selections when you turn cross-region replication on again.

  1. Open the navigation menu and click Storage. Under Block Storage, click Block Volumes.
  2. Click the block volume that you want to change the replication settings for.

  3. Click Edit.
  4. In the Cross Region Replication section, select OFF.
  5. Check CONFIRM to acknowledge the that volume replica will be deleted.
  6. Click Save Changes.

  7. Click Edit.
  8. In the Cross Region Replication section, select ON.
  9. Select the region you want to replicate the volume to, the availability domain to place the volume replica in, and then specify the name for the volume replica.
  10. Check CONFIRM to acknowledge the cost warning.
  11. Click Save Changes.

To disable cross-region replication for a volume
  1. Open the navigation menu and click Storage. Under Block Storage, click Block Volumes.
  2. Click the block volume that you want to disable replication for.

  3. Click Edit.
  4. In the Cross Region Replication section, select OFF.
  5. Check CONFIRM to acknowledge the that volume replica will be deleted.
  6. Click Save Changes.

To activate a volume replica

To create a new volume from a volume replica, you need to activate the replica. The activation process creates a new volume by cloning the replica.

  1. Open the navigation menu and click Storage. Under Block Storage, click Block Volume Replicas. Ensure that you are in correct destination region that contains the volume replica you want to activate.
  2. Click the replica that you want to activate.

  3. Click Activate to open the Activate Volume Replica form.
  4. On the Activate Volume Replica, specify the settings for the new volume, including:
    • Name
    • Compartment
    • Size and performance settings
    • Backup policy
    • Volume replication
    • Encryption
    • Tags
  5. Click Create. The new volume will appear in the block volumes list, in the provisioning state.
To monitor a replica's status

The volume replica's details page provides information about the replica's status.

  1. Open the navigation menu and click Storage. Under Block Storage, click Block Volume Replicas. Ensure that you are in the destination region containing the volume replica that you want to view.
  2. Click the replica that you're interested in.

  3. The replica details page displays the following relevant fields:
    • Last Sync: The time of the last data synchronization from the source volume to the replica.
    • Total Data Transfered: The amount of data, in GBs, that has been transferred during the replication process for the volume. This includes all data from the point that volume replication was enabled to now.
To failback a volume replica to the source region

To failback a volume replica to the source region, you need activate the volume replica in the destination region, with volume replication enabled, and select the original source region as the target region for replication.

  1. Open the navigation menu and click Storage. Under Block Storage, click Block Volume Replicas. Ensure that you are in correct destination region that contains the volume replica you want to activate.
  2. Click the replica that you want to activate.

  3. Click Activate to open the Activate Volume Replica form.
  4. On the Activate Volume Replica, specify the settings for the new volume, including:
    • Name
    • Compartment
    • Size and performance settings
    • Backup policy
    • Volume replication
    • Encryption
    • Tags

    Ensure that Volume Replication is enabled, and select the original source region.

  5. Click Create. The new volume will appear in the block volumes list, in the provisioning state. Once the initial synchronization finishes, the failback process is complete, and you can use the volume in the original source region.

Boot Volume Replicas

Use the Console procedures in this section for boot volume replicas.

To enable cross-region replication for a boot volume

Use the steps described in this procedure to enable cross-region replication on an existing boot volume.

  1. Open the navigation menu and click Storage. Under Block Storage, click Block Volumes. In the Block Storage menu on the sidebar, click Boot Volumes.
  2. Click the boot volume that you want to enable replication for.

  3. Click Edit.
  4. In the Cross Region Replication section, select ON.
  5. Select the region you want to replicate the boot volume to, the availability domain to place the boot volume replica in, and then specify the name for the boot volume replica.
  6. Check CONFIRM to acknowledge the cost warning.
  7. Click Save Changes.

To update the destination region or availability domain replication settings for a boot volume

To change the destination region or availability domain for cross-region replication you need to first turn cross-region replication off for a boot volume. Then specify the new region and availability domain selections when you turn cross-region replication on again.

  1. Open the navigation menu and click Storage. Under Block Storage, click Block Volumes. In the Block Storage menu on the sidebar, click Boot Volumes.
  2. Click the boot volume that you want to change the replication settings for.

  3. Click Edit.
  4. In the Cross Region Replication section, select OFF.
  5. Check CONFIRM to acknowledge the that boot volume replica will be deleted.
  6. Click Save Changes.

  7. Click Edit.
  8. In the Cross Region Replication section, select ON.
  9. Select the region you want to replicate the boot volume to, the availability domain to place the boot volume replica in, and then specify the name for the boot volume replica.
  10. Check CONFIRM to acknowledge the cost warning.
  11. Click Save Changes.

To disable cross-region replication for a boot volume
  1. Open the navigation menu and click Storage. Under Block Storage, click Block Volumes. In the Block Storage menu on the sidebar, click Boot Volumes.
  2. Click the boot volume that you want to disable replication for.

  3. Click Edit.
  4. In the Cross Region Replication section, select OFF.
  5. Check CONFIRM to acknowledge the that boot volume replica will be deleted.
  6. Click Save Changes.

To activate a boot volume replica

To create a new volume from a volume replica, you need to activate the replica. The activation process creates a new volume by cloning the replica.

  1. Open the navigation menu and click Storage. Under Block Storage, click Block Volumes. In the Block Storage menu on the sidebar, click Boot Volume Replicas. Ensure that you are in correct destination region that contains the boot volume replica you want to activate.
  2. Click the boot volume replica that you want to activate.

  3. Click Activate to open the Activate Volume Replica form.
  4. On the Activate Volume Replica, specify the settings for the new volume, including:
    • Name
    • Compartment
    • Size and performance settings
    • Backup policy
    • Volume replication
    • Encryption
    • Tags
  5. Click Create. The new volume will appear in the boot volumes list, in the provisioning state.
To monitor a boot volume replica's status

The boot volume replica's details page provides information about the replica's status.

  1. Open the navigation menu and click Storage. Under Block Storage, click Block Volumes. In the Block Storage menu on the sidebar, click Boot Volume Replicas. Ensure that you are in the destination region containing the boot volume replica that you want to view.
  2. Click the replica that you're interested in.

  3. The replica details page displays the following relevant fields:
    • Last Sync: The time of the last data synchronization from the source boot volume to the replica.
    • Total Data Transfered: The amount of data, in GBs, that has been transferred during the replication process for the boot volume. This includes all data from the point that cross-region replication was enabled to now.
To failback a volume replica to the source region

To failback a boot volume replica to the source region, you need activate the boot volume replica in the destination region, with volume replication enabled, and select the original source region as the target region for replication.

  1. Open the navigation menu and click Storage. Under Block Storage, click Block Volumes. In the Block Storage menu on the sidebar, click Boot Volume Replicas. Ensure that you are in correct destination region that contains the boot volume replica you want to activate.
  2. Click the replica that you want to activate.

  3. Click Activate to open the Activate Volume Replica form.
  4. On the Activate Volume Replica, specify the settings for the new boot volume, including:
    • Name
    • Compartment
    • Size and performance settings
    • Backup policy
    • Volume replication
    • Encryption
    • Tags

    Ensure that Volume Replication is enabled, and select the original source region.

  5. Click Create. The new boot volume will appear in the boot volumes list, in the provisioning state. Once the initial synchronization finishes, the failback process is complete, and you can use the boot volume in the original source region.

Using the CLI

For information about using the CLI, see Command Line Interface (CLI).

Block Volume Operations

Use the following operations for cross-region replication of block volumes.

To enable cross-region replication when creating a block volume

Open a command prompt and run:

oci bv volume create --compartment-id <compartment_ID> --block-volume-replicas '[{"displayName":"<display_name>","availabilityDomain":"<availability-domain_ID>"}]' 

For example:

oci bv volume create --compartment-id ocid1.compartment.oc1.phx.<unique_ID> --block-volume-replicas '[{"displayName":"Sample_Replica","availabilityDomain":"pjBI:US-ASHBURN-AD-1"}]'
To enable cross-region replication when updating a block volume

Open a command prompt and run:

oci bv volume update --volume-id <volume_ID> --block-volume-replicas '[{"displayName":"<display_name>","availabilityDomain":"<availability-domain_ID>"}]' 

For example:

oci bv volume update --volume-id ocid1.volume.oc1.phx.<unique_ID> --block-volume-replicas '[{"displayName":"Sample_Replica","availabilityDomain":"pjBI:US-ASHBURN-AD-1"}]'
To disable cross-region replication for a block volume

Open a command prompt and run:

oci bv volume update --volume-id <volume_ID> --block-volume-replicas '[]' 

For example:

oci bv volume update --volume-id ocid1.volume.oc1.phx.<unique_ID> --block-volume-replicas '[]'
To activate a block volume replica

Open a command prompt and run:

oci bv volume create --source-volume-replica-id  <volume_ID> --compartment-id <compartment_ID> --availability-domain <availability_domain> 

For example:

oci bv volume create --source-volume-replica-id ocid1.blockvolumereplica.oc1.phx.<unique_ID> --compartment-id ocid1.compartment.oc1.phx.<unique_ID> --availability-domain ABbv:PHX-AD-1 
To list block volume replicas

Open a command prompt and run:

oci bv block-volume-replica list --availability-domain <availability_domain> --compartment-id <compartment_ID>

For example:

oci bv block-volume-replica list --availability-domain ABbv:PHX-AD-1 --compartment-id ocid1.compartment.oc1.phx.<unique_ID> 
To retrieve a block volume replica

Open a command prompt and run:

oci bv block-volume-replica get --block-volume-replica-id <block-volume-replica-ID>

For example:

oci bv block-volume-replica get --block-volume-replica-id ocid1.blockvolumereplica.oc1.phx.<unique_ID>

Boot Volume Operations

Use the following operations for cross-region replication of boot volumes.

To enable cross-region replication when creating a boot volume

Open a command prompt and run:

oci bv boot-volume create --source-boot-volume-id <volume_ID> --compartment-id <compartment_ID> --boot-volume-replicas '[{"displayName":"<display_name>","availabilityDomain":"<availability-domain_ID>"}]' 

For example:

oci bv boot-volume create --source-boot-volume-id ocid1.bootvolume.oc1.phx.<unique_ID> --compartment-id ocid1.compartment.oc1.phx.<unique_ID> --boot-volume-replicas '[{"displayName":"Sample_Replica","availabilityDomain":"pjBI:US-ASHBURN-AD-1"}]'
To enable cross-region replication when updating a boot volume

Open a command prompt and run:

oci bv boot-volume update --boot-volume-id <volume_ID> --boot-volume-replicas '[{"displayName":"<display_name>","availabilityDomain":"<availability-domain_ID>"}]' 

For example:

oci bv boot-volume update --boot-volume-id ocid1.bootvolume.oc1.phx.<unique_ID> --boot-volume-replicas '[{"displayName":"Sample_Replica","availabilityDomain":"pjBI:US-ASHBURN-AD-1"}]'
To disable cross-region replication for a boot volume

Open a command prompt and run:

oci bv boot-volume update --boot-volume-id <volume_ID> --boot-volume-replicas '[]' 

For example:

oci bv boot-volume update --boot-volume-id ocid1.bootvolume.oc1.phx.<unique_ID> --boot-volume-replicas '[]'
To activate a boot volume replica

Open a command prompt and run:

oci bv boot-volume create --source-volume-replica-id  <volume_ID> --compartment-id <compartment_ID> --availability-domain <availability_domain> 

For example:

oci bv boot-volume create --source-volume-replica-id ocid1.bootvolumereplica.oc1.phx.<unique_ID> --compartment-id ocid1.compartment.oc1.phx.<unique_ID> --availability-domain ABbv:PHX-AD-1 
To list boot volume replicas

Open a command prompt and run:

oci bv boot-volume-replica list --availability-domain <availability_domain> --compartment-id <compartment_ID>

For example:

oci bv boot-volume-replica list --availability-domain ABbv:PHX-AD-1 --compartment-id ocid1.compartment.oc1.phx.<unique_ID> 
To retrieve a boot volume replica

Open a command prompt and run:

oci bv boot-volume-replica get --boot-volume-replica-id <boot-volume-replica-ID>

For example:

oci bv boot-volume-replica get --boot-volume-replica-id ocid1.bootvolumereplica.oc1.phx.<unique_ID>

Using the API

For information about using the API and signing requests, see REST APIs and Security Credentials. For information about SDKs, see Software Development Kits and Command Line Interface.

Use the following operations to list and retrieve volume replicas:

You can enable cross-region replication for a boot volume or block volume when you create or update a volume. To disable cross-region replication, use the Update operation. To activate a volume replica, use the Create operation and pass the source volume's replica ID.