Oracle Rman Backup

-
Oracle RMAN or the Recovery Manager is the tool provided by Oracle to perform all its database related data protection operations. This include Rman Backups, Restorations and recovery, Flashback, Backup encryption, Duplication and other numerous options. Although a comprehensive article on Rman can be a complex topic, idea of this post is to provide basic understanding of configuring a Oracle rman backup with minimal database administration knowledge.

Oracle Backup Types – Online (Hot) Backups and Offline (Cold) Backups

Rman backup can be either Online backup where backups is taken while the database is open for users and applications to connect and work. Offline backups are a dying concept as more and more systems are not tolerating downtimes to take backups. In order to take online rman backup the database must be in archive log mode.
 SQL> select log_mode from v$database;  
 LOG_MODE  
 ------------  
 ARCHIVELOG  
 SQL>
  • Setting the Oracle database to archivelog mode - https://www.oracle.com/ocom/groups/public/@otn/documents/webcontent/283263.htm
Other than above mentioned, Oracle rman backups can be categorized based on the backup criteria, such full backups, incremental backups, tablespace level, table level etc. For the scope of the document we are referring to full backups here.

Rman Backup Script

Below is a simple Rman backup script which can be used to take a full backup of the database. Purpose of including the script is to discuss the same line by line in order to understand the Rman backup procedure.
 export ORACLE_HOME=/u01/db_1  
 export ORACLE_SID=MIS  
 export PATH=$PATH:$ORACLE_HOME/bin  
 export LD_LIBRARY_PATH=/u01/db_1/lib  
 DPATH=/backup/`date +%Y-%m-%d`  
 mkdir $DPATH  
 chmod -R 777 $DPATH  
 chown oracle:oinstall $DPATH  
 RUN {  
 crosscheck archivelog all;  
 delete archivelog all backed up 1 times to device type disk;  
 CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '$DPATH/%F';  
 ALLOCATE CHANNEL disk1 DEVICE TYPE DISK MAXPIECESIZE 1500M;  
 ALLOCATE CHANNEL disk2 DEVICE TYPE DISK MAXPIECESIZE 1500M;  
 BACKUP FORMAT '$DPATH/bk_u%u_s%s_p%p_t%t' DATABASE plus archivelog;  
 release channel disk1;  
 release channel disk2;  
 }

Exports and other bash commands

- This is to setup the environment for the script. Example is from a Solaris Rman setup and it creates a location on the server to store the Rman backup files. (DPATH==/backup/MIS/`date +%Y-%m-%d`). So daily backups are stored in this folder under the date.
we need to make sure this backup mount point is not from the same storage as the database itself. Other wise a failure in the storage would cause both the database it self and the backups to be lost.

RMAN Run Block

- First two commands of the scripts are for managing the archive logs, which deletes the archivelogs that are already backed up.
Next are the channel allocations. Rman backup client use these channels to backups the database. channel can be tape or disk device based on the backup media used. Here 2 backup channels are declared while setting max backup piece size per channel to 1.5 GB.
Next BACKUP FORMAT '$DPATH/bk_u%u_s%s_p%p_t%t' DATABASE plus archivelog; does perform the actual backup operation. It uses the DPATH location variable to store the backup pieces and the archive logs.
Finally, the two channels are closed by rman.
By scheduling similar script Oracle database can be backed up daily full basis to a given disk location on the servers. By including the archive logs to the Rman backup we are adding the PITR (Point in time Reco every) capability. This allows Rman to recover the restored database from the backups to exact point in time even after the full backup completion time, which minimizes the possible data lose.

Comments

Post a Comment

Popular posts from this blog

ORA-16433: The database or pluggable database must be opened in read/write

-
Image
ORA-16433 is an error returned when a database cannot be opened. This can be a result of multiple conditions including, The inconsistency of the database Physical corruption Loss of dependent files or access issues etc.. More often than not the solution is to recover from available backups, but there can be situations where backups are not available, specially on UAT or Test setups. Although not the ideal scenario, in this type of situation you might want to open the databases even with inconsistency.  In Comes --> _ALLOW_RESETLOGS_CORRUPTION First, if you are in a position to use _ALLOW_RESETLOGS_CORRUPTION=TRUE, that means it has to be a critical moment, and when you come across more ora- errors while you are trying to reopen the databsae, that can be annoying. Note - _ALLOW_RESETLOGS_CORRUPTION=TRUE must only be used after Oracle support confirmation as a last resort. Also make sure to take cold backup before proceeding. Basic steps to be followed to resolve ORA 16433 af...
Read more

Oracle Multitenant - Create new service for PDB using DBMS_SERVICE

-
Image
When an Oracle PDB is created it starts up a default service with the PDB name. For direct connections to    PDB this service can be used. But there are situations where new service name is required in PDB level, common example is after a PDB restoration/clone, in order to enable application connections without changes in connection string. Setting service_names parameter in PDB level is not possible hence it is not an option in multitenant setup. How to create a new PDB service on Oracle 12C Check the current services, here only the default service is running, SQL> show pdbs; CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 3 NFACTORPDB READ WRITE NO SQL> select service_id, name, pdb from dba_Services; SERVICE_ID NAME PDB ---------- ---------------------------------------- ---------- 7 nfactorpdb NFACTORPDB SQL> ...
Read more

Wait for unread message on broadcast channel - Blocking Sessions

-
Image
What is Wait for unread message on broadcast channel wait event? Wait for unread message on broadcast channel is a wait event where source destination communication is involved and the database is waiting for a reply from remote party. Mostly this wait is seen related to data pump export (expdp) or import (impdp) operations. Although categorized in idle wait class "Wait for unread message on broadcast channel" can become the blocking session for some other sessions. Common causes for stuck sessions waiting on this wait event includes, Broken databases links, where remote database is not responding. Abnormally killed remote processes causing the sessions to wait. When a session is waiting on "Wait for unread message on broadcast channel" it can become a blocking session for dependent sessions. Most probably these sessions will be waiting on "library cache pin" or related concurrency wait events. The blocking_session column of (g)v$session view...
Read more