Documentation Home
MySQL Cluster Manager 1.2 User Manual
Download this Manual

MySQL Cluster Manager 1.2 User Manual  /  MySQL Cluster Manager Limitations and Known Issues  /  MySQL Cluster Manager Limitations Relating to MySQL Cluster

5.3 MySQL Cluster Manager Limitations Relating to MySQL Cluster

This section describes limitations relating to MySQL Cluster functionality that is unsupported or curtailed by MySQL Cluster Manager 1.2.4.

MySQL Cluster Manager and replication.  MySQL Cluster Manager currently does not provide any explicit support for MySQL Cluster Replication. However, you should still be able to perform manual setup of replication of a MySQL Cluster that is managed by MySQL Cluster Manager.

Backup and restore operations.  Starting with version 1.2.1, MySQL Cluster Manager provides integrated backup and restore functionality. You can back up NDB databases and tables using the mcm client backup cluster command, and restore them using the restore cluster client command. Beginning with MySQL Cluster Manager 1.2.3, restoring distributed privileges is also supported.

You can also back up NDB databases and tables using the ndb_mgm client START BACKUP command, and restore them using the ndb_restore program (see ndb_restore — Restore a MySQL Cluster Backup); however MySQL Cluster Manager is not aware of backups that it was not employed to create. Both of the programs just mentioned are supplied with the MySQL Cluster distribution; for more information, see Online Backup of MySQL Cluster, and ndb_restore — Restore a MySQL Cluster Backup.


Backups of tables using storage engines other than NDB, as well as of all other database objects which are not tables, cannot be made using MySQL Cluster Manager, and must be made using some other method, such as mysqldump. (See mysqldump — A Database Backup Program.)

Rolling restarts.  Currently, all cluster nodes must be running in order to perform a rolling restart using MySQL Cluster Manager. However, MySQL Cluster itself requires only that at least one management server and all data nodes are running (in other words, any mysqld processes and any additional ndb_mgmd processes can be stopped). In such cases, you can perform the rolling restart manually, after stopping the MySQL Cluster Manager agent.

When making changes in configuration attributes only those nodes requiring a restart to make the change take effect are actually restarted. ndbapi nodes are never restarted by MySQL Cluster Manager.

Cluster upgrades and downgrades.  Not all upgrades and downgrades between different versions of MySQL Cluster are supported. (This is not an issue with MySQL Cluster Manager but rather a limitation in the MySQL Cluster software.) For information on supported online upgrades and downgrades, see Upgrading and Downgrading MySQL Cluster.