There are three different types of data guards
1. Maximum Availability
2. Maximum Performance
3. Maximum Protection
1. Maximum Availability
2. Maximum Performance
3. Maximum Protection
Maximum Availability
This protection
mode provides the highest level of data protection that is possible
without compromising the availability of a primary database.
Transactions do not commit until all redo data needed to recover those
transactions has been written to the online redo log (not all - that's the catch) and to at least one
synchronized standby database.
If the primary database cannot write its
redo stream to at least one synchronized standby database, it operates
as if it were in maximum performance mode to preserve primary database
availability until it is again able to write its redo stream to a
synchronized standby database.
This mode ensures that no data loss will occur if the primary
database fails, but only if a second fault does not prevent a complete
set of redo data from being sent from the primary database to at least
one standby database.
This protection
mode provides the highest level of data protection that is possible
without affecting the performance of a primary database.
This is
accomplished by allowing transactions to commit as soon as all redo data
generated by those transactions has been written to the online log.
Redo data is also written to one or more standby databases, but this is
done asynchronously with respect to transaction commitment, so primary
database performance is unaffected by delays in writing redo data to the
standby database(s).
This protection mode offers slightly less data protection than
maximum availability mode and has minimal impact on primary database
performance.
This is the default protection mode.
To
provide this level of protection, the redo data needed to recover a
transaction must be written to both the online redo log and to at least
one synchronized standby database before the transaction commits.
To
ensure that data loss cannot occur, the primary database will shut down,
rather than continue processing transactions, if it cannot write its
redo stream to at least one synchronized standby database.
Because this data protection mode prioritizes data protection over
primary database availability, Oracle recommends that a minimum of two
standby databases be used to protect a primary database that runs in
maximum protection mode to prevent a single standby database failure
from causing the primary database to shut down.
Comments