About Replication Policy for Accounts Created Before March 2018

Important:

This topic applies to accounts created before March 2018.

For the accounts created after March 2018, the replication policy for the account is set to any, by default.

If your account was created before March 2018, then you must select a replication policy for your account after activating your Storage Classic Subscription. This replication policy 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.

Note:

See About Guidelines for Selecting a Replication Policy before you select a replication policy for your account.

You can select a replication policy by using the following interfaces:

Interface	Resources
Web Console (Not available on Oracle Cloud at Customer)	See Selecting a Replication Policy for Your Account Using the Web Console.
RESTful API	See Selecting a Replication Policy for Your Account Using the REST API.

About Guidelines for Selecting a Replication Policy

Read these guidelines before you select 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 account.
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 unavailable) is acceptable.
Georeplication policies: These policies specify a primary DC that hosts your account, and 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, read requests that are sent 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 specifies 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 that specifies the primary DC that hosts your other services that use Oracle Cloud Infrastructure Object Storage Classic the most.

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

When you select the replication policy for your account, keep in mind any security, legal, and regulatory requirements that may apply to your data.

Selecting a Replication Policy for Your Account Using the Web Console

Read the guidelines carefully, and pick a replication policy that serves your business requirements.

Sign in to your Oracle Cloud account.
If you see Infrastructure Classic at the top of the page when you sign in to Oracle Cloud, then you are using the Infrastructure Classic Console to access your services and your subscription does not support access to the Infrastructure Console. See Signing In to Your Cloud Account in Getting Started with Oracle Cloud.

If you can access the service from the Infrastructure Console, see Signing In to the Console in Oracle Cloud Infrastructure documentation.
Look for Storage, and from the Actions menu, select Open Service Console.
Click Storage.
The Service Details page displays the details of your Oracle Cloud Infrastructure Object Storage Classic account.
- If a replication policy has not yet been selected for your account, then the Guidelines for Selecting a Replication Policy dialog box appears.
- If the Guidelines for Selecting a Replication Policy dialog box does not appear, a replication policy has already been selected for your account. 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.
Caution:
After you select a replication policy, you can’t change it. Select the policy carefully.

From the drop-down list at the bottom of the dialog box, select a replication policy.
After you select a replication policy, click Set Policy.
The Oracle Cloud Infrastructure Object Storage Classic web console is displayed.
Expand the Account Information pane.
The selected georeplication policy is displayed.

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

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

Finding the Data Center-Specific URL for Your Account

Select the data center to set the replication policy for your account.

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`
LAD	Sao Paulo, Brazil	`brdc1`

Example: em2

Construct the data center-specific URL for your account.
Format:

https://dataCenterCode.storage.oraclecloud.com/v1/Storage-account_name

For traditional accounts, the account name and the identity domain name are the same.

Example:

https://em2.storage.oraclecloud.com/v1/Storage-acme

Selecting a Replication Policy for Your Account Using the REST API

Find out the data center-specific URL for your account. See Finding the Data Center-Specific URL for Your Account.
Request an authentication token. See Authenticating Access When Using the REST API.

Pick a suitable replication policy for your account 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`

For LAD Accounts

Primary Region	Georeplication Region	Policy
Sao Paulo, Brazil	None	`brdc1`

Send a POST request to set the policy for your account:
```
curl -v -X POST \
        -H "X-Auth-Token: token \
        -H "X-Account-Meta-Policy-Georeplication: ReplicationPolicy" 
        data-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 account.
- data-center-specific—URL is the data center-specific URL from Step 1.
Caution:
After you select a replication policy, you can’t change it. Select the policy carefully.
See About 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/Storage-acme
```

The following is an example of the output of this command:

> POST /v1/Storage-acme 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 account, Verifying the Replication Policy for Your Service Instance.

You can now start creating containers and uploading objects in your account. See Creating Containers.