Chat now with support
Chat with Support

NetVault Plug-in for Oracle 12.2 - 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

Optional RMAN configuration settings

The following settings are optional in a Data Guard environment.

Retention Policy

RMAN’s Retention Policy specifies a persistent, ongoing policy for backup sets and copies those sets that RMAN marks as obsolete, that is, not needed and eligible for deletion. As time passes, RMAN marks backup sets and copies as obsolete according to the criteria specified in the retention policy. RMAN automatically deletes obsolete backup sets and copies in the FRA when space is needed. RMAN does not automatically delete obsolete files outside the FRA, such as on NetVault Backup backup media.

Primary database configuration
1
After making sure that the Recovery Catalog database is open, connect RMAN to the primary target database and to the Recovery Catalog database.
For example, issue the following commands to connect to the catalog database:
> rman TARGET / CATALOG rman/<password>@<connect_identifier for catalog>
2
Configure the retention policy:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF <n> DAYS
Archive Log Deletion Policy

RMAN’s Archive Log Deletion Policy specifies that archived redo logs are eligible for deletion if both of the following conditions are met:

•
The archived redo logs have been applied to the required standby databases.
•
The logs are not needed by the BACKED UP … TIMES TO DEVICE TYPE deletion policy. If the BACKED UP policy is not set, this condition is always met.
Optional settings
•
When backups of archived redo log files are taken on a standby database:
•
Primary database configuration:
a
After making sure that the Recovery Catalog database is open, connect RMAN to the primary target database and to the Recovery Catalog database.
For example, issue the following commands to connect to the catalog database:
> rman TARGET / CATALOG rman/<password>@<connect_identifier
for catalog>
b
Configure the deletion policy:
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY
•
Configuration for standby database where backups are performed:
a
After making sure that the Recovery Catalog database is open, connect RMAN to the standby target database performing backups and to the Recovery Catalog database.
b
Configure the deletion policy:
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE
•
Configuration for standby database where backups are not performed:
a
After making sure that the Recovery Catalog database is open, connect RMAN to the standby target database where backups will not be performed and to the Recovery Catalog database.
b
Configure the deletion policy:
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY
•
When backups of archived redo log files are taken on the primary database:
•
Primary database configuration:
a
After making sure that the Recovery Catalog database is open, connect RMAN to the primary target database performing backups and to the Recovery Catalog database.
b
Configure the deletion policy
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE
•
Standby database configuration:
a
After making sure that the Recovery Catalog database is open, connect RMAN to the standby target database and to the Recovery Catalog database.
b
Configure the deletion policy:
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY
Backup optimization

RMAN Backup Optimization prevents RMAN from backing up a file to a device type if the identical file is already backed up on the backup media. However, RMAN does not signal an error if backup optimization causes all files to be skipped during a backup.

Configuration for standby database performing backups
1
After making sure that the Recovery Catalog database is open, connect RMAN to the standby target database performing backups and to the Recovery Catalog database.
For example, issue the following commands to connect to the catalog database:
> rman TARGET / CATALOG rman/<password>@<connect_identifier for catalog>
2
Configure the backup optimization:
CONFIGURE BACKUP OPTIMIZATION ON
 
* 
IMPORTANT: In a switchover or failover where the databases change roles, the corresponding CONFIGURE commands must be re-run on the new primary and standby databases.

Installing or upgrading the plug-in

In a Data Guard environment, you must install the plug-in on the Primary Database Server. Optionally, you can also install the plug-in on one or more Physical Standby Database Servers. For more information on the supported Data Guard deployments, see Deployment.

1
Install the NetVault Backup Client software.
Install the NetVault Backup Client software on each Oracle Database Server where the plug-in will be installed.
2
Add the NetVault Backup Clients to the NetVault Backup Server.
From the WebUI on the NetVault Backup Server, open the Manage Clients page. Add the NetVault Backup Clients installed on the primary and standby databases to the NetVault Backup Clients list.
3
Install Plug‑in for Oracle.
With the NetVault Backup Client software installed on each required system of the Data Guard environment, install the plug-in on each system as well. The process is identical to installing the plug-in for a non-Data Guard single or multi-instance database environment.

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.

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

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.
This option creates a tag name for the backup set. Use only characters that are allowed in filenames on the target file system. For example, ASM does not support the use of hyphens (-) in filenames that it uses internally, so you cannot use a hyphen in the tag name, such as, weekly-incremental, if you are storing backups in ASM disk groups.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating