In my previous eBook, I showed how to configure a Pacemaker HADR cluster and how the remote client connections behaved in various Pacemaker/HADR setups (with and without VIP and/or ACR).
However, back then I didn’t experiment at all with the separate quorum devices, which is the recommended approach for production workloads, and I made a promise (to myself and you 😊) to do that testing at a later stage and share the results with you.
So, trying to stay true to my word, I’ve just done the installation and the configuration of yet another Pacemaker/HADR cluster, this time in a cloudy AWS environment (following the current trends) and including a separate quorum device (following the “best practices”).
If you’re interested to see how it went and learn all the details, please download my latest eBook.
Configuring Db2 Pacemaker HADR cluster with QDevice in AWS
Damir Wilder demonstrates how a Db2 Pacemaker/HADR cluster with a QDevice can be deployed on RHEL9 virtual servers in the AWS VPC environment.
"APIS IT have been working to deliver a programme that moves a set of extremely important applications onto new Linux Db2 based systems. Over the past 2 years, Triton Consulting has been a trusted supplier to us as they have provided us with technology expertise in Db2 to help us when we haven't got the expertise internally. Damir's expertise in Pacemaker in particular has proved essential to us."
Robert Stanko - Director, IT Support at APIS IT d.o.o.