Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> RE: Tuning RMAN backup and recovery

RE: Tuning RMAN backup and recovery

From: Allen, Brandon <Brandon.Allen_at_OneNeck.com>
Date: Fri, 16 Nov 2007 16:01:30 -0700
Message-ID: <04DDF147ED3A0D42B48A48A18D574C45097709FC@NT15.oneneck.corp>


I set out to specifically to test compression performance a few months ago so I changed absolutely nothing other than adding "AS COMPRESSED BACKUPSET" to my BACKUP DATABASE command. I'm backing up to sbt_tape via Netbackup 6.0, but I believe the backups actually go to a disk staging pool rather than directly to a tape drive. I've only tested compression on this one system, so I don't have anything else to compare it to and I'm not sure what would explain why we're seeing different results. It seems to me that the most likely explanation is that my bottleneck is the speed of writes to sbt_tape and those are drastically reduced by the compression so that's where I save the time, whereas you probably are not bottlenecked by the speed of your backup writes to disk so you experience an increase in time due to the extra CPU overhead. Here are my rman configurations:

RMAN> show all;

RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE'; CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO
'%F'; # default

CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 3 BACKUP TYPE TO BACKUPSET; CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' MAXOPENFILES 1 PARMS
'ENV=(NB_ORA_SCHED=User)';

CONFIGURE MAXSETSIZE TO UNLIMITED; # default CONFIGURE ENCRYPTION FOR DATABASE OFF; # default CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default CONFIGURE SNAPSHOT CONTROLFILE NAME TO
'/opt/oracle/product/10.2/db_1/dbs/snapcf_baandev.f'; # default

-----Original Message-----
From: Limin Guo [mailto:lguo.oracle_at_gmail.com]

Brandon and Robert:

Very interesting to know that it actually save time for you to use RMAN compression than not use it.

Do you use different CONFIGURE when using compression? like channels , parallelization, etc.

Privileged/Confidential Information may be contained in this message or attachments hereto. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of this company shall be understood as neither given nor endorsed by it.

--
http://www.freelists.org/webpage/oracle-l
Received on Fri Nov 16 2007 - 17:01:30 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US