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.
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 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 Server machine: The machine that is to serve as the NetVault 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. |
• |
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. |
The following settings are optional in a Data Guard environment.
• |
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. |
• |
Configuration for standby database where backups are not performed: |
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. |
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.
3 |
© ALL RIGHTS RESERVED. Feedback Conditions d’utilisation Confidentialité Cookie Preference Center