Enterprise-class Disaster Recovery for Oracle SE that prioritizes database integrity, disaster resiliency, recovery speed, and ease of use.
Why use physical replication for Disaster Recovery on Oracle SE?
Why use physical replication for Disaster Recovery on Oracle Databases?
This white paper explains the concepts, considerations and principles behind replication and provides details of various replication methods available.
One of these methods is physical replication that delivers unparalleled database integrity. The paper outlines a range of solutions that can be used to deliver physical replication for Oracle databases before explaining in detail the operation of one such solution, StandbyTM by Dbvisit.
What's in it?
An introduction to key business continuity metrics including RPO and RTO.
Physical vs logical replication
An comparison of two distinct approaches to achieving a standby database: (1) Physical replication, and (2) Logical replication.
Physical replication methods
A look into home-grown scripting and third-party tools for the creation of a physical standby database.
Standby product page
Standby is gold standard Disaster Recovery for Oracle SE. Start your journey here.
NEC software achieves 5min RPO with Standby
NEC software implemented StandbyTM for database continuity of a large payment system. StandbyTM delivers guaranteed successful failover and a RPO of 5 minutes across all disasters.
Why is integrity required for DR?
Learn why you must be certain that at any time, no matter what, your database will be available.
Why use Physical Replication for DR?
An explanation of physical replication and how it delivers an exact replica of the original data at the binary level. This helps to guarantee data integrity.
What is a Standby database?
Learn how a standby database can deliver low data loss and fast recovery times.