ASM BACKUP PROCEDURES
ASM_Backups_v2.doc 7/22/2013
Document Control
DOCUMENT INFORMATION
Title ASM procedures for backup configurations on ASM
based systems
Author Anchit Khar
File Name ASM_Backups_v2.doc
Path
Created on 11-July-2013
Last Edited on 12-July-2013
Reviewed by
Document Number
REVISION HISTORY
Version Issue Authoris
Change Details Approved by
No. Date ed by
1 11-July-2013 Initial draft
2 12-July-2013 Included recommendations
from Klaus-uwe
TARGET READERS
1. Project Manager, APMM Project
2. System Owner, APMM Project
3. Team Members , APMM Project
ASM_Backups_v2.doc 7/22/2013
Introduction
The purpose of this document is to document the procedures and steps involved in
configuration of the full, incremental and archivelog backups on ASM based systems.
This document will be of assistance to the SAP team for any future backup
configurations, and also for troubleshooting of issues with the backups.
Details
The backups of ASM based systems must be performed using RMAN. Thus, the SAP
specific brtools is used to trigger the backup, which in turn executes rman backup by
referring to a utl file, and a remote TSM server for backing up the files.
For all the ASM based systems (except VLDBs), a shared TSM server is used to backup
the files. The configuration steps for the backups of the ASM based systems, except
VLDBs is further described in the document.
For VLDBs, dedicated TSM servers, and a split mirror technique is followed in addition
to the brtools-rman process. The split mirror backup technique ensures that the
database is not kept in ‘begin backup’ mode for long durations of time, thereby making
the backup process fairly independent of the productive operations.
The detailed document for the split mirror backup configuration process for VLDBs is
described in the following document.
<Split mirror backup configuration v1.1.pdf>
Please always refer to the latest version of this document available with the team.
For non-VLDB FACT systems, the following types of rman backups are of relevance :
1. Full backup (Level-0).
2. Incremental backup (Level-1)
3. Archivelog backups.
Full and Incremental Backups for ASM based systems:
1. Copy the backup specific files from old to new Oracle Home directory (OCFS2 to ACFS)
# cp /oracle/<SID>/112_64/dbs/*.bki /oracleacfs/<SID>/112_64/dbs/
# cp /oracle/<SID>/112_64/dbs/*.sap /oracleacfs/<SID>/112_64/dbs/
# cp /oracle/<SID>/112_64/dbs/*.utl /oracleacfs/<SID>/112_64/dbs/
# cp /oracle/<SID>/112_64/dbs/agent.lic /oracleacfs/<SID>/112_64/dbs/
ASM_Backups_v2.doc 7/22/2013
2. Take a backup/copy of the copied files [/oracleacfs/<SID>/112_64/dbs/*] before modifying
them.
3. Check / make the following entries in init<SID>1.sap and init<SID>2.sap file:
Change all /oracle values to /oracleacfs
Parameter backup_dev_type = rman_util
Add the below parameters
o asm_root_dir = ASM
o asm_ora_sid = (<SID>1:+ASM1, <SID>2:+ASM2)
o asm_ora_home = (<SID>1:/oracle/CRS03/112_64,
<SID>2:/oracle/CRS03/112_64)
Parameter util_par_file = /oracleacfs/<SID>/112_64/dbs/init<SID>.utl
Parameter rman_parms =
"ENV=(XINT_PROFILE=/oracleacfs/<SID>/112_64/dbs/init<SID>.utl,PROLE_PORT=57323
,&BR_INFO)"
4. Check / make the following changes in init<SID>.utl file (path of .utl file which is in use, is
mentioned in init<SID>.sap file):
Change all /oracle values to /oracleacfs
Parameter SERVER should be entered as the correct TSM server
Parameter CONFIG_FILE for init<SID>.bki file to be changed from /oracle to /oracleacfs
5. Create directory /oracleacfs/<SID>/sapprof
6. Copy all the files from dbs into sapprof folder
# cp /oracleacfs/<SID>/112_64/dbs/* /oracleacfs/<SID>/sapprof/
7. Create a new pfile using the following command in sqlplus:
(Note : Below query should be executed from /oracleacfs/<SID>/sapprof directory only)
> create pfile=/oracleacfs/<SID>/sapprof/init<SID>1.ora from spfile;
8. Create a snapshot controlfile in RMAN:
rman> connect target /
rman> configure snapshot controlfile name to '+<DGNAME>/<SID>/snapcf<SID>.dbf';
(DGNAME is the name of the diskgroup where the rman snapshot controlfile needs to be
saved)
ASM_Backups_v2.doc 7/22/2013
9. Create a link to sapbackup directory in ORACLE_HOME. From path $ORACLE_HOME
# /oracleacfs/<SID>/112_64> ln –s /oracleacfs/<SID>/sapbackup sapbackup
10. Check if the below link-file libobk.so is available at $ORACLE_HOME/lib/
If it is not present, create the link as:
ln -s /opt/tivoli/tsm/tdp_r3/ora64/libtdp_r364.so $ORACLE_HOME/lib/libobk.so
11. Create sapreorg directory within /oracleacfs/<SID> and provide 775 permissions to it.
# mkdir /oracleacfs/<SID>/sapreorg
# chmod 775 /oracleacfs/<SID>/sapreorg
12. Check whether the environment variables for user <sid>adm are pointing to /oracleacfs
Example:
scrbdefrmr207:mddadm #> env |grep -i ora
PATH=/oracleacfs/MDD/112_64/bin:/krb5/bin/64:/usr/local/bin:/bin:/usr/bin:/usr/X
11R6/bin:/usr/sap/MDD/SYS/exe/uc/linuxx86_64:/usr/sap/MDD/SYS/exe/run:/sapmn
t/MDD/home:.
LD_LIBRARY_PATH=/usr/sap/MDD/SYS/exe/run:/usr/sap/MDD/SYS/exe/uc/linuxx86_6
4:/oracle/client/11x_64/instantclient
dbms_type=ORA
dbs_ora_tnsname=MDD1
dbs_ora_schema=SAPSR3
ORACLE_SID=MDD1
ORACLE_BASE=/oracleacfs
TNS_ADMIN=/sapmnt/MDD/profile/oracle
ORACLE_HOME=/oracleacfs/MDD/112_64
SAPDATA_HOME=/oracleacfs/MDD
13. Trigger full backup using the below command :
brbackup -u / -c -p /oracleacfs/<SID>/112_64/dbs/init<SID>1.sap –r
/oracleacfs/<SID>/112_64/dbs/init<SID>.utl -m full -t online
14. Repeat steps 3, 4 and 6 to make similar changes in init<SID>1.sap_rman_incr file (and
relevant utl file mentioned in it) for triggering incremental backups.
ASM_Backups_v2.doc 7/22/2013
15. Trigger incremental (level 1) backup using the below command:
brbackup -u / -c -p /oracle/<SID>/112_64/dbs/init<SID>1.sap_rman_incr -r
/oracle/<SID>/112_64/dbs/init<SID>1.utl -m incr -t online
Archive log backups for ASM based systems:
1. Create saparch directory within /oracleacfs/<SID> and provide 775 permissions to it.
# mkdir /oracleacfs/<SID>/saparch
# chmod 775 /oracleacfs/<SID>/saparch
2. Repeat steps 3, 4 and 6 (from above) to make similar changes in init<SID>1.sap.archive file
(and relevant utl file mentioned in it) for triggering offline archive log backups.
16. Trigger archivelog backup backup using the below brarchive command:
brarchive -u / -r /oracleacfs/<SID>/112_64/dbs/init<SID>.utl.archive -c -sd –n <count>
ASM_Backups_v2.doc 7/22/2013
