InnoDB is a data storage engine used by default in MySQL database since version 5.5. It has a strong focus on reliability and performance, and features row-level locking and transaction support. It follows the ACID (atomicity, consistency, isolation, durability) model which guarantees that all transactions are handled properly and error free.
With Handy Backup you can create live snapshots of MySQL databases, independently of the storage engine used in your tables. The MySQL Backup plug-in connects to MySQL as a common client application and exports data into dump files which can then be used to recover lost data, set up replication servers, migrate to other DBMS, and much more. For more details, please refer to MySQL Backup.
Version 8.3.3, built on November 28, 2021. 112 MB
Backing up and restoring MySQL database with InnoDB tables is available in the Small Server edition of our software. Free download, 30 days trial period!
It is important to understand that InnoDB is a general-purpose engine that is designed to meet the needs of an average MySQL user. Most users never change default settings, and InnoDB delivers everything that users expect from a DBMS. However, if you want your website or application to excel, you need to develop a well thought out architecture that will provide maximum availability and performance, and let you easily scale your application when your user base grows.
InnoDB or MySQL Cluster?
Clustering is a built-in feature of the MySQL DBMS that is available in version 5.0 and higher. It lets you connect multiple computers (nodes) over a network and create a distributed system acting as a single database server. MySQL clusters use a Network DataBase (NDB) storage engine which is basically a wrapper built around original storage mechanisms that handles distributed storage and processing.
While both InnoDB and NDB are transaction-safe, they are very different in implementation and have different target uses:
InnoDB and Replication
Replication is another built-in feature of MySQL that enables you to have several MySQL databases with similar contents that don’t need to be connected all the time. It not only increases availability and performance of your applications, but can be also used for geographical distribution of data.
While clustering is based on shared-nothing architecture and suggests that all nodes are independent and self-sufficient, replication lets you assign different roles to your servers. In replication configuration, there is one Master Server that acts as a primary source of data and at least one Slave Server that is optimized for data distribution and is not supposed to receive any updates or inserts.
Since such a distribution of roles expects Slave databases to serve primarily for reading, the InnoDB storage engine loses most of its advantages. This is why it is recommended to change storage engine of your Slave databases to MyISAM instead of InnoDB. To learn more, please refer to MySQL Replication.
To set up Master-to-Slave replication configuration, you can use Handy Backup. We welcome you to download it right!
Version 8.3.3, built on November 28, 2021
Term of the Day
Backup Software Glossary
Current glossary explains various terms that you may come across while working with Handy Backup or other backup software.
Handy Backup is a backup utility for Windows Servers and PCs that is famous for its flexibility and ease of use.
The glossary contains 141 terms. The current section Databases contains 17 terms.
Other “Databases” Terms