Find key product information on Dbvisit StandbyTM through the following links. Be sure to trial StandbyTM for free, in either the cloud or on-premise.
What is physical replication?
Next, why use physical replication to create a standby database?
Data integrity - The standby database is an exact replica of the primary database as changes are applied at the lowest (binary) level within the database.
Everything is covered - There are no restrictions on the type of data that can be replicated. All changes including indexes, pointers, and tables are transferred. This ensures consistency.
Fast & efficient - Only archive logs are transferred to update the standby reducing bandwidth and latency requirements. Comparatively, block-level replication requires datafiles, redo logs and archive changes to be copied to the standby.
.png)
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 - Where as 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.
