StandbyMP will revolutionize how organizations manage DR enterprise-wide by making the same Gold Standard of DR available to both Oracle SE and MS SQL Server users - all from a single common user interface.
What is a standby database?
A standby database is a shadow copy of a production or primary database on a remote server.
Read on to hear how a standby database can deliver enterprise-class Disaster Recovery through the creation of a continuously verified warm standby database.
The benefits of a standby database for Disaster Recovery
The creation of a warm, continuously updated and verified standby guarantees database continuity no matter what disaster occurs.
A warm offsite standby database, such as one created by Dbvisit StandbyTM, guarantees minimal data loss, fast recovery and resilience against any disaster.
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?
A standby is warm, continually verified, and can be failed over to within just a few minutes in the event of a disaster or failure.
Continuous verification of the standby database, and its warm (operational) state, guarantees database integrity after failover.
Minimal data loss
Continuous updating from the source database ensures only a minimal gap between the primary and standby.
Include DR testing
Perform regular, comprehensive DR testing easily without affecting your primary database.
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.
Standby product page
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.
7-Elevent ensures 24/7 availability of their WMS
StandbyTM enables 24/7 availability of 7-Eleven's WMS system despite threats from tropical storms.
Why integrity must be prioritized for DR
Learn why integrity is the most important requirement of a Disaster Recovery architecture.
Find a local partner
We work with partners around the world to give you the best advice and world-class local support.