Chat now with support
Chat with Support

NetVault Backup 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

RMAN-based backups are the only supported backup method for Data Guard environments. RMAN is Data Guard-aware in that it uses its metadata to behave transparently across the primary and physical standby databases in the Data Guard environment.

Performing backups in a Data Guard environment is almost identical to performing backups for a single- or multi-instance database in a non-Data Guard environment. The differences are described in the following topics.

For more information on selecting data for backup, setting backup options, and finalizing and submitting the job, see Performing RMAN backups.

Creating a User Defined Backup Tag

When a Data Guard strategy of backing up from both the Primary and Standby Database Server is implemented with backups from the Primary and Standby Database Servers being interchangeable, you might want to be able to select the source of the backup during a restore. For example, you might want to restore from the Primary Database Server versus the Standby Database Server. The User Defined Backup Tag option lets you assign a tag to the backups that indicates the source of the backup — the Primary Database Server or the Standby Database Server. During the restore, the User Defined Backup Tag is specified in the Restore Options to ensure that only backups from the applicable server are used for the restore.

1
On the NetVault Backup Plugin Options page, click the RMAN Backup Options tab.
2
Select the User Defined Backup Tag option, and enter a tag name.

Performing manual backups of Control File and SPFILE

For Oracle 10.2.x Data Guard environments where the back-up-from-both-Primary-and-Secondary strategy has been deployed or Oracle 11.x Data Guard environments where the Control File and SPFILE backups are the only backups that are performed on the Primary Database Servers, Manual Control File and SPFILE backups are performed.

2
In the selection tree, select the Parameter File and Control File nodes.
3
On the Backup Option tab of the NetVault Backup Plugin Options page, select the following options:
In the Backup Method section, select RMAN.
In the Backup Destination section, select either NetVault Backup Media Manager or Both NetVault Backup Media Manager and Disk (Backup to FRA then Backup FRA to NetVault Backup Media). This step ensures that the Control File and SPFILE are stored on backup media for disaster recovery purposes.
In the Backup Method section, select Full.
4
Use the Schedule, Target Storage, and Advanced Options lists to configure any additional required options.
5
Click Save or Save & Submit, whichever is applicable.

Restoring data

When performing restores in a Data Guard environment where the backup is being restored to the same Database Server where the backup was taken, there is no difference between performing the restore in a Data Guard environment or a non-Data Guard environment. For more information on single-instance environments, see Performing RMAN restores. For more information on multi-instance environments, see Restoring data in a RAC environment.

When performing restores in a Data Guard environment where the backup is restored to an alternate Database Server in the Data Guard environment, the restore is identical to restoring to the same Database Server except for the differences detailed in the following topics.

Related Documents