Scribd
Upload
7 views2 pages

DATAGUARD

Dataguard Implementation

Uploaded by

madhan kumar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
7 views2 pages

DATAGUARD

Dataguard Implementation

Uploaded by

madhan kumar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

DATAGUARD

A Dataguard configuration consists of one primary database and one or more standby database.
The standby databases will be always in sync with primary database. If primary production database
is unavailable due to planned or unplanned outage, then we can switch the production to standby
database, making the application less affected by the outage. Oracle Data Guard ensures high
availability, data protection, and disaster recovery for enterprise data. Dataguard configuration
option available with Enterprise Edition.

Types of Standby Database:

Physical Standby

Logical Standby

Snapshot Standby

Physical Standby
 Physical Standby is the exact block-for-block copy of the primary database.
 Physical standby database synchronized with the primary database through the application
of redo data received from the primary database.
 It can be used concurrently for data protection and reporting.
 Physical standby database will be mounted stage while recovery is processed.
 It can be opened as read-only mode

Active vs Normal Standby.

 Active standby enables read-only access to a physical standby database for queries,
sorting, reporting, Web-based access, and so on, while continuously applying changes
received from the primary database (Active Dataguard License Required).
 Normal Standby enables you to switch to the Standby Database when your primary
database is down due to some outage or natural calamities. In normal Data guard, you can
still open the standby database in read-only mode but changes not applied while in read-
only mode.
Logical Standby:
The logical standby database is kept synchronized with the primary database through
SQL APPLY, which transforms the data in the redo received from the primary database into SQL
statements and then executes the SQL statements on the standby database. So it contains same
logical information as that of production, but physical structure of data can be different.

Snapshot Standby:
A snapshot standby database is a fully update-able standby database that is created by
converting a physical standby database into a snapshot standby database. During this setup though it
will receive logs from primary, But those redo won’t be applied to snapshot standby. Redo data
received from the primary database is applied when a snapshot standby database is converted back
into a physical standby database, after discarding all local updates to the snapshot standby database.

It provides an exact replica of a production database for development and testing purposes,
while maintaining data protection at all times.

Oracle Data Guard Broker


In a data guard configuration, we know that there are minimum two servers that take part: one is
primary and another one is standby.

A data guard broker logically groups these primary and standby databases into a Broker
Configuration. This allows Data Guard broker to manage and monitor (primary and standby) as one
single unit.
Benefits of Data Guard Broker

One of the biggest benefits of Data Guard broker is that is centralizes the configuration,
management and monitoring of Oracle Data Guard configurations.

Some of the operations that Data Guard broker simplifies are

 Create Data Guard configuration between primary and standby databases


 Add additional standby databases to existing Data Guard configuration
 Mange Data Guard protection modes
 Start switchover / failover by just one single command
 Monitor redo apply, gaps and data guard performance
 Perform all above operations locally or remotely !

You might also like