Replication for Azure BYOC

Q Replication technology is now available for Db2® Warehouse SaaS on Azure BYOC, enabling high availability and disaster recovery.

Overview

Replication enables continuous availability, including disaster recovery, by synchronizing transactions over both row and column organized tables. This works across platforms, data centers, or globally in an active-active configuration.

It offers near real-time asynchronous data replication from a primary database server to one or more standby replicas. This supports workload balancing, planned outage handling, and significantly reduces recovery time during unplanned outages.

Requirements

Two Db2 Warehouse instances are needed.

Important: When provisioning or deploying an instance of Db2 Warehouse inside the data plane, you must select either Public Load Balancer option and/or Private Link Service option.

While enabling the Replication feature:

  • You will have to choose either Public (default) or Private connection type, if you had chosen Private Link Service when deploying the Db2 Warehouse instance.
  • Once replication is enabled with one connection type (either public or private), it cannot be switched to the other connection type.
  • To change the connection type, replication must be deactivated and a support case opened to reset replication settings before reactivating replication with the new connection type.
  • Switching between connection types for replication will require all replication configuration steps to be performed again.
  • Replication must be activated individually on each instance via the SaaS Data Management Console
  • The option to activate Replication in the SaaS Data Management Console is located under: Administration → Replication tab.
Note: Activation may take up to 60 minutes and will restart the Db2 database, so it should be done during a maintenance window.

An admin user and credentials must be provided when associating a target to a source Db2 Warehouse system.

Learn more

For detailed instructions and configuration steps, please refer Q Replication for Continuous Availability