Chat now with support
Chat with Support

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

Installing or upgrading the software

Installation of the plug-in for a clustered environment is different than the traditional installation of this plug-in. This process is completed through the creation of a Virtual Client on the NetVault Backup Server. A Virtual Client is a group of nodes within the cluster that are seen by the NetVault Backup Server as a single client that is created to back up a single clustered service.

Creating a Virtual Client

As noted earlier, the Virtual Client creation process is not plug-in-specific, and you can find complete details in the Quest NetVault Backup Administrator’s Guide. However, consider the following points during the Virtual Client creation process:

Assign a name to the Virtual Client: Quest recommends that you use the virtual-network name assigned to the Oracle database as the NetVault Backup Virtual Client name; you can also use a name that is easily associated with the Oracle database or cluster environment. This configuration makes it easier to recognize the Oracle database for which the NetVault Backup Virtual Client was created.
Only include relevant cluster nodes in the Virtual Client: The hosts that are to be included in the creation of a Virtual Client should only be those nodes within the cluster that are relevant to the Oracle Database Server that is to be backed up and restored.

After the creation of the Virtual Client, the plug-in is transferred to all designated cluster nodes and installed locally. You can use the installed Plug‑in for Oracle by using the Virtual Client to back up and restore shared data; you can only perform backups and restores of data established as shared within the cluster.

Licensing the plug-in

Another difference between using Plug‑in for Oracle in a clustered environment is how it is licensed for use. The plug-in supports backup and restore of shared data only. Hence, for an Oracle Database Server Failover Cluster environment, only a single license would be needed — a clustered application license for the Virtual Client.

For information on the licensing process, including how to obtain the proper license keys, see the Quest NetVault Backup Installation Guide.

Configuring the plug-in and adding a database

Configuring Plug‑in for Oracle for a clustered failover environment is almost identical to configuring the plug-in for a single-instance, non-clustered environment. Adding a database involves the following exceptions:

Oracle SID: Enter the local SID to the active node in the cluster for the target Oracle database. The local SID is the Oracle instance name on the local node for the target database.
Control File Autobackup enabled: Quest recommends that you select this option.
PFILE usage: If the local instances in the cluster nodes of the targeted Oracle database use PFILE instead of SPFILE, you might want to clear the Use RMAN Commands to Backup SPFILE option on the RMAN Details tab. Access this tab through the Add Database or Edit Database options, and enter the applicable information in the Parameter File(s) Path box on the Oracle Instance Details tab.

For more information, see Configuring the plug-in and Adding a database.

IMPORTANT: If a failover to a different node occurs, use the Add Database option to add the Oracle database information to the plug-in on the active node — the one to which the cluster failed over. You only need to enter this information once; in subsequent failovers, the plug-in automatically retrieves the information.
Related Documents