The smart solution for your business continuity needs

Dbvisit Standby is the #1 Disaster Recovery solution for easy creation and management of standby databases for Oracle® Standard Edition. More than 1300 customers in 110 countries trust Dbvisit to protect their data from hardware and logical failures, natural disasters, human error and outages.

Disaster Recovery Made Easy

Maintaining your database, protecting it against failures and ensuring recovery from disasters or outages, is an essential part of a DBA's role.

But without the right tools it can prove to be the most unproductive and stressful part of it too. Because Dbvisit Standby gives you control over your database, it makes managing Oracle Standard Edition environments less of a chore and frees up more time to focus on other activities.

Designed by DBAs for DBAs, Dbvisit Standby gives you the confidence that you need to ensure business continuity and protect your existing infrastructure, whether on-premises, hybrid or in the cloud, from unexpected outages that could put your critical data at risk.

If you are considering updating your aging hardware infrastructure, Oracle Database Appliance is already optimized for Disaster Recovery with Dbvisit Standby, ensuring that you have the perfect solution for your Oracle Standard Edition environment.




    Dbvisit Standby is very simple to install, configure and administer, with both a graphical user interface and access to the command line for:

    • Step by step guided installation process
    • Optional templating function for easy recreation of standby databases
    • Customizable creation of the standby database
    • Option to script administrative tasks and run in batch mode
    • Automatic management of archived log files on the primary and secondary database
    • Cloud ready for Oracle, AWS, Microsoft Azure and Google Cloud 
    • Full support for creating standby databases using Oracle Managed Files (OMF), Oracle Automatic Storage Management (ASM) or even RAW device based storage 

    Dbvisit Standby Features

    Out of the box Dbvisit Standby provides features such as failover, graceful switchover, RAC, ASM and OMF, with a number of advanced features such as compression and encryption for archive log transportation. For a full list of features, please download the Dbvisit Standby Datasheet.

    • Central Console - easily manage one or multiple configurations from one web based interface
    • Support for Cascading Standby Database (Create standby from Standby)
    • Dbvnet network component - enhanced encryption and compression
    • Oracle RAC support with the option to create a RAC enabled Standby Database
    • Time-delayed standby database updating
    • Full support for Oracle Database 12c Multitenant in an Oracle Standard Edition 2 (SE2) configuration
    • Graceful Switchover to seamlessly switch the primary database server back to the original configuration it was in prior to an outage
    • Create multiple standby databases from the same primary 
    • Create a separate standby database for reporting purposes during the day
    • Secure encrypted communication between all Dbvisit Standby components
    • Support for custom pre- and post-processing scripts 
    • Support for option to recover standby to specific SCN or Timestamp 
    • Dbvisit Standby Archive Log Management Module (AMM) fully automates the management and monitoring of Oracle archive logs on both the primary and standby servers
    • Automatic detection of archive log generation followed by transfer of logs without dedicated schedule
    • Automatic detection of archivelog arrival at standby site and starting the application (recovery) procedure

    Real Application Cluster (RAC)

    Dbvisit Standby can be used together with Oracle RAC to provide a scalable and high availability (HA) disaster recovery (DR)  and Business Continuity (BC) 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.