Selecting a Replication Policy for Your Service Instance

To be able to use Oracle Cloud Infrastructure Object Storage Classic, your service administrator must select a replication policy for the service instance.

About Georeplication

After activating your Oracle Cloud Infrastructure Object Storage Classic subscription, you must choose a replication policy, which defines your primary data center and also specifies whether your data should be replicated to a geographically distant (secondary) data center. Data is written to the primary data center and replicated asynchronously to the secondary data center. The primary and secondary data centers are eventually consistent. In addition to being billed for storage capacity used at each data center, you will also be billed for bandwidth used during replication between data centers.

Guidelines for Selecting a Replication Policy

Read these guidelines before selecting a replication policy.

Oracle provides several replication policies. Broadly, they belong to one of the following types:

  • Policies that have no georeplication: These policies specify only the primary data center (DC) that hosts your service instance.

    All read and write requests go to the primary DC, always. If the primary DC is unavailable, then the requests fail.

    Such a policy may be adequate if you have standard data-durability requirements and if an occasional failure of read requests (when the primary DC is down) is acceptable.

  • Georeplication policies: These policies specify a primary DC that hosts your service instance as well as a geographically distant, georeplication DC.

    Write requests that you send to the global namespace URL are routed to the primary DC. Data that you write is replicated automatically, but asynchronously, to the georeplication DC. The primary and secondary DCs are eventually consistent.

    If the primary DC is unavailable, then write requests fail with the 403 – Forbidden error, but read requests are routed to the georeplication DC. When the primary DC is available again, requests to the global namespace URL are routed to the primary DC.

    You’ll be billed for the sum of the capacities used in both DCs and for the data transfer from the primary to the georeplication DC.

    A policy that has a georeplication DC is ideal if you have advanced durability requirements for your data or if read requests must succeed always regardless of the state of the primary DC.

For faster data transfer between your other Oracle Cloud services and Oracle Cloud Infrastructure Object Storage Classic, consider selecting a policy with a primary DC that hosts your other services that use Oracle Cloud Infrastructure Object Storage Classic the most.

For example, if Java Cloud Service is provisioned in the Chicago data center, then for faster data transfer between your Java Cloud Service instances and Oracle Cloud Infrastructure Object Storage Classic, select a replication policy that has Chicago (us2) as the primary data center.

When selecting the replication policy for your service instance, keep in mind any security, legal, and regulatory requirements that may apply to your data.

Selecting a Replication Policy Using the Web Console

  1. Sign in to the Oracle Cloud My Services application. See Signing In to the My Services Application in Managing and Monitoring Oracle Cloud.

    The My Services Dashboard is displayed. It lists the services that are assigned to your account.

  2. Look for Storage, and from the Actions Select any of the actions displayed to perform the corresponding activity. menu, select Open Service Console.
  3. Click Storage. Alternatively, select View Details from the Actions Select any of the actions displayed to perform the relevant corresponding activity. menu.

    The Service Details page appears. You can see the details of your Oracle Cloud Infrastructure Object Storage Classic account here.

    • If a replication policy has not yet been set for your service instance, then a Guidelines for Selecting a Replication Policy dialog box appears.
    • If the Guidelines for Selecting a Replication Policy dialog box is not displayed, then that means a replication policy has already been selected for your service instance. Skip the remainder of this procedure. You can start creating and managing containers and objects in the service.

    Note:

    If you try to create containers and objects without first selecting a replication policy, then the requests you send to the service will fail with the 403 Forbidden error.
  4. Read the guidelines carefully, and pick a replication policy that serves your business requirements.
  5. From the drop-down list at the bottom of the dialog box, select the required replication policy.

    Caution:

    Once you select a replication policy, you can’t change it. So select your policy carefully.
  6. After selecting a replication policy, click Set Policy.

    The Oracle Cloud Infrastructure Object Storage Classic web console is displayed.

  7. Expand the Account Information pane.

    The selected georeplication policy is displayed.

    If the policy field is blank initially, then refresh the browser.

You can now start creating containers and objects in Oracle Cloud Infrastructure Object Storage Classic.

Selecting a Replication Policy Using the REST API

  1. Find out the data center-specific URL for your account.

    1. Sign in to the Oracle Cloud My Services application.

    2. Look for Storage.

    3. Select View Details from the Actions Select any of the actions displayed to perform the relevant corresponding activity. menu.

    4. Look for the REST Endpoint field under Additional Information. Make a note of the REST endpoint URL of your service instance.

      Example: https://foo.storage.oraclecloud.com/v1/myservice-bar

    5. Look for the Data Center field under Additional Information.

      Make a note of the data center where the service is provisioned.

      Example: EMEA Commercial 2 - Amsterdam

    6. Determine the data center code:

      Region Location Code
      US Commercial 2 Chicago, Il. US us2
      US Commercial 6 Ashburn, Va. US us6
      US Commercial Central Illinois, US uscom-central-1
      EMEA Commercial 2 Amsterdam, NL. EMEA em2
      EMEA Commercial 3 Slough, UK. EMEA em3
      Sydney Sydney, Australia aucom-east-1

      Example: em2

    7. Replace the first part in the REST endpoint URL identified in step d with the data center code determined in the previous step.

      Example:

      In https://foo.storage.oraclecloud.com/v1/myservice-bar, replace the first foo with em2 to derive the following data-center-specific REST endpoint URL:

      https://em2.storage.oraclecloud.com/v1/myservice-bar

  2. Request an authentication token. See Authenticating Access When Using the REST API.

  3. Pick a suitable replication policy for your service instance from one of the following tables, based on the region where your account is provisioned:

    For US Accounts

    Primary Region Georeplication Region Policy
    Chicago, Il. US None us2
    Ashburn, Va. US None us6
    US Commercial Central, Illinois, US None uscom-central-1
    Chicago, Il. US Ashburn, Va. US us2–us6

    Available only for entitlement-based accounts

    Ashburn, Va. US Chicago, Il. US us6–us2

    Available only for entitlement-based accounts

    Ashburn, Va. US US Commercial Central, Illinois, US us6–uscom-central-1

    Available only for entitlement-based accounts

    Chicago, Il. US US Commercial Central, Illinois, US us2–uscom-central-1

    Available only for entitlement-based accounts

    US Commercial Central, Illinois, US Ashburn, Va. US uscom-central-1–us6

    Available only for entitlement-based accounts

    US Commercial Central, Illinois, US Chicago, Il. US uscom-central-1–us2

    Available only for entitlement-based accounts

    Chicago, Il. US Ashburn, Va. US us2-uscom-east-1
    Ashburn, Va. US None us6-uscom-east-1
    Ashburn, Va. US None uscom-east-1-us6
    Ashburn, Va. US Chicago, Il. US uscom-east-1-us2
    Ashburn, Va. US US Commercial Central, Illinois, US uscom-east-1-uscom-central-1
    US Commercial Central, Illinois, US Ashburn, Va. US uscom-central-1-uscom-east-1
    Ashburn, Va. US None uscom-east-1

    For EMEA Accounts

    Primary Region Georeplication Region Policy
    Amsterdam, NL. EMEA None em2
    Slough, UK. EMEA None em3
    Amsterdam, NL. EMEA Slough, UK. EMEA em2–em3

    Available only for entitlement-based accounts

    Slough, UK. EMEA Amsterdam, NL. EMEA em3–em2

    Available only for entitlement-based accounts

    Amsterdam, NL. AD1 EMEA Amsterdam, NL. EMEA eucom-north-1–em2
    Slough, UK. EMEA London, UK. AD1 EMEA em3-gbcom-south-1
    London, UK. AD1 EMEA None gbcom-south-1
    London, UK. AD1 EMEA Amsterdam, NL. AD1 EMEA gbcom-south-1-eucom-north-1
    Amsterdam, NL. AD1 EMEA Slough, UK. EMEA eucom-north-1-em3
    Amsterdam, NL. EMEA Amsterdam, NL. AD1 EMEA em2-eucom-north-1
    Slough, UK. EMEA Amsterdam, NL. AD1 EMEA em3-eucom-north-1
    Amsterdam, NL. EMEA London, UK. AD1 EMEA em2-gbcom-south-1
    Amsterdam, NL. AD1 EMEA None eucom-north-1
    Amsterdam, NL. AD1 EMEA London, UK. AD1 EMEA eucom-north-1-gbcom-south-1
    London, UK. AD1 EMEA Slough, UK. EMEA gbcom-south-1-em3
    London, UK. AD1 EMEA Amsterdam, NL. EMEA gbcom-south-1-em2

    For APAC Accounts

    Primary Region Georeplication Region Policy
    Sydney, Australia None aucom-east-1
  4. Send a POST request to set the policy for your service instance:

    curl -v -X POST \
            -H "X-Auth-Token: token \
            -H "X-Account-Meta-Policy-Georeplication: ReplicationPolicydata-center-specific—URL     
    • token is the authentication token obtained earlier from Oracle Cloud Infrastructure Object Storage Classic.
    • ReplicationPolicy is the value of the replication policy to be set for your service instance.
    • data-center-specific—URL is the data center-specific URL from Step 1.

    Caution:

    Once you select a replication policy, you can’t change it. So select your policy carefully.

    See Guidelines for Selecting a Replication Policy.

    Example:

    curl -v -X POST \
         -H "X-Auth-Token: AUTH_tkb4fdf39c92e9f62cca9b7c196f8b6e6b" \
         -H "X-Account-Meta-Policy-Georeplication: us2" \
         https://us2.storage.oraclecloud.com/v1/myservice-bar
    
The following is an example of the output of this command:
> POST /v1/myservice-bar HTTP/1.1
> User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.14.0.0 zlib/1.2.3 libidn/1.18 libssh2/1.4.2
> Host: us2.storage.oraclecloud.com
> Accept: */*
> X-Auth-Token: AUTH_tkb4fdf39c92e9f62cca9b7c196f8b6e6b
> X-Account-Meta-Policy-Georeplication: us2
>
< HTTP/1.1 204 No Content
< Date: Fri, 06 Nov 2016 11:44:29 GMT
< Content-Length: 0
< Content-Type: text/html; charset=UTF-8
< X-Trans-Id: tx0742dd38e3a445529860a-0054f9931d
< Cache-Control: no-cache
< Pragma: no-cache
< Content-Language: en
<

To find out the replication policy that’s selected for your Oracle Cloud Infrastructure Object Storage Classic instance, see Verifying the Replication Policy Selected for Your Service Instance.

You can now start creating containers and objects in Oracle Cloud Infrastructure Object Storage Classic.

Verifying the Replication Policy Selected for Your Service Instance

Using the Web Console

To find out the replication policy that’s selected for your Oracle Cloud Infrastructure Object Storage Classic instance, sign in to the web console. Expand Account Information. The details of your account are displayed in the Account Information pane. Look for the Georeplication Policy field.

Using the REST API

Send a HEAD request to view the replication policy details for your service instance. Look for the header X-Account-Meta-Policy-Georeplication in the output. See Getting Account Metadata.