Introducing Quest® NetVault® Backup Plug-in for Oracle
Quest NetVault Backup Plug-in for Oracle: at a glance
Key benefits
Feature summary
Target audience
Recommended additional reading
Defining a backup strategy
Defining a strategy: overview
Reviewing the available backup methods
Reviewing the supported Oracle file types
Defining an RMAN backup strategy
Installing and removing the plug-in
Choosing the location for the RMAN repository
Reviewing the RMAN Tablespace and Datafile backup types
Reviewing the Control File backup types
Reviewing the other backup types
Developing a Recovery Catalog backup strategy
Examples of backup sequences
Defining a Backup Destination strategy
Oracle Flashback technology
Prerequisites
Prerequisites for RMAN backups
Configuring the plug-in
Adding the Oracle user to the local administrator group on Windows
Determining the Oracle SID and Home directory in a non-RAC environment
Creating the RMAN repository
Recommended configuration for a single-instance non-RAC environment
Installing or upgrading the plug-in
Removing the plug-in
Configuring the Recovery Catalog database
Creating the Recovery Catalog owner
Creating the Recovery Catalog
Registering the target database
Enabling Control File Autobackups
Enabling Flashback Database
Enabling Block Change Tracking
Configuring a default Target Set for RMAN backups
Configuring default settings
Adding a database
Backing up data
Editing database information
Setting the database password
Removing a saved password
Removing a database
Viewing database details
Using RMAN Post-Backup Scripts
Language support
Performing User Managed backups
Performing RMAN backups
Using Plug-in for FileSystem to back up Oracle ACFS
Using the Oracle® Flashback Database
Flashback Database: an overview
Viewing Flashback Database status
Flashback Database options
Flashback Database restrictions
Restoring data with the plug-in and Flashback Database
Restoring data
Restoring and recovering data: an overview
Maintaining the Recovery Catalog
Using the RMAN CLI
Understanding User Managed recovery
Performing User Managed restores
Determining which datafiles require recovery
Recovering datafiles and archive logs
Restoring Control Files
Understanding RMAN recovery
Preparing the database for recovery
Selecting data for a restore
Finalizing and submitting the job
Recovering the database
Opening the database for use
Using advanced User Managed restore procedures
Renaming or relocating Control File, Datafile, or individual Archived Log files
Renaming or relocating the Archive Log Directory
Performing RMAN restores
Selecting data for a restore
Setting restore options
Using RMAN types of recovery in a non-RAC environment
Viewing the contents of backup pieces
Setting the Pre-Restore and general Restore Options
Setting recovery options
Setting Block Media Recovery options
Setting Post Recovery options
Setting Destination Details
Setting the Recovery Catalog details
Setting the Clone Database options
Setting Generate RMAN Script options
Finalizing and submitting the job
Restoring the Control File from an Autobackup
Recovering individual datafiles and tablespaces to the same server
Recovering Whole Database to same server
Performing disaster recovery with RMAN
Using advanced procedures with RMAN restores
Renaming or relocating files
Duplicating a database in a non-RAC environment
Restoring a Duplicate Database to the same server
Restoring a Duplicate Database to an alternate server with the same directory structure
Restoring a Duplicate Database to an alternate server with an alternate directory structure
Performing table-level recovery
CLI-based RMAN backups and restores: an overview
Prerequisites for CLI-based backups and restores
Using the Plug-in with Oracle® RAC
Verifying that the proper RMAN executable is in use (Linux only)
Ensuring an "SBT_TAPE" channel is established
Running the NetVault Backup 'nvpluginaccess' utility
Performing CLI-based backups
Example of a basic CLI backup
More parameters: the "format" clause
More parameters: the "send" and "PARMS" clauses
Querying the NetVault Backup media name
Performing CLI-based restores
Oracle RACs: an overview
Recommended additional reading
Defining a deployment strategy
Licensing
Installing the plug-in in a RAC environment
Configuring the plug-in
Using the Plug-in in a failover cluster environment
Configuring default attributes
Determining the local Oracle SID and Home directory in a RAC environment
Adding a database to the plug-in
Backing up data
Restoring data in a RAC environment
Oracle Server Fail Safe Failover Clustering: an overview
Installing the plug-in
Licensing the plug-in
Configuring the plug-in and adding a database
Backing up data
Restoring data
Using the plug-in with Oracle® Data Guard
Oracle® Data Guard: an overview
Defining a deployment strategy
Deployment
Troubleshooting
Single-instance to single-instance Data Guard deployment
Multi-instance RAC to single-instance Data Guard deployment
Multi-instance RAC to multi-instance RAC Data Guard deployment
Installing the plug-in in a Data Guard environment
Backing up data
Restoring data
RAC configuration requirements
Plug‑in for Oracle’s support for multi-instance RAC databases is limited to environments that meet the following criteria:
|
• |
The version of Oracle® and the platform are listed as a supported RAC environment in Quest NetVault Backup Compatibility Guide. |
Figure 6 and Figure 7 provide an overview of supported single and multiple RAC database deployments.
Figure 6. Supported single-database deployments
Figure 7. Supported multiple-database deployments
Installation prerequisites
The following prerequisites must be met before you can install Plug‑in for Oracle in a RAC environment:
|
• |
Oracle® RAC environment in place: You must have a properly configured Oracle RAC environment that matches the configuration as specified in RAC configuration requirements. |
|
• |
Separate NetVault Backup Server machine: The machine that is to serve as the NetVault Backup Server must be properly configured. This machine must exist outside the Oracle RAC environment, but have network connectivity to the nodes and hosts within the RAC environment. |
|
• |
Separate Recovery Catalog Server: Quest recommends that you store the RMAN repository in a Recovery Catalog database on a server outside the Oracle RAC environment. For more information, see Creating the RMAN repository. |
|
• |
Additional prerequisites: In addition to the preceding RAC-specific requirements, meet the requirements that are specified in Prerequisites. |
|
• |
Oracle 11g Release 2 and later: If you are using Oracle 11g Release 2 or later, ensure that the snapshot Control File is shared by all nodes in the RAC database. The snapshot Control File must be saved in a shared location, such as in one ASM instance or on a shared drive. The location of the snapshot Control File is managed by the snapshot Control File name RMAN parameter. In Oracle 11g Release 2, by default, this parameter refers to a persistent file in the local file system on each of the RAC nodes. If this configuration applies to your environment, ensure that you change the parameter to point to a shared location. Otherwise, RMAN backups that include the Control File might fail with an “ORA-00245: control file backup operation failed” message. |
Enabling Control File Autobackups in a RAC environment
Control File Autobackups are required in a RAC environment. For more information, see Reviewing the Control File backup types. For more information on single-instance RAC databases, see Enabling Control File Autobackups.
Installing or upgrading the plug-in
Installing Plug‑in for Oracle in a multi-instance database environment is almost identical to installing it in a single-instance database environment. The plug-in is installed on one of the nodes that hosts one of the instances for the RAC-enabled database. All RMAN-based backups and restores are performed from this single installation of the plug-in. Installing the plug-in is a two-step process:
|
1 |
Install the NetVault Backup Client software. |
During installation of the NetVault Backup Client software on the selected node of the RAC environment, a name that represents the entire RAC environment should be specified as the NetVault Machine Name versus the machine name of the selected node. For example, if the machine name for the node where the NetVault Backup Client software is being installed is called RAC_NODE_1, RAC_NODE_1 should not be specified as the NetVault Machine Name; it should be a generic or virtual name that represents the entire RAC environment such as PROD_RAC.
|
2 |