Disaster recovery made easy!

• New Feature: Resynchronise standby database after NOLOGGING operations or archive log loss. Previously the standby database had to be rebuilt, but with this new feature only the changed blocks or deltas are transferred, saving time and network bandwidth. Fully automated through the web-based interface or command line.
• New Feature: Run your standby database in the Cloud

• Fully automated robust standby database solution
• Creates the standby database
• Supports RAC, ASM and OMF
• Graceful Switchover (role reversal) for planned outages

• Manage and run multiple standby databases from the same source database
• Elegant fully featured web-based interface plus command line
• Simple failover

Simplicity

With both a graphical web-based, user interface and access to the command line Dbvisit Standby is very simple to install, configure and administer. It automatically creates the standby database and standby database environment and includes all the tools and utilities to effectively and easily manage it.

• Simple step by step guided installation process
• Optional templating function for easy recreation of standby databases
• Customizable creation of the standby database
• Resynchronise standby database after NOLOGGING operations or archive log loss

• Option to script administrative tasks and run in batch mode
• Threshold setting and automatic notification with conflict resolution
• Automatic management of log files on the primary and secondary database

Fully Featured

Out of the box Dbvisit Standby matches Data Guard on features such as failover, graceful switchover, RAC, ASM and OMF and includes a number of advanced features such as compression, monitoring and encryption for archive log transportation.

• Configurable standby database lag to mitigate human error
• Run reports, backups and business analysis off the standby database
• Create multiple standby databases from the same primary
• Apply different configurations to primary and standby databases
• Automatic archive log management on primary and standby databases
• Transportable Media support option for creation of large standby databases
• Compression enabled by default - save 70% on network bandwidth

Robust

In the event of a failure Dbvisit Standby ensures you can switch applications over to the standby database in a matter of minutes, saving you the inconvenience of dealing with restoration delays, undue pressure on other systems and hardware unavailability. Every database change is replicated to the standby database and security is at the core of Dbvisit Standby’s design.

• Automatic continuation, without human intervention, freeing up DBA resources 
• No database triggers needed to avoid operational conflicts and performance issues
• Provides advanced options such as compression, monitoring and encryption

• Save up to 80% on Oracle Licensing - affordable with long term savings
• Robust, Trusted, Proven
• Maximize your standby database Return On Investment (ROI) with additional uses enabled

Save on time and money

Maintaining your database and protecting it against failures is an essential part of the DBAs job. Without the right tools it can prove to be the most unproductive part of it too. Because Dbvisit Standby gives you control over your database environment it makes managing it less of a chore and frees up more time to focus on other activities. Additionally, the savings on license costs and maintenance fees are significant (up to 80%), as there is no need to upgrade to Enterprise Edition to utilise Data Guard and Dbvisit Standby requires you to license only the primary server.

Increase Return On Investment (ROI) with a single product

Dbvisit Standby is also used in the following scenarios to provide even further value for Standard Edition users:

• Remote or local standby databases for comprehensive disaster recovery and instant protection for failover sites
• Shadow environment to provide risk free investigation and resolution of database bugs or inconsistencies
• Batch processing environment capturing snapshots of 'point in time' transactions for rollback purposes when errors occur
• As a read-only reporting database to run large reports without impacting the primary database and server
• To form part of a backup strategy speeding up the Mean Time To Recovery (MTTR) when restoring databases from tape
• Providing a recent 'point in time' view of the primary database data, in read-only view mode, for access by a remote office
• Bundled as the disaster recovery component of a software product offering

Peace of mind

Dbvisit Standby is backed by DbvisitProtect, providing support services designed to ensure your software continues to operate flawlessly with all Oracle updates and upgrades and new versions of your operating system.

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.

Graceful Switchover

Dbvisit Standby uses Graceful Switchover to seamlessly switch the primary database server back to the original configuration it was in prior to an outage.

Often called 'role reversal' because users are re-directed to the standby database, this process is often used to keep a working database available to all users during disaster recovery testing of the primary database server and planned outages for server maintenance or upgrades. It is done in a matter of minutes* with no dataloss.

Graceful Switchover is never used during a disaster when the primary database is no longer available. In the event of a disaster the Failover process signals the users that the standby database is now their primary database.

Archive Log Management

Unlike Oracle database files, Oracle archive logs need to be monitored and managed constantly to ensure optimal database operation. If poorly managed they use up all the available disk space, cause the entire database to freeze and stop any updates or insert operations from happening.

Easy to configure, the Dbvisit Standby Archive Log Management Module (AMM) fully automates the management and monitoring of Oracle archive logs on both the primary and standby servers.

• Alerts through email when Oracle archive logs have reached a set threshold of available disk space
• Deletes Oracle archives logs after a set number of days
• Deletes Oracle archive logs after available disk space has been used up

• Ensures Oracle archive logs have been sent to standby database before removing any logs
• Integrates with backup software to ensure logs have been backed up before removing

Reporting Database

With Dbvisit Standby it is possible to create a separate standby database that acts as reporting database or open the standby database for reporting purposes during the day. This offloads the processing overhead associated with report generation or schedules it to occur during off-peak times. All updates are applied automatically once the database is switched from reporting to standby mode with Dbvisit Standby used to manage scheduling.

Multiple Standby Databases

Dbvisit Standby enables multiple local-site or remote-site standby databases to be kept up to date from a single primary database. Each runs to its own schedule, can be used for different purposes and automatically synchronises with the primary database.

Real Application Cluster (RAC)

Dbvisit Standby can be used together with Oracle RAC to provide a scalable and high availability (HA) disaster recovery (DR) solution for your Oracle Standard Edition database. 

In the case of a RAC configuration, if one node fails Dbvisit Standby on another RAC node can take over the log shipment from the failed node automatically. 

As easy to set up and manage with Dbvisit Standby as a single instance database is, the RAC database does not require a restart or any of its Oracle parameters changed.

RAC primary and RAC standby database.

• All primary nodes need to send the archive logs to a shared location on the RAC standby cluster
• Dbvisit Standby only needs to be scheduled on one standby instance to apply the archives from all threads to the standby database

RAC primary and single instance Oracle standby database.

• All primary nodes need to send the archive logs to the single standby node
• Dbvisit Standby will apply the archives from all threads to the single instance standby database

DOWNLOAD DBVISIT STANDBY >

About this Software

• This software is fully functional, commercial enterprise software and includes a 30-day evaluation license
• A commercial license key is needed to activate the software to change it from an evaluation version to a fully licensed version
• No re-install or upgrade is required to activate the software

To upgrade your version of Dbvisit Standby

• Existing license keys are automatically applied to the latest software
• Download the software for an upgrade to Dbvisit Standby

Please note

• Free support is available during the evaluation period
• Upgrade to Dbvisit Standby 6.0 is free if you have current Dbvisit Standby support
• Existing 5.1, 5.2 and 5.3 license keys are NOT valid for 6.0. Please contact our Service Desk to obtain 6.0 license keys if you have current Dbvisit Standby support
• Oracle Databases or servers will not be restarted during the installation
• This software is compatible with Oracle 8i, 9i, 10g and 11g databases (may support Oracle 7.3 and 8.0 in come cases)
• This software supports single instance and RAC databases

To price and order Dbvisit Standby, please visit the Pricing and Ordering page.

Pricing comparison example - Dbvisit Standby versus Data Guard pricing

This comparison shows Oracle Standard Edition One (SE1) price together with Dbvisit Standby, compared to upgrading to Oracle Enterprise Edition (EE) to access Oracle Data Guard.