5 Frequently Asked Questions for Object Storage Classic

This section provides answers to frequently asked questions (FAQ) for Oracle Cloud Infrastructure Object Storage Classic.

Topics:

How can I find the REST Endpoint URL of my Oracle Cloud Infrastructure Object Storage Classic instance?

See Finding the REST Endpoint URL for Your Cloud Account.

How can I make objects within a container publicly readable?

By default, all access to objects are private and require credentials. It is possible however, to make all objects within a specific container publicly readable.

To make the objects within a container publicly readable, add the following as an entry to the container's read Access Control List:

.r:*
Also, see Setting Container ACLs.

Note that the Oracle Cloud Infrastructure Object Storage Classic account is accountable for its monthly bandwidth usage, including traffic which is downloading publicly readable objects. If large amounts of traffic are expected, it is better to cache publicly readable objects in a Content Delivery Network (CDN). See How can I use a Content Delivery Network (CDN) to accelerate the downloads of my publicly available content?

How can I increase the upload speed of my large files?

Depending on your network connection, it may take a long time to upload large files.

To decrease the amount of time it takes to upload large files, try locally segmenting a large file into smaller pieces and then uploading the segments serially. Once all segments are uploaded, create a manifest object to map all the pieces together.

For more information about uploading large files by using the static large object approach, see Uploading Large Objects.

How can I use a Content Delivery Network (CDN) to accelerate the downloads of my publicly available content?

A Content Delivery Network (CDN) can be used to accelerate the download rate of objects from a container. It can also limit the egress bandwidth usage of an Oracle Cloud Infrastructure Object Storage Classic account which is serving publicly readable objects. Oracle does not provide CDN functionality with Oracle Cloud Infrastructure Object Storage Classic but customers can use their own third-party CDNs. Third-party CDNs must support Origin Pull and HTTPS in order to work with an Oracle Cloud Infrastructure Object Storage Classic account.

The first step is to make a container publicly readable. See How can I make objects within a container publicly readable?. The next step is to use the URL of the Oracle Cloud Infrastructure Object Storage Classic account as the Origin Server for the third-party CDN.

At this time, private objects cannot be accelerated with a CDN. Additionally, Oracle will not share the SSL certificate for the domains which Oracle Cloud Infrastructure Object Storage Classic accounts are hosted on.

How can I store my Oracle Database backups to Oracle Cloud?

You can use Oracle Database Backup Service, a cloud storage solution from Oracle for storing Oracle Database backups. It is built on top of the Oracle Cloud Infrastructure Object Storage Classic, which provides reliable, secure, and scalable storage. In order to store backups in Oracle Database Backup Service, you have to install the client side Oracle Database Cloud Backup Module from OTN. This module is used with Recovery Manager (RMAN) to ship the backup data to Oracle Database Backup Service.

Note that you cannot use the Oracle Database Cloud Backup Module with Oracle Cloud Infrastructure Object Storage Classic. It can only be used with Oracle Database Backup Service.

Can I delete a container which contains objects?

Before you delete the container, you must first delete the objects in the container. To delete the objects, see Deleting Objects. To delete the container, see Deleting Containers.

How can I replicate data to multiple data centers?

(Not available on Oracle Cloud at Customer)

In Storage Classic accounts created after March 2018, the replication policy is set to any for the account, by default. For more information, see About Replication Policy for Your Object Storage Classic Instance.

If your account was created before March 2018, then you can enable geo-replication policy on your account to automatically replicate data to multiple data centers. You can do this by selecting a replication policy for your account. The replication policy defines the site where your data is replicated to and guarantees data consistency across multiple sites. For example, if you select the Chicago-Ashburn policy, you configure Chicago, Illinois, U.S.A as the primary site and Ashburn, Virginia, U.S.A. as the secondary site for your Oracle Cloud Infrastructure Object Storage Classic account. For more information, see About Replication Policy for Accounts Created Before March 2018.

How do I find out the replication policy for my account?

(Not available on Oracle Cloud at Customer)

Send a HEAD request to your account. Alternatively, you can view the replication policy in the Oracle Cloud Infrastructure Object Storage Classic console.

See Verifying the Replication Policy for Your Service Instance.

Are there any charges for the storage space used by replicated data stored in the secondary data center?

(Not available on Oracle Cloud at Customer)

You'll be charged for storage space used in each site — primary and secondary. You’ll also be billed for the data transfer across the primary and secondary data centers.

Can I change the replication policy for my account?

(Not available on Oracle Cloud at Customer)

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

If your account was created before March 2018, then you cannot change the replication policy later.

Can I change the replication policy for a container?

You can set the container-specific replication policy when you create a container. You cannot change the container-specific replication policy later.

How soon after a successful write operation is data replicated to the secondary data center?

(Not available on Oracle Cloud at Customer)

After a successful write operation, your data is written only to the primary data center and it is asynchronously replicated to the secondary data center. The primary and secondary sites are always eventually consistent.

Is replication to the secondary data center guaranteed for every write operation?

(Not available on Oracle Cloud at Customer)

By default, data is eventually consistent across the primary and secondary data centers. For every write operation, when an object or container is created or modified, it is not replicated instantaneously to the secondary data center. Until the replication is completed, a container or an object's data may not be consistent across the primary and secondary sites. Over time, all changes to all objects or containers are replicated, and the data becomes consistent across the sites.

What happens when the primary site is unavailable?

(Not available on Oracle Cloud at Customer)

When the primary site is unavailable, a transparent failover redirects your global namespace to the secondary site and all your read requests are redirected to the secondary site. You cannot write data to primary site during failover. All your write requests generate the 403 – Forbidden error during failover. When the primary site resumes its operation, a transparent failback redirects your global namespace back to the primary site. You can now write data to the primary site.

This is applicable only for accounts that have selected Chicago-Ashburn or Ashburn-Chicago as their geo-replication policy. The accounts that have selected either Chicago or Ashburn as their geo-replication policy will not have transparent failover.

What happens when a subscription expires?

(Not available on Oracle Cloud at Customer)

Go to Oracle Cloud Services Contracts and Service Descriptions page and look forOracle Platform as a Service (PaaS) and Infrastructure as a Service (IaaS) (Tech Cloud) - Service Descriptions document.

How can I identify if a container is an archive or standard container?

(Not available on Oracle Cloud at Customer)

By default, containers are of the Standard storage class. For an Archive container, the X-Storage-Class header in the container metadata displays the value Archive. See Getting Container Metadata.

How long does it take to restore an archived object?

(Not available on Oracle Cloud at Customer)

It takes up to four hours to restore an archived object. You can track the restoration progress and determine if the object is restored. For more information, see Tracking Restoration of an Object in an Archive Container.

How can I check whether archival or restoration of an object has been completed?

(Not available on Oracle Cloud at Customer)

Send a HEAD request to the object. You can determine the status of the object in the Archive container from the X-Archive-Restore-Status header in the object metadata. For more information, see Finding Out the Status of Objects in an Archive Container.

How can I limit the capacity of a container?

You can set a container quota – in terms of maximum number of objects or maximum number of bytes. See Setting Container Quotas.

How can I find out the storage entitlement for my account?

To find out the storage entitlement for your account, see Viewing Service Details in My Account for Entitlements in Managing and Monitoring Oracle Cloud.

If you have a metered account and would like to know your account balance details, see Viewing Estimated Account Balance Details of Metered Services in Managing and Monitoring Oracle Cloud.

Can I upload dynamic large objects using Oracle Cloud Infrastructure Object Storage Classic?

Support for uploading dynamic large objects is not available in Oracle Cloud Infrastructure Object Storage Classic. You can download existing dynamic large objects from your account in Oracle Cloud Infrastructure Object Storage Classic.

How do I contact Oracle for support?

See Contacting Oracle for Support.