Introducing Quest® NetVault® Plug-in for Oracle
Quest NetVault 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 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 '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 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
Prerequisites for CLI-based backups and restores
Verifying that the proper RMAN executable is in use (Linux only)
Various installations of Linux include more than one executable named as rman. Because of this inclusion, you must verify that the correct Oracle RMAN application is started when you issue the rman command at the prompt. This step can be done by making the path to the Oracle RMAN executable ($ORACLE_HOME/bin) as the first search path in the PATH environmental variable.
Ensuring an "SBT_TAPE" channel is established
Plug‑in for Oracle uses an Oracle “SBT_TAPE” channel to conduct backups of an Oracle database. SBT is commonly used to specify a destination for RMAN commands used to back up to tape media. For complete information on establishing this type of channel for use, see Configuring and Allocating Channels for Use in Backups in the Oracle Database Backup and Recovery Advanced User’s Guide.
|
IMPORTANT: Jobs that are generated using the RMAN CLI cannot be re-run using the NetVault WebUI. The RMAN CLI command, that is, the RMAN script, is not sent from the RMAN CLI application back to NetVault. So, if you select Run Now on the Job Status page, the job fails. |
Running the NetVault 'nvpluginaccess' utility
You can run the nvpluginaccess utility, which is available in the “util” directory on the NetVault Server, from the NetVault Server or from a NetVault Client.
If the password for the NetVault default user has been set or a non-default NetVault user is used to run the backup and restore, you must run the nvpluginaccess utility on the NetVault Server or you must configure access for the NetVault Client. You must then obtain the necessary security clearance for the plug-in to perform CLI backups and restores.
nvpluginaccess -client <NetVaultServerName>
|
2 |
|
IMPORTANT: Do not select option 2 or 3; you must enter CLI for the name of the plug-in, which requires selection of option 4. |
|
4 |
Successfully added client '<NetVaultServerName>'.
|
1 |
Initiate a command-line session, and navigate to the “util” directory: |
|
• |
|
• |
where “…” represents the path to the NetVault Server installation directory.
nvpluginaccess -remove -client <clientMachineName>
where <clientMachineName> is the name of the NetVault Client machine on which the plug-in is installed and <userName> is the NetVault user who performs the backups and restores.
|
5 |
Verify that the nvpluginaccess utility has been correctly configured by reviewing the contents of the “hookplugs.cfg” file located in the “config” directory: |
|
• |
|
• |
where “…” represents the path to the NetVault Server installation directory.
|
NOTE: The Password field in the “hookplugs.cfg” file contains an encrypted view of the password. The actual password is not displayed. |