Chat now with support

Get Live Help
Complete Registration

Sign In

Request Pricing

Contact Sales

NetVault Plug-in for Oracle 12.3 - User Guide

Table of Contents

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

User Managed backup method Recovery Manager (RMAN) backup method

Reviewing the supported Oracle file types Defining an RMAN backup strategy

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

Flash Recovery Area (FRA) backups

Developing a Recovery Catalog backup strategy Examples of backup sequences Defining a Backup Destination strategy

Oracle Flashback technology NetVault Backup Policy Management

Installing and removing the plug-in

NetVault Backup Server and Client software Database in ARCHIVELOG mode

Prerequisites for RMAN backups

Adding the Oracle user to the local administrator group on Windows Determining the Oracle SID and Home directory in a non-RAC environment

Windows Linux and UNIX

Creating the RMAN repository

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

Determining whether Flashback Database is enabled Setting a retention target

Enabling Block Change Tracking Using DR Series or QoreStor as the storagedevice for Oracle Database 12.x or later on Linux or UNIX

Recommended configuration for a single-instance non-RAC environment Installing or upgrading the plug-in Removing the plug-in

Configuring the plug-in

Configuring a default Target Set for RMAN backups Configuring default settings Adding a database

Editing database information Setting the database password Removing a saved password Removing a database Viewing database details Using RMAN Post-Backup Scripts

Creating an RMAN Post-Backup Script Updating a Post-Backup Script Removing a Post-Backup Script

Language support

Backing up data

Performing User Managed backups

Selecting data for a backup Selecting backup options Finalizing and submitting the job

Performing RMAN backups

Selecting data for a backup Setting backup options Finalizing and submitting the job

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 and recovering data: an overview

Understanding User Managed recovery

Determining which datafiles require recovery Recovering datafiles and archive logs Restoring Control Files

Understanding RMAN recovery

How RMAN backups are selected for use in recovery operations Choosing between Incremental Backups and Redo Logs Choosing the restore source Datafile media recovery Block Media Recovery

Performing User Managed restores

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

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

Using RMAN types of recovery in a non-RAC environment

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 the Stepwise Disaster Recovery process Disaster recovery to same server Retrieving a Control File manually

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

Uses of table-level recovery Table-level requirements and limitations Configuring channels for table-level recovery Performing table-level recovery from the RMAN CLI Performing table-level recovery from the NetVault Backup WebUI

Maintaining the Recovery Catalog

Resynchronizing the Recovery Catalog Using CROSSCHECK to update the RMAN repository

Using the RMAN CLI

CLI-based RMAN backups and restores: an overview Prerequisites for CLI-based backups and restores

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

Using the plug-in with Oracle RAC

Oracle RACs: an overview Recommended additional reading Defining a deployment strategy

RMAN backup process for RAC environment RMAN restore process for RAC environment

Licensing Installing the plug-in in a RAC environment

RAC configuration requirements Installation prerequisites

Enabling Control File Autobackups in a RAC environment

Installing or upgrading the plug-in

Configuring the plug-in

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

Performing backups after node failure

Restoring data in a RAC environment

Recovering a Whole Database to the same RAC environment Restoring SPFILE in a RAC environment Restoring Control Files in a RAC environment Performing disaster recovery in a RAC environment

Prerequisites Performing the disaster recovery

Performing restores after node failure Duplicating a database in a RAC environment

Prerequisites Post-restore procedure

Using the plug-in in a failover cluster environment

Oracle Server Fail Safe Failover Clustering: an overview Installing the plug-in

Installation prerequisites Installing or upgrading the software

Creating a Virtual Client

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

Back up from Primary only Back up from both Primary and Standby Back up from Standby only

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

Installation prerequisites

Optional RMAN configuration settings

Installing or upgrading the plug-in

Backing up data

Creating a User Defined Backup Tag Performing manual backups of Control File and SPFILE

Configuring a restore to an alternate server in a Data Guard environment Restoring data to an alternate server in a Data Guard environment Recovering Whole Database to Primary Database Server

Using the plug-in with Oracle Container Databases (CDBs) and Pluggable Databases (PDBs)

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

Unable to add a database Backup fails Backup job hangs Restore fails Oracle RMAN output is not displayed correctly in binary logs

Backing up data

You can use the WebUI or CLI to back up the CDB and PDBs.

•

Backing up the CDB and PDBs from the WebUI

•

Backing up the CDB and PDBs from the CLI

Backing up the CDB and PDBs from the WebUI

To set up the plug-in for backup and restore of a CDB using the WebUI, use the same process outlined in Adding a database.

Performing backups is almost identical to the process described in Performing RMAN backups. You must use sets — Backup Selection Set, Backup Options Set, Schedule Set, Target Set, and Advanced Options Set — to create a backup job. Note the following differences:

•

To include all the datafiles of the CDB root container, the seed container, and all the datafiles of the plugged-in PDBs, select the Database node or the All Tablespaces node of a CDB.

•

To include only individual tablespaces or individual datafiles of a CDB, select the specific tablespaces or datafiles of the root container. Note that this option excludes the tablespaces or datafiles of PDBs from the backup.

•

You cannot add a PDB to the WebUI; PDBs are protected as a part of the CDB to which they are plugged. If applicable, you can use the CLI commands described in Backing up the CDB and PDBs from the CLI to back up only the contents of a PDB.

Backing up the CDB and PDBs from the CLI

When you back up the CDB and PDBs from the CLI, you have the option of backing up everything or backing up only the PDB that is targeted by a specific CDB or a specific PDB.

To back up the CDB and all PDBs

rman catalog rcat/rcat@rcatalog

RMAN> connect target /

connected to target database: SALESDB (DBID=3924627550)

using target database control file instead of recovery catalog

RMAN> run { allocate channel ch1 type sbt;

2> backup database include current controlfile

3> plus archivelog; }

The CLI displays the applicable output regarding the status of the backup.

To back up a PDB that is connected to a CDB as a target

RMAN> run { allocate channel ch1 type sbt;

2> backup pluggable database sales_region300_pdb; }

The CLI displays the applicable output regarding the status of the backup.

To back up a PDB that is connected to a PDB as a target

RMAN> connect target pdbadmin/pdbadmin@sales_region200_pdb

connected to target database: SALESDB:SALES_REGION200_PDB (DBID=3022227374)

using target database control file instead of recovery catalog

RMAN> run { allocate channel ch1 type sbt;

2> backup database; }

The CLI displays the applicable output regarding the status of the backup.

Restoring data

You can use the WebUI or CLI to back up the CDB and PDBs.

•

Restoring the CDB and PDBs from the WebUI

•

Restoring the CDB and PDBs from the CLI

Restoring the CDB and PDBs from the WebUI

If you use the WebUI to create and run a backup of a CDB, including its PDBs, you can restore the whole CDB and individual tablespaces or datafiles using the steps provided in Performing RMAN restores. For a more granular restore, you can use the CLI as described in Restoring the CDB and PDBs from the CLI.

Restoring the CDB and PDBs from the CLI

When you restore the CDB and PDBs from the CLI, you have the option of restoring everything or restoring only the PDB that is targeted by a specific CDB.

To restore the CDB

CDBs are restored in a manner similar to restoring non-CDBs. The following example shows the restore of a tablespace from the CDB.

rman catalog rcat/rcat@rcatalog

RMAN> connect target /

connected to target database: SALESDB (DBID=3924627550, not open)

using target database control file instead of recovery catalog

RMAN> run { allocate channel ch1 type sbt;

2> restore tablespace USERS; }

allocated channel: ch1

channel ch1: SID=22 device type=SBT_TAPE

channel ch1: Quest(R) NetVault(R) Backup Plug-in for Oracle. v.12.2.0.9

Starting restore at 28-NOV-18

channel ch1: starting datafile backup set restore

channel ch1: specifying datafile(s) to restore from backup set

channel ch1: restoring datafile 00007 to
Q:\APP\ORACLEUSER\ORADATA\SALESDB\USERS01.DBF

channel ch1: reading from backup piece 0rtjacic_1_1

channel ch1: piece handle=0rtjacic_1_1 tag=TAG20181128T002027

channel ch1: restored backup piece 1

channel ch1: restore complete, elapsed time: 00:00:15

Finished restore at 28-NOV-18

released channel: ch1

To restore a PDB that is connected to a CDB as a target

RMAN> run { allocate channel ch1 type sbt;

2> restore pluggable database sales_region300_pdb;

3> recover pluggable database sales_region300_pdb; }

The CLI displays the applicable output regarding the status of the restore.

sqlplus / as sysdba

SQL> alter pluggable database sales_region300_pdb close;

Pluggable database altered.

rman catalog rcat/rcat@rcatalog

RMAN> connect target /

connected to target database: SALESDB (DBID=3924627550)

using target database control file instead of recovery catalog

RMAN> run { allocate channel ch1 type sbt;

2> set until scn=1860018;

3> restore pluggable database sales_region300_pdb;

4> recover pluggable database sales_region300_pdb auxiliary
destination='C:\oracle_recovery';

5> alter pluggable database sales_region300_pdb open resetlogs; }

The CLI displays the applicable output regarding the status of the restore.

RMAN> connect target pdbadmin/pdbadmin@sales_region300_pdb

connected to target database: SALESDB:SALES_REGION300_PDB
(DBID=1471149548, not open)

RMAN> run { allocate channel ch1 type sbt;

2> restore database;

3> recover database; }

The CLI displays the applicable output regarding the status of the restore.

Troubleshooting

•

Unable to add a database

•

•

Backup job hangs

•

•

Oracle RMAN output is not displayed correctly in binary logs

Unable to add a database

When attempting to add a database to the plug-in, the following error appears:

Invalid Credentials.

Unable to configure plugin to connect to this database.

Connection to the database cannot be established due to LDAP failure.

Disable LDAP, and try adding the database again.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating

© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center