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
NetVault Backup Policy Management
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
Using DR Series or QoreStor as the storagedevice for Oracle Database 12.x or later on Linux or UNIX
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
Using the CROSSCHECK and CATALOG commands with backups
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
Using the plug-in with Oracle Container Databases (CDBs) and Pluggable Databases (PDBs)
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
Oracle PDBs: an overview
Enabling connection to a PDB
Querying CDB, PDB, and non-CDB databases
Restrictions for backing up and restoring a PDB
Backing up data
Restoring data
Troubleshooting
Setting Block Media Recovery options
Use the options on the Block Media Recovery tab to specify that you want to perform Block Media Recovery. When Block Media Recovery is performed, the following should be noted:
|
• |
Objects selected on the Create Selection Set page are ignored. |
|
• |
Mount Database Before Restore and Shutdown Abort Database First options on the Restore Options tab are honored. |
|
• |
Options selected on the Post Recovery tab are honored. |
The Block Media Recovery tab contains the following options:
|
• |
Perform Block Media Recovery: Select this option to perform Block Media Recovery and recover only the corrupted blocks versus recovering the entire datafile. |
|
• |
Recover All Corrupted Blocks: Select this option to recover all the corrupted blocks that are reported in V$DATABASE_BLOCK_CORRUPTION. |
|
• |
Specify Corrupted Blocks to Recover: When you only want to recover a certain subset of the corrupted blocks, select this option. In the corresponding text box, enter the datafile number and block number of each of the corrupted blocks that you want to recover. Enter one datafile-block entry per line in the following format: |
In this example, <num> represents the datafile and block number to recover.
Setting Post Recovery options
When performing recovery using the Whole Database, All Tablespace, or Disaster Recovery options, the database is in a MOUNT state during the restore and recovery process. You must return the database to the OPEN state after completion. The plug-in provides the flexibility of opening the database automatically after the recovery process during the restore.
The Post Recovery tab includes the following options:
|
• |
Open Database after Recovery: Select this option to open the database automatically and make it available for normal use after the recovery process is completed during the restore. Selecting this option makes the following options available: |
|
• |
Read Write: Opens the database in read/write mode, which lets you generate redo logs. This option is the default if you are opening a primary database. |
|
• |
Read Write and Reset Logs: Opens the database in read/write mode and resets the current log sequence number to 1. It also archives any un-Archived Log files, including the current log, and discards any redo information that was not applied during recovery so that it is never applied. This option must be selected in the following situations: |
|
• |
After a previous OPEN RESETLOGS operation did not complete. |
|
• |
After a FLASHBACK DATABASE operation. |
|
• |
Read Only: Select this option to restrict users to read-only transactions, which prevents them from generating redo logs. This option is the default setting when you open a physical standby database, so that the physical standby database is available for queries even while archive logs are being copied from the primary database site. Oracle has the following restrictions on opening a database with the Read Only option: |
|
• |
You cannot open a database in Read Only mode if it is opened in Read Write mode by a different instance. |
|
• |
You cannot open a database in Read Only mode if it requires recovery. |
|
• |
You cannot take tablespaces offline while the database is open in Read Only mode. However, you can take datafiles offline and online, and you can recover offline datafiles and tablespaces while the database is open in Read Only mode. |
Setting Destination Details
If the SYSDBA user name or password or the Oracle SID for the database has changed since the time of backup, set the following options for the restore job on the Destination Details tab:
|
• |
Target Service: This option is required only if the current SID for the Oracle DBID has been changed since the backup was taken. |
|
• |
Oracle SYSDBA User Name: Specify the new SYSDBA user name if changed. |
|
• |
Oracle SYSDBA Password: Specify the password associated with the name specified in the preceding field. |
|
IMPORTANT: The Destination Details requires that the DBID of the backed-up or source database match the DBID of the destination database. When the goal of the restore is to create a duplicate of the source database to a database with a different DBID, using a Duplicate Database backup is required. For more information, see Duplicate Database backup. |
Setting the Recovery Catalog details
While the Recovery Catalog information is provided for backups on the Configure or Add, or Edit, Oracle Database dialog box, set the Recovery Catalog configuration for a particular restore job by configuring the Recovery Catalog information on the Recovery Catalog tab.
|
• |
Use Catalog: Select this option to use the RMAN repository in the Recovery Catalog and store information about this restore operation in a Recovery Catalog. Clear Use Catalog when performing a test recovery. |
|
• |
Catalog Instance Name: Enter the Oracle Instance name, which might differ from the Oracle Net Service name, for the Recovery Catalog database. This instance name must be defined in the “tnsnames.ora” file on the Oracle Database Server so that the plug-in can connect to the Recovery Catalog database. If the Recovery Catalog was used during the backup, the Instance Name field defaults to the Oracle Instance name used during the backup job. |
|
• |
Catalog Owner: Specify the user that was specified as the owner of the Recovery Catalog and was granted the RECOVERY_CATALOG_OWNER role. |
|
• |
Catalog Password: Provide the password associated with the Catalog Owner name specified in the preceding field. |