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
Configuring channels for table-level recovery
You can also use the following command to add additional channels, if applicable:
RMAN> CONFIGURE CHANNEL <channelNumber> DEVICE TYPE sbt
For more information on configuring channels, see your Oracle documentation.
Performing table-level recovery from the RMAN CLI
|
• |
Table-level recovery requires the use of the “until” clause to define the state that you want to recover to. |
The following example recovers three tables of an Oracle user, sales, to a specific SCN using a fully automated auxiliary instance for which the required files are populated in a Linux or UNIX directory, /oracle/nvbu_pitr_auxiliary_destination, which you created before running recovery.
Similar example except that it uses a log sequence:
Using the remap table option, the following example recovers two of the three selected tables to a new table with a different name. The third table is recovered with the same name as the original.
Recovers a table from a common user:
By default, RMAN imports the recovered tables or table partitions into the target database. Before import, the tables are stored in an export dump file. You can use the NOTABLEIMPORT option to prevent RMAN from importing the recovered tables or table partitions. If you use this option, the tables are recovered to the specified point, and the export dump file is created, but the dump file is not imported into the target database. At that point, you can analyze the tables using the auxiliary instance, or manually import the dump file into the target database instance using the Oracle Data Pump Import utility.
Performing table-level recovery from the NetVault WebUI
In addition to the steps outlined in Performing RMAN restores, the following options apply specifically to table-level recovery.
|
1 |
In the Recovery Type section on the Perform Recovery tab, select the Perform Table Level Point in Time Recovery option. |
|
2 |
|
• |
If you select the System Change Number Based option, the plug-in instructs RMAN to use the “until scn” clause during table recovery. For example: until scn 5555638 |
|
• |
If you select the Log Sequence Based option, the plug-in instructs RMAN to use the “until sequence <number> thread <number>” clause during table recovery. For example: until sequence 38 thread 1 |
|
• |
If you select the Time Based option, the plug-in instructs RMAN to use the “until time” clause during table recovery. For example: until time "to_date('2013/11/23 06:59:00', 'yyyy/mm/dd hh24:mi:ss')" |
|
3 |
In the Auxiliary Destination field, specify a directory (full path) that the auxiliary instances use to store all the files needed, including copies of the controlfile, archive logs, and datafiles. |
|
4 |
In the Recover table field, enter a comma-separated list of tables that you want to include in the recovery table as part of a table-level recovery. |
Use the oracle_user_name.table_name construct. Oracle 12c includes common users and local users, and the naming convention used for the local users is similar to the Oracle database user names in earlier versions of Oracle.
For containers where common users are in place, the Oracle database supplies the SYS and SYSTEM common users. The name of user-created common users must begin with C## or c#. For more information, see the Oracle 12c Multitenant Architecture documentation.
|
IMPORTANT: When listing a table from a common user, use double quotation marks. While SQL*Plus accepts queries on the tables using a string that includes C## or c# and excludes the double quotation marks, RMAN does not. |
Example 1: The following lists three tables for the sales user.
Example 2: The following example lists two tables for the common C##SALES user.
Use of the preceding example is equivalent to the recover table "C##SALES"."NORTHSALES", "C##SALES"."SOUTHSALES" clause.
|
5 |
In the Remap table field, enter a comma-separated list of tables that you want to rename, if applicable, as a part of a table-level recovery. |
This option lets you recover the table and analyze it for appropriateness to determine whether to overwrite the original table. You do not need to provide a mapping for every table listed in the Recover table field; you only need to list the mapping for those tables that you want to rename temporarily.
Use of the preceding example is equivalent to the remap table "C##SALES"."NORTHSALES":"NORTHSALES_RECOVERED" clause.