Databases Reference
In-Depth Information
4.
Now that the archived log destination is set, you want to back up the archived log to an
ASM storage location, more specifically to a disk group RMANBAK. Here's how:
RMAN> backup archivelog sequence 94 format '+RMANBAK/%U.rmb';
Starting backup at 18-AUG-12
using channel ORA_DISK_1
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=94 RECID=85 STAMP=791648751
channel ORA_DISK_1: starting piece 1 at 18-AUG-12
channel ORA_DISK_1: finished piece 1 at 18-AUG-12
piece handle=+RMANBAK/0vniv6pv_1_1.rmb tag=TAG20120818T143126 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 18-AUG-12
You have now completed the placement of archived logs on an ASM disk group.
How It Works
When you point archived logs into a specific directory in ASM, the archived logs are not actually created there.
This is due to the property of Oracle Managed Files (OMF) in ASM volume manager (described in Recipe 24-1).
You can confirm that by checking for the actual files and aliases inside the disk group DG1:
ASMCMD> cd +dg1
ASMCMD> ls -l
Type Redund Striped Time Sys Name
Y ASM/
Y IDB1/
N rman/
N rmanbackup/
Note that the archivelog file created earlier is nowhere to be seen in the directory +DG1. Where did it go? To find
out, check the Oracle Managed File structure. The OMF file is created inside IDB1 (the name of the database).
ASMCMD> cd IDB1
ASMCMD> ls -ls
Type Redund Striped Time Sys Block_Size Blocks Bytes Space Name
Y ARCHIVELOG/
Y BACKUPSET/
Y TEMPFILE/
ASMCMD> cd ARCHIVELOG
ASMCMD> ls
2012_08_18/
ASMCMD> ls -ls
Type Redund Striped Time Sys Block_Size Blocks Bytes Space Name
Y 2012_08_18/
