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
Create an Oracle policy
Use the following procedure to create a policy to protect Oracle databases.
To create a policy
- In the web UI, on the left expand Protection > Policies.
- Click Add.
- Type a unique name for the new policy.
- For the Policy type, select Oracle.
- The default values are the best values for most configurations. However, you may need to customize the parameter settings on one or more of the tabs.
The dialog contains the following tabs:
Attributes tab. Default values are automatically selected on the Attributes tab. More information is available about these attributes.
Schedules tab. More information is available about this tab.
Instances and databases tab. On this page, select the instances and instance groups that you want backed up for the policy. An Oracle Intelligent Policy (OIP) must include either the Protect Instances and Databases or the Protect instance groups option. More information is available about this tab.
Backup selections tab. More information is available about the attributes on this tab.
Oracle tab. More information is available about the attributes on this tab.
See Oracle tab.
- To protect the newly discovered instances, you may have to create the instance group first, then set up a policy for the default instance group.
See Automatically register new instances with an instance group.
- (Optional) Create
bpstart_notify
andbpend_notify
scripts for an Oracle Intelligent Policy (OIP).For an OIP, the scripts must include the
.policyname
or.policyname.schedule
suffix or the script does not run at the start or end of the policy. An OIP ignores the genericbpstart_notify
andbpend_notify
scripts and they do not work for a non-OIP.Note:
For RAC OIP backups the
bpstart_notify
and thebpend_notify
scripts must reside on all Oracle RAC nodes.The generic bpstart_notify or bpend_notify scripts reside on the server and the location varies by platform:
UNIX:
/usr/openv/netbackup/bin/goodies/
Windows:
Install_path/NetBackup/bin/goodies/
The renamed script must be copied from the server and placed in the NetBackup
bin
directory on the client:UNIX:
/usr/openv/netbackup/bin/
Windows:
Install_path\NetBackup\bin\
Examples of renamed scripts:
UNIX:
/usr/openv/netbackup/bin/bpstart_notify.oip_instance1
or/usr/openv/netbackup/bin/bpend_notify.oip_instance2.full
Windows:
install_path\NetBackup\bin\bpstart_notify.oip_instance1.bat
orinstall_path\NetBackup\bin\bpend_notify.oip_instance2.full.bat
For more information about the bpstart_notify and bpend_notify scripts, refer to the NetBackup Administrator's Guide, Volume II.