{"id":3193,"date":"2019-07-09T07:20:45","date_gmt":"2019-07-09T06:20:45","guid":{"rendered":"http:\/\/dasini.net\/blog\/?p=3193"},"modified":"2019-09-10T08:45:28","modified_gmt":"2019-09-10T07:45:28","slug":"mysql-innodb-cluster-recovering-and-provisioning-with-mysqldump","status":"publish","type":"post","link":"https:\/\/dasini.net\/blog\/2019\/07\/09\/mysql-innodb-cluster-recovering-and-provisioning-with-mysqldump\/","title":{"rendered":"MySQL InnoDB Cluster – Recovering and provisioning with mysqldump"},"content":{"rendered":"\n
\"Butterfly<\/figure><\/div>\n\n\n\n

As the administrator of a cluster, among other tasks, you should be able to restore failed nodes and grow (or shrink) your cluster by adding (or removing) new nodes.<\/p>\n\n\n\n

In MySQL, as a backup tool (and if your amount of data is not too big), you can use mysqldump<\/a><\/strong> a client utility that performs logical backups<\/a>.
The results are SQL statements that reproduce the original schema objects and data.<\/p>\n\n\n\n

For substantial amounts of data however, a physical backup<\/a> solution such as MySQL Enterprise Backup<\/a><\/strong> is faster, particularly for the restore operation.
Hey! guess what? You can read: MySQL InnoDB Cluster \u2013 Recovering and provisioning with MySQL Enterprise Backup<\/a><\/p>\n\n\n\n\n\n

Context<\/h2>\n\n\n\n

Let’s make it as simple as possible \ud83d\ude42
I’m using MySQL 8.0.16<\/strong>.
I have an InnoDB Cluster<\/strong> setup<\/a> – up and running.
So my main assumption is that you already know what is MySQL Group Replication<\/a> & MySQL InnoDB Cluster<\/a>.
Additionally you can read this tutorial<\/a> and this article<\/a> from my colleague lefred<\/a> or this one on Windows Platform<\/a> from my colleague Ivan<\/a>. <\/p>\n\n\n\n

Note<\/em><\/u>:<\/p>

Depending on how you configured your MySQL InnoDB Cluster, some steps could be slightly different.<\/p><\/blockquote>\n\n\n\n\n\n

Scenario 1 – Node Recovering<\/h2>\n\n\n\n