July 12, 2018 | Written by: Saygin Yag
Share this post:
After announcing Data Virtualization capabilities last month (read here), Db2 on Cloud team has even more exciting news to share with our users. We are announcing Disaster Recovery (DR) capabilities for Db2 on Cloud. It leverages Db2’s HADR technology and lets users add a DR Node on demand in an offsite data center of their choice. In an unlikely event where the primary data server is affected by external circumstances, such as a natural disaster, users can failover to their Geo-Replicated Disaster Recovery Node with a few clicks. Users can also fail back to their primary node just as easily.
A quick overview of the new HADR capabilities
- Users can add a disaster recovery node in a data center of their choice on-demand.
- In addition to failover functionality, the DR node also allows “read-on-standby” and improves performance.
- Users must initiate the failover. This process can be automated with the API that is provided with HADR functions.
- Users can failover to the DR Node and fail back to the Primary Node with a few clicks.
- Using both an HA node plus an offsite HADR geo-replicated node is the ideal option for maximum uptime. Please note that “HADR” is not the same as “HA.” HA Node, without DR, automatically completes the failover, is synchronous, and both servers are in the same data center.
- For technical documentation on Db2 on Cloud Geo-Replicated Disaster Recovery, click here.
High Availability vs. Disaster Recovery
Previously, Db2 on Cloud introduced the High Availability Node feature, which offers an on-demand warm standby node that is constantly synced with the primary server within the same data center. This node provides the user with a 99.99% uptime SLA. When required, failover to the HA node is managed seamlessly and automatically by IBM using automatic client reroute (ACR) and portable IPs.
With the introduction of Geo-Replicated Disaster Recovery Nodes, users are now able to add an on-demand Disaster Recovery Node to their primary server, regardless of whether they have an HA node synced to their primary server. In rare cases, data centers can be affected by unexpected circumstances, such as fires, region-wide outages, earthquakes, and storms. During such events, a server’s connection with client apps may be lost. Therefore, without a Disaster Recovery node, data stored in these data centers is exposed to the risk of being lost, even with HA capabilities. Disaster Recovery Node ensures that users’ valuable data is safely stored in a data center that is located in a different geography (e.g., Primary Node: Dallas, DR Node: Toronto).
How to get started
If you are already a Db2 on Cloud user:
- Click your instance in the dashboard. You’ll now see a “Manage Disaster Recovery” button. You can add a Geo-Replicated Disaster Recovery Node from there.
- If you purchased Db2 on Cloud on contract via a sales representative and do not have an IBM Cloud subscription, please contact your IBM representative to add a DR Node.
If you are currently not a Db2 on Cloud user:
- Click here to order Db2 on Cloud via IBM Cloud, or speak to your IBM sales representative.
- Learn about Db2 on Cloud using our tutorials via Digital Technical Engagement or read the docs.
Here is a quick glance at how easy it is to initiate the failover:
We have recently introduced some key features, such as the free-forever lite plan, data virtualization, and web console enhancements along with our existing option for a 99.99% uptime SLA. We’re excited to add our new Geo-Replicated Disaster Node capability to the mix. Stay tuned for more capabilities coming soon.