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
Configuring an Oracle Intelligent Policy using Replication Director
Use the following procedure to configure an Oracle snapshot policy that uses Replication Director. This procedure uses the Oracle Intelligent Policy, which makes configuration easier.
To create an Oracle Intelligent Policy
- In the web UI, select Protection > Policies.
- Click Add.
- Select the Attributes tab.
- Provide a unique name for the policy.
- The following items are specific to creating an Oracle policy for snapshots with Replication Director:
Policy type
For NetBackup to perform Oracle backups, select Oracle. An Oracle tab appears.
Policy storage
Oracle combines snapshots (proxy) and stream-based backups as part of the same backup. The storage that is indicated here is used for the stream-based part of the Replication Director backup.
Select a storage lifecycle policy that is configured to contain the stream-based (non-snapshot) part of the database backup. The storage must use a storage lifecycle policy that is configured for non-snapshot backups.
Use Replication Director
Enable Use Replication Director to automatically select other options that Replication Director requires:
Perform snapshot backups: Ensures that the policy creates snapshots of the disk array.
Retain snapshots for Instant Recovery or SLP management: Ensures that the policy retains the snapshot after the backup completes.
Snapshot options button
Snapshot Type
Auto (default): The OpenStorage partner uses the best snapshot technology available to that partner to create the snapshot.
Differential: The OpenStorage partner creates a snapshot that is completely dependent on the source. This parameter is based on copy-on-write technology. The device creates a cache object to maintain the original blocks of the snapshot when the blocks are modified.
Plex: The OpenStorage Partner creates a snapshot that is completely independent of the source snapshot. This option is based on mirror-break-off technology. When a mirror device is attached to the source, the contents of the mirror device is exactly the same as the source device. When the relationship is broken between the two, the mirror device is separated from the source. The mirror device acts as a point-in-time copy.
Clone: The OpenStorage Partner creates an independent copy of the volume. The copy process can take some time as the entire copy must be complete. The snapshot that is created is independent of the source.
Maximum Snapshots
Sets the maximum number of snapshots to be retained at one time.
The default setting is one. Choose the number of snapshots that is appropriate for your environment. Note that the maximum number of snapshots on a NetApp volume is 255.
When the maximum is reached, snapshot rotation occurs: The next snapshot causes the oldest to be deleted.
Managed by SLP retention is automatically selected if the Fixed or the Expire after Copy retention is currently selected in the SLP.
- Select the Schedules tab. Create one schedule:
Type of backup: Select Full Backup. The Full Backup is used for both the snapshot (proxy) part of the database and the non-snapshot (stream-based) part of the Oracle database.
The Oracle Intelligent Policy does not support the snapshot of an Archived Redo Log Backup. To take a snapshot of the archived redo logs, use the script-based Oracle policy method.
Note:
Unless creating Block Level Incremental (BLI) backups, always select Full Backup to create snapshots of the Oracle database.
Override policy storage selection: Enable and select the SLP that is configured for snapshot replication. (A snapshot SLP is one in which the first operation is a snapshot operation.) This option must be enabled so that the schedule storage overrides the policy storage with a snapshot SLP.
Retention: The retention for the streamed data is based on the non-snapshot SLP that was indicated as the Policy storage in Step 5.
The non-snapshot SLP specified on the policy storage in Step 5 determines the retention for the streamed data.
The snapshot SLP that is specified as the schedule storage (Override policy storage selection) determines the retention for the snapshot data.
Click Add to save the schedule.
- Select the Instances and databases tab and specify the instances to back up. The policy must include at least one instance. To continue to use the Oracle Intelligent Policy method, select either Protect instances or Protect instance groups.
- Select the Backup selections tab. Select the parts of the database to back up. Note that the selection applies to all listed instances.
The following can be selected for the policies that use Replication Director:
Whole database: Backs up the entire database (default).
Partial database - Tablespaces: Backs up the tablespaces.
Partial database - Datafiles: Backs up the data files.
Fast Recovery Area (FRA): Do not select for a policy that uses Replication Director.
Database backup shares: Do not select for a policy that uses Replication Director.
Whole Database - Datafile Copy Share: Do not select for a policy that uses Replication Director.
Note:
If you back up the partial database, and later want to perform a Point-in-time rollback restore, make sure that you select all of the tablespaces or data files from a partition in the Backup selections.
For copy-back restores, this step is not a requirement.
- Select the Oracle tab to configure Oracle RMAN properties.
- When the policy configuration is complete, click Create.