Veritas NetBackup™ for Oracle Administrator's Guide
- Introduction
- NetBackup for Oracle QuickStart
- Installing NetBackup for Oracle
- About linking Oracle RMAN with NetBackup for UNIX
- Oracle policy configuration
- Preparing for NetBackup for Oracle configuration
- Instance management for an Oracle Intelligent Policy
- About Oracle Intelligent Policies (OIP)
- About script- or template-based Oracle policies
- About adding backup selections to an Oracle policy
- About configuring the run-time environment
- About creating templates and shell scripts
- About creating RMAN scripts manually
- Performing backups and restores of Oracle
- About NetBackup for Oracle backups
- About NetBackup for Oracle restores
- Using NetBackup for Oracle in a Microsoft Windows cluster environment
- Guided Recovery
- Troubleshooting Guided Recovery
- NetBackup for Oracle with Snapshot Client
- About NetBackup for Oracle with Snapshot Client
- How NetBackup for Oracle with Snapshot Client works
- About configuring Snapshot Client with NetBackup for Oracle
- Restoring NetBackup for Oracle from a snapshot backup
- About configuring NetBackup for Oracle block-level incremental backups on UNIX
- About Snapshot Client effects
- About Oracle support for Replication Director
- Troubleshooting
- Troubleshooting RMAN backup or restore errors
- Appendix A. Real Application Clusters
- Appendix B. Best practices for protecting Oracle RAC with NetBackup
- Appendix C. Deduplication best practices
- Appendix D. Snapshot Client support of SFRAC
- Appendix E. Script-based block-level incremental (BLI) backups without RMAN on UNIX and Linux systems
- Verifying installation requirements for BLI backups without RMAN
- Creating NetBackup policies for script-based BLI backup
- Creating notify scripts for BLI backups
- Performing backups and restores
- About troubleshooting backup or restore errors
- Appendix F. XML Archiver
- NetBackup for Oracle XML export and XML import
- About XML export templates and shell scripts
- Performing an XML export archive
- Restoring an XML export archive
- Troubleshooting XML export or XML import errors
- Appendix G. Register authorized locations
Configuring a stream-based Oracle backup
The following procedure explains how to reconfigure an existing Oracle RMAN specification to achieve a stream-based, optimized, deduplicated Oracle backup.
To configure a stream-based Oracle backup
- On the client computer that hosts the Oracle database, open the RMAN backup script in a text editor, and make the following edits:
Add the FILESPERSET=1 parameter to the part of the RMAN script that specifies how you want to back up the database.
Do not add FILESPERSET=1 to the section of the RMAN script that specifies how to back up the control files or archive logs. Typically, these other data objects are unique to each backup, so there is very little potential gain from optimizing the control file and archive log backups for deduplication.
Example RMAN script after editing:
BACKUP FILESPERSET=1 %BACKUP_TYPE% FORMAT 'bk_u%%u_s%%s_p%%p_t%%t' DATABASE;
The addition of FILESPERSET=1 suppresses Oracle multiplexing of more than one data file into a backup set. When you suppress Oracle multiplexing, Oracle creates the backup set identically each time the backup runs. NetBackup can deduplicate these identical backup sets.
Specify parallel backup streams for the database backup.
Specify appropriate ALLOCATE CHANNEL and RELEASE CHANNEL parameters in the backup script.
For an example that shows an edited backup script, see the following:
- Disable Oracle's optimization and encryption for the duration of the database backup.
By default, Oracle disables optimization and encryption. If optimization and encryption are enabled, run the following RMAN commands from the command line to disable optimization and encryption:
RMAN> CONFIGURE BACKUP OPTIMIZATION OFF; RMAN> CONFIGURE ENCRYPTION FOR DATABASE OFF;
If your site requires encryption, you can specify encryption in the NetBackup for Oracle backup policy.
- Disable Oracle's compression for the duration of the database backup.
By default, Oracle disables compression. If compression is enabled, Oracle compresses unused sections in streams, and the result is unpredictable deduplication rates. If compression is enabled, run the following RMAN command from the command line to disable compression:
RMAN> CONFIGURE DEVICE TYPE SBT_TAPE BACKUP TYPE TO BACKUPSET;
If your site requires compression, you can specify compression in the NetBackup for Oracle backup policy.
- Configure a NetBackup for Oracle policy.
If you want to compress or encrypt the backup, enable compression and encryption in the NetBackup pd.conf file.
Run a full database backup as soon as you can. The policy can perform incremental backups until the full backup can be run.
Note:
Make sure that Oracle optimization, encryption, and compression are disabled for the entirety of the database backup. Make sure to check specifications outside of the RMAN backup script, too.