지금 지원 담당자와 채팅
지원 담당자와 채팅

NetVault Plug-in for Oracle 12.3 - User Guide

Introducing Quest® NetVault® Backup Plug-in  for Oracle Defining a backup strategy Installing and removing the plug-in Configuring the plug-in Backing up data Using the Oracle Flashback Database Restoring data
Restoring and recovering data: an overview Performing User Managed restores Using advanced User Managed restore procedures Performing RMAN restores Using RMAN types of recovery in a non-RAC environment Using advanced procedures with RMAN restores
Maintaining the Recovery Catalog Using the RMAN CLI Using the plug-in with Oracle RAC Using the plug-in in a failover cluster environment Using the plug-in with Oracle Data Guard Using the plug-in with Oracle Container Databases (CDBs) and Pluggable Databases (PDBs) Troubleshooting

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 nocatalog
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
RMAN>
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.
SQL> exit
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 nocatalog
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 fails
•
Backup job hangs
•
Restore fails
•
Oracle RMAN output is not displayed correctly in binary logs

Unable to add a database

Problem

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.
Possible Cause

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

Resolution

Disable LDAP, and try adding the database again.

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택