You’ve invested a great deal of time and effort in building a replicated environment using Oracle Data Guard. But will those replicated servers work when you need them most? In the event of a disaster, is the replicated copy of your critical business data guaranteed to be consistent and complete? Will you be able to meet with business’s RPO and RTO requirements, and ensure a smooth and flawless recovery?
Let’s face it: it is difficult to keep your Oracle Data Guard implementation perfectly aligned with vendor best-practices, and in sync with changes in the other IT layers that Oracle Data Guard interfaces with (such as OS, Storage, Networking and more). Unfortunately, even a small misconfiguration or discrepancy between production and disaster recovery systems can lead to unsuccessful recovery attempts, painful outages and even data loss.
Oracle Data Guard – Configuration Validation and Best-Practice Checks
On a daily basis, AvailabilityGuard verifies that your Oracle Data Guard systems are configured correctly relative to the OS, Storage and other layers. AvailabilityGuard also checks that your Oracle Data Guard configuration follows Oracle’s best practices.
AvailabilityGuard automatically detects errors and potential risks in how Oracle servers configured with Data Guard. AvailabilityGuard captures and displays the relationship between nodes, as well as configuration and startup parameters and state information. The solution automatically detects a wide range of issues and risks that pose a threat to your Oracle Data Guard systems and to the integrity and recoverability of your data.
AvailabilityGuard performs the following:
- Detailed analysis of replication status, state, heartbeat status, unrecoverable changes, …
- Verification of correct settings and configuration:
- Detects incorrect configuration (e.g., Force Logging state, archiver state, etc.)
- Compares configuration of primary and standby servers
- Host configuration (OS version, SP, patch, kernel parameters, network configuration, …)
- Oracle configuration (version, compatibility, …)
- RPO / RTO violation (e.g., by detecting violation of max sequence number drift, detecting log apply AND/OR copy lag drifts)