Setting up disaster recovery for Db2 Warehouse SaaS on Azure

This topic provides step-by-step instructions for setting up Disaster Recovery (DR) for IBM Db2® Warehouse SaaS on Azure engines. The disaster recovery (DR) for Db2 Warehouse SaaS on Azure ensures business continuity by allowing you to configure a secondary environment that can be used in case of failure.

Before you begin

• Active Db2 Warehouse BYOC instance
• Access to the Admin console
• Azure account with required permissions
• At least one Db2 Warehouse engine deployed

About this task

In Db2 Warehouse SaaS on Azure, the disaster recovery setup involves two distinct responsibilities:

• Admin console: It is used to link a secondary dataplane that serves as the disaster recovery target

• Engine console (Q Rep): QRep provides asynchronous replication of data between Db2 Warehouse instances, and is used to configure replication between the primary and DR environment. For a step-by-step walkthrough, see the QRep documentation.

The Admin console workflow enables you to:

• Link a secondary dataplane
• Validate permissions and connectivity
• Prepare the environment for replication

After the dataplane is successfully linked, you must use the engine console to complete the replication setup.

1. Navigate to the Admin console and open the Home page.

   The following information shall be visible:

   • Instances section lists all engines
   • Linked dataplanes shows connected dataplanes
   • Dataplane details panel displays dataplane information

   

2. In the Linked dataplanes section, click Link Data plane for disaster recovery which would act as a disaster recovery target..

   

3. Select a dataplane from the Select Data plane drop down .This dataplane will be used as the DR environment
4. Click Deploy and complete the ARM template deployment in Azure.

   A new tab opens in the Azure portal. Upload the ARM template and complete deployment. The deploy button is disabled until selection and is enabled after dataplane selection

5. Click Verify Role and wait for validation to complete. The system checks Azure roles, deployment, and permissions. After validation succeeds, click Link Dataplane.

6. Once the dataplane is successfully linked, the dialog closes automatically. The dataplane appears in the table with the status shown as Linked, indicating that it is ready for disaster recovery setup.

   

   If linking fails, the status will show 'Failed'. Use Retry from the Actions menu.

7. View linked dataplanes.

   

   The following information about the data plane is visible:

   • Name: dataplane identifier
   • Region: location
   • Link: navigate to dataplane
   • Policies : IAM details
   • Status: Linked or Failed
   • Actions: Retry or Unlink

8. In the Policies column, click Role Assignments and review the details.

   The following information will be displayed:

   • Managed identity
   • Assigned roles
   • Permissions

9. Create a Db2 Warehouse engine in the linked dataplane that will act as the disaster recovery (target) engine.
   1. Navigate to the Engines section.
   2. Click Create Engine.
   3. Configure the engine settings.
      • Connectivity options:
        • Public Load Balancer: allows public access to the engine
        • Private Link Service: enables private connectivity
      • Compatibility:
        • Optional: Enable Oracle compatibility configuration if required.
      • Compute:
        • Select Type: Standard or Memory Optimized.
        • Select a Compute size.
      • Storage:
        • Configure Block storage (TB).
   4. Enter the Db2 warehouse credentials.
   5. Review the configuration.
   6. Click Create to create the Db2 engine.

   

   

Results

A secondary dataplane is linked and validated. The environment is ready for disaster recovery configuration using the engine console.

What to do next

Continue with replication setup using the engine console (QRep).

For a step-by-step walkthrough of the Q Rep configuration, see the interactive demo.