Please enter search query.
Search <book_title>...
Veritas NetBackup™ for Oracle Administrator's Guide
Last Published:
2018-09-17
Product(s):
NetBackup (8.1.2)
- 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
Example Oracle BLI backup policy
The following example shows attributes and schedules for an Oracle BLI backup policy. Use the NetBackup Administration Console to add policies.
Policy Name: oracle_backup1 Policy Type: Standard Active: yes Block level incremental: yes Job Priority: 0 Max Jobs/Policy: 1 Residence: oracle_tapes Volume Pool: NetBackup Keyword: ORA1 Client List: Sun4 Solaris2.6 mars HP9000-800 HP-UX11.00 mars Backup Selections List: /oradata/oradata1 Schedule: full Type: Full Backup Frequency: 1 week Retention Level: 3 (one month) Daily Windows: Sunday 18:00:00 --> Monday 06:00:00 Monday 18:00:00 --> Tuesday 06:00:00 Tuesday 18:00:00 --> Wednesday 06:00:00 Wednesday 18:00:00 --> Thursday 06:00:00 Thursday 18:00:00 --> Friday 06:00:00 Friday 18:00:00 --> Saturday 06:00:00 Saturday 18:00:00 --> Sunday 06:00:00 Schedule: incr Type: Differential Incremental Backup Frequency: 1 day Retention Level: 3 (one month) Daily Windows: Sunday 18:00:00 --> Monday 06:00:00 Monday 18:00:00 --> Tuesday 06:00:00 Tuesday 18:00:00 --> Wednesday 06:00:00 Wednesday 18:00:00 --> Thursday 06:00:00 Thursday 18:00:00 --> Friday 06:00:00 Friday 18:00:00 --> Saturday 06:00:00 Saturday 18:00:00 --> Sunday 06:00:00 Schedule: userbkup Type: User Backup Retention Level: 3 (one month) Daily Windows: Sunday 00:00:00 --> Sunday 24:00:00 Monday 00:00:00 --> Monday 24:00:00 Tuesday 00:00:00 --> Tuesday 24:00:00 Wednesday 00:00:00 --> Wednesday 24:00:00 Thursday 00:00:00 --> Thursday 24:00:00 Friday 00:00:00 --> Friday 24:00:00 Saturday 00:00:00 --> Saturday 24:00:00
In this example, the oracle_backup1 policy backs up all the files in /oradata/oradata1. The policy specifies a weekly full backup, a daily differential incremental backup, and a user-directed backup schedule. The archive logs and the control file are backed up using the user-directed schedule at the completion of the full or incremental backup.