サポートと今すぐチャット
サポートとのチャット

NetVault Plug-in for Oracle 11.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 Troubleshooting

Multi-instance RAC to multi-instance RAC Data Guard deployment

In a multi-instance to multi-instance Data Guard deployment, the plug-in is installed in the Primary RAC Database environment and at least one of the Standby Database Servers.

Figure 10. Multi-instance RAC to multi-instance RAC Data Guard deployment

For more information on deploying the plug-in in a multi-instance RAC environment, see Defining a deployment strategy.

Installing the plug-in in a Data Guard environment

Before completing any additional or different steps that are outlined in the following topics, review the information provided in earlier topics, such as Installing and removing the plug-in and Configuring the plug-in.

•
Installation prerequisites
•
Installing or upgrading the plug-in

Installation prerequisites

The following prerequisites must be met before you can install Plug‑in for Oracle in a Data Guard environment:

•
Oracle® Data Guard environment in place: You must have a properly configured Data Guard environment. The version of Oracle is listed as a Supported Data Guard environment in the Quest NetVault Backup Compatibility Guide.
•
Oracle RAC environment in place: For Data Guard environments that include multi-instance Primary or Standby Database Servers, meet the Oracle RAC-required configuration that is specified in RAC configuration requirements.
•
Separate NetVault Backup Server machine: The machine that is to serve as the NetVault Backup Server must be properly configured. This machine must exist outside the Data Guard environment, but have network connectivity to the nodes and hosts within the Data Guard environment.
•
Separate Recovery Catalog Server: Quest recommends that you store the RMAN repository in a Recovery Catalog database on a server outside the Data Guard environment. Only the primary database can be registered with the Recovery Catalog. For more information, see Creating the RMAN repository.
•
Control File Autobackups are enabled: Automatic backups of the Control File and SPFILE must be enabled on the databases that meet the following criteria:
•
Back up from Primary Only strategy: Enable Autobackups of the Control File and SPFILE on the Primary Database Server.
•
Back up from both Primary and Standby strategy:
•
Oracle 10.2.x: Disable Autobackups of the Control File and SPFILE on both the Primary and all the Standby Database Servers where backups are performed. Manual Control File and SPFILE backups are performed on the Primary Database Server.
•
Oracle 11.x: Enable Autobackups of the Control File and SPFILE on all the database servers where backups are performed. For example, if Incremental Level 0 Backups are taken from Standby Database Server while Incremental Level 1 Backups are taken from the Primary Database Server, enable Autobackups on both the Primary and Standby Database Server.
•
Back up from Standby Only strategy: Enable Autobackups of the Control File and SPFILE on the Standby Database Servers where backups are being performed.
For more information, see Enabling Control File Autobackups.
•
Flash Recovery Area recommended: Enabling FRA is recommended for Data Guard environments. For more information, see Configuring the Flash Recovery Area in the Oracle Database Backup and Recovery User’s Guide.
•
Flashback Database recommended: Enabling the Flashback Database is recommended on Data Guard Standby Database Servers. For more information, see Enabling Flashback Database and the Using Flashback Database After a Role Transition section in Oracle Data Guard Concepts and Administration.
•
Additional prerequisites: In addition to the preceding Data Guard-specific requirements, meet the non-Data Guard-specific requirements that are specified in Prerequisites.

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.
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択