In any clustered environment, it’s essential to maintain consistent software versions, and keeping track of all available patches for the technologies in your database infrastructure can be exhausting. ClusterControl provides reports to let you know what needs to be upgraded or patched and then helps you perform the upgrades using methods to keep you secure and compliant.

Stay up-to-date and compliant, and reduce maintenance time with a little help from ClusterControl.

Available with these databases

Use ClusterControl to keep your versions in line with application needs and requirements and gradually upgrade nodes according to the technology being used.

Check database release availability online

ClusterControl offers an “upgrade node” option to check for updates and install the packages you deem correct. This is technology-dependent but critical to understanding which database solution is the one for you when planning for lifecycle updates.

Try Upgrades with ClusterControl
for yourself!

Top rated Docs




Top rated Blogs

Implementing Sovereign DBaaS using ClusterControl and Conductor – Part II

Best Practices in Scaling Databases: Part 1

Cluster-Wide Database Maintenance and Why You Need It


I need to deploy specific database configurations to align with my organization’s requirements. Can I maintain this software deployment, or will I have to manually implement these changes after a default install?

You can adjust the default template as seen here under configuration template.

What if I need to modify a server’s configuration or take a node from a cluster offline? Will I get inundated with alerts?

No problem. Just set a Scheduled Maintenance period configurable for all nodes for that specific period. You’ll be presented with the following message: “All alarms and notifications from the cluster are disabled during maintenance mode.”

I’m still using MySQL 5.7, for example, and I need to deploy this version and not the latest. Is that ok?

Yes. We don’t provide all the older versions, but we do understand that it’s hard to be on the bleeding edge versions, so we’ll always offer a previous version too. And depending on the technology, you can see 4 or 5 different versions easily deployable.