Skip to main content

Moving RMAN backup from the OCI Standard Bucket to Archive Storage - Oracle Cloud

Moving RMAN backup from the OCI Standard Bucket to Archive Storage - Oracle Cloud

Storing large volumes of database backups in Object Storage? Is the data seldom accessed or primarily intended for archival purposes? Now, with the introduction of Archive Storage, we have an opportunity to leverage a cost-effective, long-term, and secure storage solution.

The key distinction between data backup and data archiving lies in the duration of data retention and the frequency of access. Archiving offers prolonged storage with infrequent access. Oracle offers Archive Storage as part of its Oracle Cloud Infrastructure Object Storage service, catering precisely to these requirements. By utilizing Archive Storage, we can retain database backups for extended periods without manual intervention, ensuring compliance with retention policies. Not only does this solution offer cost savings, but it also enables organizations to meet regulatory and compliance obligations effectively.

In this blog post, we will explore how to leverage Archive Storage for database backups on DB Systems within Oracle Cloud Infrastructure (OCI). 
In Previous post I shared how to take Backup of the database on OCI Standard Bucket.

Refer Below:

In Oracle Cloud Infrastructure (OCI), Object Storage offers two storage tiers: Standard Storage and Archive Storage. Each tier is designed to address different storage requirements based on data access patterns, durability, and cost considerations.

Standard Storage:

  1. Use Cases:

    • Frequently accessed data requiring low-latency access times.
    • Data that needs to be readily available for retrieval and processing.
    • Active workloads, application data, backups, and content distribution.

  2. Features:

    • High-performance storage with low-latency access times.
    • Designed for frequent read and write operations.
    • Supports real-time data access and high-throughput workloads.
    • Offers higher availability and durability compared to Archive Storage.

  3. Durability and Availability:

    • Standard Storage is designed for 99.999999999% (11 nines) durability.
    • Provides high availability with redundant storage across multiple fault domains within an OCI region.

  4. Cost:

    • Standard Storage is priced based on usage, including storage capacity and data transfer costs.
    • Typically priced higher than Archive Storage due to its performance and availability features.

Archive Storage:

  1. Use Cases:

    • Data with infrequent access or long-term retention requirements.
    • Compliance archives, backup archives, regulatory data, and historical logs.
    • Data that is accessed less frequently but needs to be retained for compliance or business continuity purposes.

  2. Features:

    • Optimized for data with rare or intermittent access patterns.
    • Lower-cost storage suitable for long-term retention and archival purposes.
    • Provides durable and reliable storage for data preservation over extended periods.
    • Supports standard Object Storage features such as encryption, object versioning, and lifecycle management.

  3. Durability and Availability:

    • Archive Storage offers the same 99.999999999% (11 nines) durability as Standard Storage.
    • Provides slightly lower availability compared to Standard Storage, with retrieval times ranging from minutes to hours.

  4. Cost:

    • Archive Storage is priced significantly lower than Standard Storage, making it cost-effective for storing large volumes of data for long periods.
    • In addition to storage capacity, costs may include data retrieval fees based on the frequency and speed of retrieval.

Choosing Between Standard Storage and Archive Storage:

  1. Access Patterns:

    • Use Standard Storage for frequently accessed data with low-latency access requirements.
    • Use Archive Storage for data with infrequent access patterns or long-term retention needs.

  2. Cost Considerations:

    • Consider the cost-effectiveness of Archive Storage for storing large volumes of data over extended periods.
    • Evaluate the trade-offs between cost and performance when choosing between storage tiers.

  3. Data Retention Requirements:

    • Assess the data retention policies and compliance requirements for your organization.
    • Use Archive Storage for compliant archival and long-term retention needs.

Steps for setting up Archive Storage:


1) I have already my backup taken on the OCI standard Bucket.
2) The pattern of the backup pieces start with PROD.
3) The RMAN backup on the OCI is stored in the below format for storing. file_chunk>DBID>DB_NAME>backuppiece>DATE(YYYY-MM-DD)>



4) Add Policies to managed the object in Compartment.

Allow group Administrators to manage buckets in compartment gold1_compartment
Allow group Administrators to manage objects in compartment gold1_compartment
Allow service objectstorage-ap-hyderabad-1 to manage object-family in compartment gold1_compartment

5) Create a Life Cycle Rule on Object Storage Bucket.

I am using. the pattern as */PROD_*/* --> This means that anything under the directory structure and where it matches the PROD_ folder structure will be moved to archived storage.






6) The rule gets applied immediately and within few minutes we can see our objects being moved to Archive storage.

    






If you like please follow and comment
Labels:

Comments

Post a Comment

Popular posts from this blog

WebLogic migration to OCI using WDT tool

WebLogic migration to OCI using WDT tool Oracle WebLogic Deploy Tool (WDT) is an open-source project designed to simplify and streamline the management of Oracle WebLogic Server domains. With WDT, you can export configuration and application files from one WebLogic Server domain and import them into another, making it a highly effective tool for tasks like migrating on-premises WebLogic configurations to Oracle Cloud. This blog outlines a detailed step-by-step process for using WDT to migrate WebLogic resources and configurations. Supported WLS versions Why Use WDT for Migration? When moving Oracle WebLogic resources from an on-premises environment to Oracle Cloud (or another WebLogic Server), WDT provides an efficient and reliable approach to: Discover and export domain configurations and application binaries. Create reusable models and archives for deployment in a target domain. Key Pre-Requisites Source System: An Oracle WebLogic Server with pre-configured resources such as: Applica...
Post a Comment
Read more

Rename a PDB in Oracle Database Multitenant Architecture in TDE and Non TDE Environment

Rename a PDB in Oracle Database Multitenant Architecture I am sharing a step-by-step guide to help you rename a PDB. This approach uses SQL commands. Without TDE or encryption Wallet Initial Check Check the Current Database Name and Open Mode: SQL > SELECT NAME, OPEN_MODE FROM V$DATABASE; NAME OPEN_MODE --------- -------------------- BEECDB READ WRITE List Current PDBs: SQL > SHOW PDBS; CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 2 PDB$SEED READ ONLY NO 3 FUAT READ WRITE NO We need to RENAME FUAT to BEE  Steps to Rename the PDB Step 1: Export ORACLE_SID Set the Oracle SID to the Container Database (CDB): export ORACLE_SID=BEECDB Step 2: Verify Target PDB Name Availability If the target PDB name is different from the current PDB name, ensure no service exists with the target PDB name. Run SQL to Check Exi...
Post a Comment
Read more

How to make flash work on IE or Edge with IE Compatibility

How to make flash work on IE or Edge with IE Compatibility With flash been ended from 1-Jan-2021, many applications using flash have stopped working the way they were built (like OEM, OBIEE, etc). The option you have to upgrade.  This method will give a workaround in IE or Edge in IE compatibility mode without upgrading. 1. Verify you have installed flash.ocx on your desktop. Typically, flash.ocx file is located in C:\Windows\System32\Macromed\Flash or C:\Windows\SysWOW64\Macromed\Flash according to your laptop OS system. 2. Edit mms.cfg from the location as a System Administrator In the case of the 64bit system, it might have mms.cfg under C:\Windows\SysWOW64\Macromed\Flash 3. Add below options into mms.cfg file. Note: AllowListUrlPattern list is an example. The URLs need to be replaced to your hosts those have Flash pages. SilentAutoUpdateEnable=0 AutoUpdateDisable=1 EOLUninstallDisable=1 EnableAllowList=1 AllowListUrlPattern=http://www.google.com/ AllowListUrlPattern=http://goo...
Post a Comment
Read more