Maintaining mirrored database as a "live copy"

The Case

You need a mirrored database to act as a "live copy" of your production database. The data contained in the mirrored database must accord the data of the production database and be ready for disaster recovery scenarious. However, you haven't got a huge budget to install a failover cluster for it.

Moreover, the main and mirrored databases can be realized with the help of different vendors (MySQL <-> DB2 or Postgres <-> ORACLE or any couple of types of databases).

Main goals to be achived

• keeping the data in the mirrored database in step (low as practicable) with the main database;
• reducing expenditure for the maintenance of the mirrored database;

Our solution is

Use Cross-Database Studio 6.0 to maintain the mirrored database:

1. Define the list of the tables in the production database and in the mirrored database.
2. Synchronize the assigned tables between the production and mirrored databases;
3. Make the data synchronization at required intervals, according to your requirement;

You can assign the synchronization at night, or at any time you are comfortable with, by using the scheduling capabilities of the CDBS products.

Advantage of our solution

• A cost-effective solution, that enables to create backup copies while saving tens of thousands USD compared with product license feesfrom other vendors;
• Automated process, and if necessary – scheduled process, ensures that the mirrored database will be kept in step with the main database;
• Allows to keep mirrored database on different from production database type of DBMS.