NetBackup™ for Oracle Administrator's Guide
- Introduction
- NetBackup for Oracle QuickStart
- Installing NetBackup for Oracle
- About linking Oracle RMAN with NetBackup for UNIX
- Configuring RBAC for the Oracle administrator
- Managing Oracle instances and databases
- Managing Oracle credentials
- Configuring Oracle policies
- Preparing for NetBackup for Oracle configuration
- About Oracle Intelligent Policies (OIP)
- About script-based Oracle policies
- Managing Oracle RAC
- Performing backups and restores of Oracle
- About NetBackup for Oracle backups
- Managing expired backup images
- About NetBackup for Oracle restores
- Using NetBackup for Oracle in a Windows Server Failover Cluster (WSFC)
- Oracle cloning
- NetBackup Copilot for Oracle
- Configuring an OIP using universal shares (Oracle Copilot)
- Oracle Copilot with instant access
- Prerequisites when you configure an instant access Oracle database
- 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
- NetBackup Dedupe Direct for Oracle
- Using NetBackup Dedupe Direct for Oracle plug-in
- Other Oracle configuration
- Troubleshooting
- Troubleshooting RMAN backup or restore errors
- Appendix A. Deduplication best practices
- Appendix B. Snapshot Client support of SFRAC
- Appendix C. 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 D. XML Archiver
- NetBackup for Oracle XML export and XML import
- About XML export shell scripts
- Performing an XML export archive
- Restoring an XML export archive
- Troubleshooting XML export or XML import errors
- Appendix E. Register authorized locations
Writing to a directory versus writing to a storage unit
One important aspect of the parameter file is the DIRECTORY parameter. If you specify the DIRECTORY parameter, the bporaexp (bporaexp64 on some platforms) command writes the backup files to the operating system directory you specify. NetBackup does not write the files to a storage unit.
For example, assume that the archive test1 contains one table, USER1. If the directory parameter is specified, NetBackup creates certain files when you run the bporaexp command.
Windows:
DIRECTORY=\db\netbackup\xml
UNIX:
DIRECTORY=/db/netbackup/xml
Table: NetBackup files for example table USER1 shows the files NetBackup creates when you run the command.
Table: NetBackup files for example table USER1
File | Content |
---|---|
Windows: UNIX: | Master XML schema for table USER1 |
Windows: UNIX: | Table schema for table USER1 |
Windows: UNIX: | XML document for table USER1 |
If the DIRECTORY parameter is not specified, NetBackup writes the backup images to a storage unit. A NetBackup backup set is created and cataloged under the name:
Windows:
\Oracle\XMLArchive
UNIX:
/Oracle/XMLArchive
All NetBackup for Oracle bporaexp backups are cataloged using this convention.
Alternatively, if the parameter file does not contain the DIRECTORY parameter, NetBackup creates and catalogs the following files:
Windows:
\Oracle\XMLArchive\test1\test1.xsd \Oracle\XMLArchive\test1\USER1\TEST1.xsd \Oracle\XMLArchive\test1\USER1\TEST1.xml
UNIX:
/Oracle/XMLArchive/test1/test1.xsd /Oracle/XMLArchive/test1/USER1/TEST1.xsd /Oracle/XMLArchive/test1/USER1/TEST1.xml
In production, do not use the DIRECTORY parameter in the bporaexp parameter file. When you write to a storage unit, NetBackup offers the features that include searching and cataloging with the NetBackup catalog and automatic handling of output that exceeds file system limits. With the DIRECTORY parameter, file system limits, such as a 2 GB maximum, can cause an error.
To run bporaexp on the client, run the following command:
bporaexp [username/password] parfile = filename | help=y
More Information