NEW Dbvisit Standby Version 8 Features:
- New Central Console - easily manage one or multiple configurations from one web based interface
- Support for Cascading Standby Database (Create standby from Standby)
- New Dbvnet network component - enhanced encryption and compression
- New Oracle RAC support with the option to create a RAC enabled Standby Database
With both a graphical user interface and access to the command line, Dbvisit Standby is very simple to install, configure and administer. It assists you in creating the standby database and includes all the tools and utilities to effectively and easily manage it. Dbvisit Standby is focused on keeping it simple including:
- 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
- Full support for creating standby databases using Oracle Managed Files (OMF), Oracle Automatic Storage Management (ASM) or even RAW device based storage
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.
Dbvisit Standby Features include:
- Central Console from where multiple primary/standby configurations can be managed
- Time-delayed standby database updating
- Recover the standby database past unrecoverable archive log gaps
- Full support for Oracle Database 12c Multitenant in an Oracle Standard Edition 2 (SE2) configuration
- Create multiple standby databases from the same primary
- Creating a “cascading” standby database where a secondary standby database is created from an already existing standby database
- Transportable Media support option for creating of large databases
- Support for custom pre- and post-processing scripts
- Support for option to recover standby to specific SCN or Timestamp
- Support for creating an Oracle RAC enabled standby database
- 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*
** Linux only - planned for windows shortly
In the event of a failure Dbvisit Standby ensures applications switch 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.
- Secure encrypted communication between all Dbvisit Standby components
Dbvisit Standby Version 7 Features:
- Dbvisit communication layer between the primary and standby server allowing independence of SSH-based client/server network communication. On Unix based systems SSH can still be used as communication channel.
- Create Standby Database process including a pre-flight check to ensure environment is ready for standby creation.
- Recover a standby database to specific SCN or TIMESTAMP. This can be useful in environments where the standby database is used for reporting or data extracts. The standby can be recovered to a defined SCN or Timestamp after which it can be opened read-only for data extraction or reporting.
- Other features include: new directory structure, new improved licensing module and new Pre- and Post- processing script options as part of Graceful Switchover and Failover operations.
- Resynchronise standby database after NOLOGGING operations or archive log loss
- Run your standby database in the Cloud
- Fully automated robust standby database solution
- Creates the standby database
- Supports Oracle 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
Maintaining your database, protecting it against failures and ensuring business continuity 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.
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:
- With Oracle Database Appliance for a total solution that includes high performance hardware for your on-premises production environment, and as a cost effective, reliable disaster recovery solution to ensure business continuity
- 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 and business continuity 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.
|Oracle Databases||8i to 12c|
32 & 64 bit versions
Standard (including Oracle RAC)
Standard Two (including Oracle RAC)
|HIGHLIGHTS||Oracle flash recovery area|
ASM file systems
|Operating Systems||Windows: 2000 – 2012; (32 & 64bit)|
Linux: Intel & AMD (32 & 64bit);
Unix: HP-UX; AIX; Solaris (x86_64 and SPARC)
- Identical database management system and operating system versions on production and standby system.
- Similar storage capacity on production and standby system.
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 (activation) is executed and the standby database is converted to a primary database.
When installing Dbvisit Standby on an environment using ASM for database storage, the ASM instance (not the database itself) must be 11g+.
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
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) 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.
- 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
Latest release 8.0.14 (20 June 2017)
- Linux 64bit (OEL (5,6,7), RHEL (5,6,7) and SLES (11,12)
- MS Windows 64bit (MS Windows 2008 and above)
Readme | Latest Changes
Supports Oracle 11.2 and above
Latest release 7.0.68 (20 March 2017)
- Linux x86 32bit and 64bit (OEL (4,5,6,7), RHEL (4,5,6,7) and SLES (10,11))
- MS Windows 32bit and 64bit
- Solaris (SPARC) and x86 for Intel and AMD (Solaris 10 and 11)
Readme | Latest Changes
Supports Oracle 9i (9.2) and above
Previous release 6.0.62 (22 June 2015)
- Linux for Intel and AMD 32bit and 64bit
- MS Windows 32bit and 64bit
- Solaris (SPARC) and x86 for Intel and AMD
- IBM AIX UNIX
- Linux for Itanium IA64
- Linux for PowerPC
- HP-UX UNIX (PA-RISC 2.0 and Itanium IA64)
Readme | Latest Changes
Supports Oracle 8i and above
Access the Dbvisit Standby version support matrix for a list of supported versions and operating systems.
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 contact us to obtain your new license key.
- Free support is available during the evaluation period
- Upgrade to Dbvisit Standby 7.0 is free if you have current Dbvisit Standby support. Please contact us to obtain your new license key.
- Existing 5.1, 5.2 and 5.3 license keys are NOT valid for 6.0 or 7.0. Please contact our Service Desk to obtain 6.0 or 7.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, 11g and 12c (non multitenant) databases. Using the latest patch sets are recommended
- If using Oracle ASM for storage, using 11g is required (188.8.131.52 recommended)
- This software supports single instance and RAC databases