Planet MySQL HA Blog
Clustercontrol: Monitoring the HTAP StoneDB instance
In line with maintaining sovereignty of our data and architecture, nor sacrificing security over control or viceversa, let’s see what else Clustercontrol can do to help us down that path.
There’s a “new” kid on the block, so to speak, name of StoneDB. Well after installing the “Open Source”, “100% Compatible with MySQL 5.7”, “Integration of OLTP and OLAP” and other values that each of you can consider in your own time, I thought to m
Clustercontrol: Managing that pre-existing MySQL instance.
So, as you have seen in my previous post, you can get Clustercontrol up and running extremely fast in order to deploy new instances and bring existing environments closer and take control of them all, in one foul swoop.
You’re highly unlikely to have installed Clustercontrol and now want to start letting your MySQL, PostgreSQL, Mongo, Redis, etc. go forth and multiply. I wage a bet it’s the other way around: You have lots of various environments out there, wild & untamed. Here
Just Deploy It: Any DB, anywhere! Easy as 1,2,3.
As it’s been a while since I wrote an entry, I think it’s fair to share that I’m now dedicating my time to Severalnines as Product Marketing Manager, where MySQL is still MySQL and opensource is still important.
So, first things first, What do we do in Severalnines? I’m sure you all know, but just in case, I think a picture paints a thousand words so:
Make database ops easy by automating the boring stuff, and, I’d say more importantly, help you deploy all
MySQL InnoDB Cluster Disaster Recovery contingency via a Group Replication Replica
Just recently, I have been asked to look into what a Disaster Recovery site for InnoDB Cluster would look like.
If you’re reading this, then I assume you’re familiar with what MySQL InnoDB Cluster is, and how it is configured, components, etc.
Reminder: InnoDB Cluster (Group Replication, Shell & Router) in version 8.0 has had serious improvements from 5.7. Please try it out.
So, given that, and given that we want to consider how best to fulfill the need, i.e. create a DR
InnoDB Cluster: Recovering an instance with MySQL Enterprise Backup.
Ok, so if you’re reading this, then I can guess you’ve got a MySQL InnoDB Cluster in an awkard shape, i.e. you need to restore a backup and add the instance back into the cluster, so we have all our instances again.
As it might be logical to think “ah, but I’ve only lost 1 instance, a read-only instance, so all I have to do is backup & restore the other read-only instance and I’m home free. Well I want to make it a little harder. So in this scenario, assume that