Comparison between Dbvisit and Data Guard
Dbvisit is a real alternative for Oracle Data Guard without the cost and complexity.
Data Guard is the disaster recovery product offered by Oracle to keep the standby database up to date.
Data Guard only comes with Oracle Enterprise Edition (EE).
Dbvisit has similar features to Data Guard, but is much more cost-effective than upgrading to Oracle Enterprise Edition to enable the use of Data Guard.
Dbvisit works with all editions of Oracle (including Oracle Standard One and Standard Edition) and all versions of Oracle.
|
|
Dbvisit |
Data Guard |
|
Simple to use and configure |
● |
|
|
Uses secure shell for transportation |
● |
|
|
Uses SQL*Net for transportation |
|
● |
|
Uses compression to save bandwidth |
● |
|
|
Automatic continuation when temporary network or database
problems occur |
● |
● |
|
Maintains standby databases |
● |
● |
|
Databases fully supported by Oracle |
● |
● |
|
Multiple Standby Databases |
● |
● |
|
Automatic notification included |
● |
|
|
Built in monitoring |
● |
|
|
Maintains Oracle archive logs on primary and standby
databases |
● |
|
|
Maximum protection |
see note 1) |
● |
|
Maximum performance |
● |
● |
|
Graceful Switchover |
● |
● |
|
Automatic failover and fast-start failover |
see note 2) |
● |
|
Manual failover |
● |
● |
|
Logical Standby |
Dbvisit can be used to
transport the log files to the logical standby database |
● |
|
Broker or agent needed |
|
● |
|
Oracle Enterprise Manager or Grid Control needed |
|
● |
|
Precise timing of updates |
● |
|
|
All platforms (Windows, Linux, Unix) |
● |
● |
|
Automatic stopping and starting of reporting databases |
● |
|
|
Database parameters need changing |
|
● |
|
Oracle RAC support |
● |
● |
|
Oracle ASM and OMF support |
● |
● |
|
Oracle flash recovery support |
● |
● |
|
Works with all versions of Oracle |
● |
|
|
Automatic space management |
● |
● |
|
Cost-effective |
● |
|
Notes:
1) Maximum protection in Data Guard will only commit a transaction on the primary database if it is also available on the standby database.
Maximum protection has performance consequences, it needs a very big network to the standby server and the standby database must be available at all times.
Dbvisit offers maximum performance with a minimum of 60 seconds delay behind the primary database.
For most companies this is acceptable as the price to pay for maximum protection is too high in terms of network bandwidth and performance.
2) Automatic failover in Data Guard means that the standby database will automatically convert itself to a primary database when it
detects that the original primary database is no longer available.
We believe that most companies do not require this feature as there could be many reasons why the primary database is not available, not only because of a disaster.
With Dbvisit the standby database is ready to take over instantly at any time. It only requires one Dbvisit command to activate the standby database and this can be
scripted to run automatically if Automatic failover is required.