Enabling Replication When You Update a Volume

To enable replication for an existing volume on Compute Cloud@Customer, configure a replica when you update the volume the same way you configure a replica when you create a volume.

If a replica is already configured for the volume, you cannot configure a second replica. Each volume can have only one replica. To update the replica configuration, see Updating Replication Configuration for a Volume.

  • Use the following procedure to enable replication for an existing boot or block volume.

    1. In the Compute Cloud@Customer Console navigation menu, select Block Storage, then select either Block Volumes or Boot Volumes.

    2. Check whether replication is already configured for the volume for which you want to enable replication.

      If the value in the Replicas column is Off, continue with the next step in this procedure.

      If the value in the Replicas column is On, then replication is already configured for this volume. You cannot change the replication configuration by editing the volume. See Updating Replication Configuration for a Volume.

    3. Select the Actions menu and select Edit.

    4. In the Edit Volume dialog, scroll to the Replication section.

      Provide the following information:

      • Select the On button.

      • Select an Availability Domain from the drop-down menu.

        Availability Domains are in the form infrastructure_ID:AD-1, where infrastructure_ID identifies the target infrastructure.

      • Enter a name for the replica.

        The display name can be a maximum of 255 characters, does not need to be unique, and is changeable.

      • (Optional) Select the Encryption button to enable encryption using Oracle-managed keys.

    5. Select the Save Changes button.

      On the details page of the volume, the replica is listed in the Resources section.

  • First, check whether the volume for which you want to configure replication already has a replica. You can configure replication only for a volume that does not already have replication configured.

    Use the oci bv volume get command to confirm that replication is not configured for this volume. Use the --block-volume-replicas option with the oci bv volume update command to configure replication for the specified block volume. Although the value of the --block-volume-replicas option is an array, do not specify more than one replica. A volume can have only one replica.

    oci bv volume get --volume-id volume_to_update_OCID
    oci bv volume update --volume-id volume_to_update_OCID --block-volume-replicas '[{"availabilityDomain":"serial_number:AD-1","displayName":"Sample_Replica"}]'

    Use the oci bv boot-volume get command to confirm that replication is not configured for this volume. Use the --boot-volume-replicas option with the oci bv boot-volume update command to configure replication for the specified boot volume. Although the value of the --boot-volume-replicas option is an array, do not specify more than one replica. A volume can have only one replica.

    oci bv boot-volume get --boot-volume-id volume_to_update_OCID
    oci bv boot-volume update --boot-volume-id volume_to_update_OCID --boot-volume-replicas '[{"availabilityDomain":"serial_number:AD-1","displayName":"Sample_Replica"}]'

    For a complete list of CLI commands, flags, and options, see the Command Line Reference.

  • First, check whether the volume for which you want to configure replication already has a replica. You can configure replication only for a volume that does not already have replication configured.

    Use the GetVolume operation to confirm that replication is not configured for this volume. Use the UpdateVolume operation to update a block volume, specifying blockVolumeReplicas in UpdateVolumeDetails.

    Use the GetBootVolume operation to confirm that replication is not configured for this volume. Use the UpdateBootVolume operation to update a boot volume, specifying bootVolumeReplicas in UpdateBootVolumeDetails.

    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.