db.dragon · High availability for Oracle databases
Synchronize data.
Mitigate outages.
Ensure availability.
db.dragon synchronizes two independent Oracle databases, combining high availability with OS-independent operation and low acquisition costs. Use the mirror system for disaster recovery and to offload your production system.
Discover features- Redundant data storage.
- Cross-site capability.
- Oracle Standard Edition.
From production system to mirror.
Your data. Your availability.
Secure your operations.
Get more out of your mirror.
Database outages can disrupt production, order processing, and shipping. db.dragon helps safeguard these processes and is used across Europe by companies in various sectors, including the automotive industry.
Maintain redundant data
Two independent Oracle databases ensure enhanced data security. In the event of a failure, the administrator can activate the mirror system as the primary system.
Connect systems flexibly
Connect the mirror via LAN or WAN at a geographically separate location. The WAN Accelerator module supports WAN connectivity.
Relieve the production system
Offload compute-intensive queries, reports, or backups to the mirror database. Tests and analyses can also be performed there, depending on the edition and modules.
Use resources efficiently
This resource-efficient Java solution is operating-system independent. Oracle Standard Edition is sufficient; Oracle Enterprise Edition is not required for db.dragon.
Disaster recovery and production system relief – combined in a high-availability concept.
01 / How it works
Transfer changes.
React to errors.
db.dragon synchronizes two independent Oracle databases. The secondary system—the mirror—follows the primary system at a user-defined time interval. Changes to data and data structures are transferred to the mirror; available automation functions depend on the edition.
In the event of an error, db.dragon sends notifications via email or SMS (using appropriate gateways). The administrator can promote the mirror system to the primary system and subsequently restore the faulty system.
Redundant data storage and time-delayed replication help manage user and software errors, viruses, and hardware failures. A geographically remote mirror can be connected via LAN/WAN and incorporated into the disaster recovery plan for site outages.
02 / Integration & Operation
Install during live operation.
Administer centrally.
db.dragon can be installed while the primary system continues to run. Use the installation and configuration process to familiarize your administrators with its OS-independent management capabilities. In-depth Oracle knowledge is not required for operation.
Installation & Configuration
We assist you with installation and configuration during live production operations.
Integration via IP Switching
Integrate your application using IP switching, similar to a cluster setup. You can find module availability in the edition comparison.
Emergency Drills
Upon request, we conduct regular emergency drills with your staff to ensure familiarity with procedures in the event of an emergency.
03 / Modules & Versions
Compare editions.
Choose the right one.
Compare the available modules for the Professional Edition and Enterprise Edition. The TestDB Module and the WAN Acceleration Module each require an additional license key and are available in the editions listed below.
| Feature | Professional Edition | Enterprise Edition |
|---|---|---|
| Mirroring Module | Included | Included |
| Online Backup Module | Included | Included |
| Archive Cleaning Module | Included | Included |
| Service / Daemon Integration | Included | Included |
| Remote Console Module | Included | Included |
| Remote Console Module GUI | Not included | Included |
| Oracle Tracefile Archive Module | Included | Included |
| Safe Mirroring Module | Included | Included |
| E-Mail Messaging Module | Included | Included |
| SNMP Integration | Included | Included |
| Mirror Backup Module | Included | Included |
| File synchronization via Simple File Synchronization Module | Included | Included |
| File synchronization via Extended File Synchronization Module (UNC path support) | Not included | Included |
| Maintenance Switch Module | Not included | Included |
| Time Delay Apply Module | Not included | Included |
| Auto Structure Apply Module | Not included | Included |
| Read Only Usage | Not included | Included |
| Pre-Error Detection Module | Not included | Included |
| Application Switch Module | Not included | Included |
| TestDB module with additional license key | Included | Included |
| WAN acceleration module with additional license key | Not included | Included |
| Auto Network Failure Reconnect Module | Not included | Included |
| Auto LogGap Detection Module (ALGD) | Not included | Included |
04 / Modules in Detail
Combine functions.
Targeted operational support.
From archive cleanup and notifications to backups, read-only usage, and error detection: these modules complement synchronization with features designed to support your operations. Please refer to the edition comparison for specific availability.
Archive Cleaning Module (ACM)
As the number of archive files grows continuously while available storage space is typically limited, available capacity must be monitored constantly. The AC Module therefore includes an agent that keeps the number of archive files constant at all times, eliminating the need for manual checks by the administrator.
Safe Mirroring Module (SMM)
Secure mirroring service is ensured through continuous monitoring of both agents’ operations. An alert is triggered if the mirroring agent or system fails. This ensures the availability of both systems at all times.
E-Mail Messaging Module (EMM)
Errors and essential system status information are forwarded via email. With appropriate gateways, pagers and SMS services can also be addressed. Recipients and notification frequency are fully configurable. Support is provided for both a mail fallback server and SMTP-AUTH. Emails can be sent in either plain text or HTML format. By defining error classes, specific individuals can be notified depending on the type of error encountered.
Maintenance Switch Module (MSM)
A maintenance switch can be performed for maintenance tasks and emergency drills. This activates the mirror database without data loss and designates the primary database as the mirror. The switch can be executed in either direction, making it ideal for maintenance work on either system.
Time Delay Apply Module (TDAM)
This module allows you to configure a specific time delay between the mirror system and the primary/production system. Consequently, data is transferred to the mirror with a time delay. This helps prevent logical errors, such as those caused by faulty programs. The time delay is adjustable and can be deliberately increased—for instance, when switching to a new operating system version. Naturally, the time delay can also be deactivated.
Auto Structure Apply Module (ASAM)
This module automatically propagates database structure changes made in the production system to the mirror (e.g., when an additional tablespace is added). The mirror system adopts these changes and updates its structure while continuing to operate without any functional limitations.
Pre Error Detecting Module (PEDM)
Continuous monitoring of the production database allows for the detection of critical database errors—errors triggered either by the database itself or by an application. Consequently, these errors are not propagated to the mirror.
Simple/Extended File Synchronization Module (S/EFSM)
In addition to database mirroring, many systems also require file synchronization. The S/EFS module enables you to synchronize files and/or directories from the production system with the mirror system. System-independent synchronization is supported.
Auto Network Failure Reconnect Module (ANFR)
Temporary network issues are detected, and operations resume fully automatically once the connection is restored!
Online Backup Module (OB/MB)
Beyond mere database synchronization, system requirements may also call for a backup. This is provided by the OnlineBackup and MirrorBackup modules. Generally, an Online Backup is performed while the database is running. Data can be written to a local drive or a UNC path. Unlike OnlineBackup, MirrorBackup runs on the mirror host, thereby eliminating any system load on the production system. Just like OnlineBackup, MirrorBackup can be used to perform a system recovery of the production database.
In combination with the ArchiveCleaner module, this allows any system recovery requirement (backup cycles/generations) to be implemented alongside backup tape media. Unlike a pure tape backup, this method enables faster recovery because the first generation is written directly to hard disk storage.
Read-Only Module (ROM)
To generate time-critical reports without placing a load on the production database, the mirror database can be switched to read-only (RO) mode. During this time, the mirror is open for read operations, while the resulting archive files continue to be transferred from the primary system, ensuring no data loss occurs. Once RO mode ends, all accumulated changes are applied to the mirror. Activation and deactivation can be scheduled using the integrated scheduler. This allows necessary reports (such as inventory reports) to be generated overnight, for example, without requiring user intervention.
Auto LogGap Detection Module (ALGD)
Depending on the production system’s load, interruptions to the network transmission between the primary and mirror hosts can occur during operation. This can result in a “log gap”—a discrepancy between the current log file on the primary system and the one on the mirror. db.dragon automatically detects this log gap and immediately notifies the administrator. The maximum permissible lag between the PRIMARY and MIRROR hosts can be configured, allowing for adaptation to various system environments.
05 / Costs & Licensing
Plan for high availability.
Keep costs in check.
db.dragon combines high availability with low acquisition costs. Oracle Standard Edition is sufficient for deployment; purchasing Oracle Enterprise Edition is not necessary.
db.dragon is licensed based on the entire system: A single db.dragon license covers two physical systems.
In addition to disaster recovery, the mirror can also be used for queries and backups. Offloading the production system contributes to the overall value and ROI of the high-availability setup.
Your next step
Keep data available.
Plan ahead together.
Do you want to secure your Oracle databases, set up a mirror, or offload your production system? Discuss your requirements with us.
Get advice on db.dragonSchertlinstr. 39
86159 Augsburg, Germany
