iblync · Disaster recovery replication

Disaster recovery replication: keeping a standby database in sync

A disaster recovery plan needs current data at a second site. iblync can keep a standby database in sync with production, as part of that plan.

  • Built and supported by Interkey An Interkey product, delivered and supported by Interkey
  • Continuous sync with controlled load Transfer speed and resource use can be limited
  • Weekly and monthly reports A detailed record of each transfer, with proof that it completed

Disaster recovery replication keeps a second copy of a database up to date at another site, so the organisation has current data to work from if the main site is lost. This is a possible use of iblync, built by Interkey: continuous synchronisation between the production database and a standby, with control over the load on production. Switching to the standby remains a step in your own recovery plan.

Where replication sits in a recovery plan

A disaster recovery plan covers far more than data. It names a second site, the people who act when the main site is lost, the order in which systems come back, and the steps each team follows. It is tested, and it belongs to the organisation that wrote it.

Replication takes care of one part of that plan: making sure the data at the second site is current when it is needed. Without it, the second site holds only what the last backup copied, and everything written since then is missing. With a standby database kept in sync with production, the second site starts from recent data.

The rest stays with the plan: the decision to switch, the switch itself and the tests that prove it works. The wider design, from sites to testing, is covered on our disaster recovery page.

How the standby is kept in sync

One pattern, assessed for each project: production stays where it is, and iblync applies its changes to a standby database at a second site.

  1. Production database

    at the main site, serving users as usual

  2. iblync

    continuous real-time sync transfer speed and resource use limited changes queued while the standby is unavailable
  3. Live standby copy

    at the second site, with current data for your recovery plan

Moving applications to the standby is a step in your own recovery plan. The diagram shows how the data gets there, not the switch.

What iblync does in this use

iblync, Interkey's platform for migration and continuous sync, is delivered with the Interkey team that operates it. The price is discussed in a pricing meeting.

01

Continuous real-time sync

Each change on the production database is applied to the standby as it happens, so the copy at the second site stays current. More on our real-time replication page.

02

Control over the load

Transfer speed and resource use can be limited, so keeping the standby current does not slow the production systems it is there to protect.

03

A queue when the standby stops

If the standby or the link to the second site is unavailable, changes wait in a queue and are applied when it returns.

Backup or continuous replication

Backup and continuous replication answer different failures, and a recovery plan usually needs both. Four differences set them apart. With a backup:

  • How current the data is: as of the last backup.
  • What you recover from: a saved copy, restored onto a system.
  • When you use it: after data is deleted, damaged or encrypted, to go back to a point before it happened.
  • Why the plan keeps it: it holds the past, including the state before a mistake.

What to decide before design

Seven questions to settle with your own teams before a standby is designed. The answers shape the project, and each one belongs to you.

  • Which databases need a standby, and which can be restored from backup.
  • Where the second site is, and who runs it.
  • How current the standby must be for each system, in the terms your business uses.
  • Who decides to switch to the second site, and who is called first.
  • How and how often the recovery plan is tested.
  • The network link between the two sites, and who is responsible for it.
  • Who receives the weekly and monthly replication reports.

For banks and financial institutions

Core banking, payments and customer systems are the ones a bank can least afford to see stop for long. A live standby of their databases at a second site is part of being ready: if the main site is lost, the recovery team starts from current data rather than from the last backup.

This is a use the iblync product team considers possible for banks. It is scoped for each institution against its own recovery plan, which stays the institution's own.

What this page does not claim

A part of the plan, not the plan

  • iblync does not move your applications to the second site on its own.
  • No recovery time and no figure for how current the standby is are given here: the gap is measured on your own systems during the project.
  • The recovery plan, and the responsibility for it, stay with your organisation.

Questions about replication for disaster recovery

Can iblync be used for disaster recovery?

Yes, as a possible use: iblync can keep a standby database in sync with production, as one part of a disaster recovery plan. The rest of the plan, from the second site to the people and the tests, stays with your organisation. Whether the pattern suits your systems, and its scope, are decided for each project.

Does iblync switch to the standby automatically?

No. Switching to the standby is a step in your own recovery plan, decided and carried out by your teams. In this use, iblync's part is keeping the data at the second site current, so that when the plan calls for the switch, the standby already holds recent data.

How current is the standby copy?

Sync is continuous: each change on production is applied to the standby as it happens. How far the standby trails production depends on your systems, the volume of changes and the link between sites, so it is measured on your own systems during the project. No figure is given before that.

Does this replace backups?

No. Backups protect against data being deleted or damaged, because they hold a point in the past. Continuous replication protects against losing the site, because it holds the present, and a mistake on production reaches the standby too. A recovery plan usually keeps both.

Can the standby be a different database engine?

iblync synchronises data between heterogeneous systems, so the standby is not limited to the same engine as production. Whether your exact source and target pair is supported is confirmed on our connectors page, and whether that design suits your recovery plan is decided in the project.

How do we confirm the standby matches production?

From the weekly and monthly replication reports. Each one records the transfer in detail, with proof that it completed and that source and target match, so your teams can see the standby keeps up. Our replication reports page explains what they show.

Next step

Discuss your recovery setup

Tell us which databases need a standby, where the second site is, and how current the copy must be for your recovery plan.

Required field

By sending this form, you agree to our Privacy Notice.

What happens next

  1. We read your request
  2. An engineer contacts you
  3. You get an estimate or a demo
  • Built and supported by Interkey

    An Interkey product, delivered and supported by Interkey

  • Continuous sync with controlled load

    Transfer speed and resource use can be limited

  • Weekly and monthly reports

    A detailed record of each transfer, with proof that it completed

Or directly

+966-11-2180999 [email protected]

Tawuniya Towers, North Tower, 7th Floor, King Fahad Highway, Olaya, P.O. Box 56835, Riyadh 11564, Saudi Arabia

or See real-time replication

Published by Interkey. Last updated . Interkey is registered in Riyadh, Saudi Arabia under commercial registration 1010156897.