Enterprise-class Disaster Recovery for Oracle SE that prioritizes database integrity, disaster resiliency, recovery speed, and ease of use.
What is a standby database?
Overview of a standby database
Exact copy - A copy of the primary database in a remote location.
Continuously updated - Kept up to date by applying changes (new archive logs) from the primary database.
Warm (operational) - Continuously verified and ready to be failed over to at any time.
Usually remote - Resilience to disasters is improved by having the standby at a remote site.
Enable database continuity - Users and applications are transferred to the standby database after failover and continue to operate.
Why use a standby database for DR?
Instantly available
Guaranteed integrity
Minimal data loss
Include DR testing
Benefits of a standby database
compared to backups
Instantly available - Whereas a standby is instantly available, backups take significant time to restore and hardware may not even be operational for restore causing further delays.
Guaranteed integrity - Although a standby configured with StandbyTM can deliver guaranteed integrity backups are difficult to test, and without testing, there is no way to guarantee your database will have integrity when restored.
Minimal data loss - A standby database can deliver RPOs of less than 10 minutes. Backups on the other hand are taken at a point in time and do not include the latest data.
