Dbvisit Standby vs Data Guard
| Functionality | Dbvisit Standby | Data Guard |
|---|---|---|
| Works with Microsoft Windows, UNIX and Linux, 32bit and 64bit |
![]() |
![]() |
| Low cost solution |
![]() |
![]() |
| Easy to use and manage |
![]() |
![]() |
| Supports Oracle versions 8i to 11g, both 32 bit and 64 bit |
![]() |
![]() |
| Supports Oracle RAC, flash recovery area, OMF and ASM file systems |
![]() |
![]() |
| Automatic Graceful switchover (role reversal) |
![]() |
![]() |
| Provides switch over for planned maintenance and upgrades |
![]() |
![]() |
| Time-delayed updating of standby database |
![]() |
![]() |
| Automatic continuation without intervention of DBA |
![]() |
![]() |
| Automatic notification alerting via email |
![]() |
![]() |
| Automated management and monitoring of Oracle logs on both primary and standby server |
![]() |
![]() |
| Simple failover to activate standby database in case of disaster |
![]() |
![]() |
| Maximum performance mode |
![]() |
![]() |
| Maximum protection for zero data loss -i |
![]() |
![]() |
| Secure shell used for log transportation |
![]() |
![]() |
| Encryption and compression as standard |
![]() |
![]() |
| Automatic failover and fast-start failover -ii |
![]() |
![]() |
| Multiple standby databases each with their own schedule |
![]() |
![]() |
| Precise timing of update (snapshot capability) |
![]() |
![]() |
| Creation of Standby database |
![]() |
![]() |
| Easy creation of primary database for failback purposes |
![]() |
![]() |
| Automated Read Only window Option Scheduling |
![]() |
![]() |
| Additional memory resources used from host server |
![]() |
![]() |
| Additional storage resources used from host server |
![]() |
![]() |
| Protection from database corruption being replicated |
![]() |
![]() |
| Automatically replicates all changes including new tables and columns |
![]() |
![]() |
Notes:
i - Maximum protection mode in Data Guard which offers 0% data loss comes with a high price and high performance costs which are unacceptable for most companies.
ii - We believe the decision to failover to the standby database should not be automatic, as it could just be a temporary glitch. However, the failover is a simple command in Dbvisit Standby and can be automated if this feature is required.
Dbvisit Standby does not use SQL*Net, it uses secure shell (ssh) mechanism even on Windows. Dbvisit Standby for Windows includes ssh software from Bitvise to securely transfer the updates to the standby server.
This makes Dbvisit Standby on all platforms very secure and servers are not compromised by using non secure ports and non encrypted transport mechanisms.




