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
NetBackup for Oracle operation using a script- or template-based policy
The following are prerequisites for performing Oracle backups to a storage unit:
On Windows, access to the NetBackup library
On UNIX, linking with NetBackup
Generating unique file names
NetBackup users or automatic schedules can start database backups by specifying a template or a shell script in the file list of the Oracle policy. The template or the shell script specifies the backup commands that RMAN performs on the client.
On Windows, NetBackup for Oracle includes a library of functions that enable RMAN to use NetBackup. This library is in c:\Windows\system32.
On UNIX, NetBackup for Oracle includes a library of functions that enable RMAN to use NetBackup. You can link to this library.
When you use the RMAN backup command, each resulting backup set contains at least one backup piece (data file, data file copy, control file, or archive log) from the target database. You must give each backup piece a unique name using the format operand. Several substitution variables are available to aid in generating unique names. You can specify the format operand in the backup command. NetBackup considers the backup piece name as the file being backed up, so this name must be unique in the catalog.
For a backup, the following items apply:
The rman command starts the requested operation on the databases.
When the process requires media to store backup data, RMAN starts a user-directed backup by issuing a backup request.
The NetBackup media server connects to NetBackup for Oracle on the client. NetBackup for Oracle on the client sends the database data to the NetBackup media server which saves the data to secondary storage. A restore operation works in essentially the same manner except that RMAN issues a restore request. Then NetBackup retrieves the data from secondary storage and sends it to NetBackup for Oracle on the client.
RMAN supports parallel operations, so a single rman command can start more than one backup, or restore on the NetBackup system.
The status for an RMAN operation is stored in the RMAN catalog or in the database control file. This same status appears in the output of the RMAN command that runs the backup or restore. This status is the only status that a database administrator must check to verify that a backup or restore has been successful.
NetBackup also logs status, but only for its own part of the operation. The database administrator cannot use the NetBackup status to determine whether rman was successful. Errors can occur in rman that do not affect NetBackup and are not recorded in its logs.
More Information