Compress a RMAN Backup
If you are taking a backup of a big database,
you’ll notice that the RMAN backup files are bigger (almost same size as the
database itself).
So, for most situation, you should always take
compressed backup of the database.
The following example take a compressed backup of
the tablespace PRD01.
RMAN> BACKUP AS COMPRESSED BACKUPSET TAG 'PRD01_TBLS_BK_ONLY'
TABLESPACE PRD01;
When you view the backup files from the file system
level, you will not see any .gz (or .zip, or .bz2) to indicate that the RMAN
has taken a compressed backup. The file naming convention will still follow the
same as a non-compressed backup.
$ ls -l /backup/rman/
total 58352
-rw-r----- 1 oracle dba 14585856 Aug 8 11:48 ctl_c-758818131-20130808-00
-rw-r----- 1 oracle dba 14585856 Aug 8 11:54 ctl_c-758818131-20130808-01
-rw-r----- 1 oracle dba 14585856 Aug 8 11:56 ctl_c-758818131-20130808-02
-rw-r----- 1 oracle dba 14585856 Aug 8 11:59 ctl_c-758818131-20130808-03
-rw-r----- 1 oracle dba 327680 Aug
8 11:48 full_4dogpd0u_4237_1
-rw-r----- 1 oracle dba 327680 Aug
8 11:54 full_4fogpdb3_4239_1
-rw-r----- 1 oracle dba 327680 Aug
8 11:55 full_devdb_bk_4hogpdef_4241_1
-rw-r----- 1 oracle dba 127680 Aug
8 11:59 full_devdb_bk_4jogpdl0_4243_1
Note: The way to tell whether RMAN has taken a
compressed backup or not, it by looking at the size, and by looking at the
output of the RMAN “list” command which is shown in one of the section below.
For all
RMAN Backup Command visit Below Link:
Ref.: http://www.thegeekstuff.com
Comments
Post a Comment