RMAN Backup can create compressed backups. To enable binary compression for oracle database files AS COMPRESSED BACKUPSET clause of BACKUP command is used. No extra uncompression steps are required during recovery.

Binary compression creates some performance overhead during backup and restore operations. Binary compression consumes CPU resources, so compressed backups should not be scheduled when CPU usage is already high.
Following are the some consideration when you may need RMAN Backup Compression.

  1. Disk-based backup destination is limited.
  2. Backups to device over a network when reduced network bandwidth is more important than CPU usage.
  3. You are using CD or DVD, where reducing backup sizes saves on media costs and archival storage.

If you are backing up to tape and your tape device performs its own compression, then you should not use both RMAN backup set compression and the media manager vendor's compression. In most instances you will get better results using the media manager's compression.

You can either Configure RMAN Backup Compression as the default for backupsets or explicitly specify compression in an RMAN Backup Command. Following example creates full database backup as compressed backup sets.

BACKUP
AS COMPRESSED BACKUPSET
DATABASE;

In this example RMAN Backup the entire database and archived logs to the configured default backup destination (disk or tape) as compressed backup sets.

BACKUP
AS COMPRESSED BACKUPSET
DATABASE PLUS ARCHIVELOG;

 

Go to top
JSN Boot template designed by JoomlaShine.com