

If InnoDB data doesn't fit the memory, it is important that the buffer contains the most frequently accessed data. This buffer is very important for performance. InnoDB uses the buffer pool, which stores data and indexes from its tables in memory. Procedures and functions are however also part of the system tables (for example mysql.proc). However, stored procedures, views, and events are not, and need extra parameters to be recreated explicitly (for example, -routines and -events). Mysqldump dumps triggers along with tables, as these are part of the table definition. The data can be imported into other versions of MariaDB, MySQL, or even another DBMS entirely, assuming there are no version or DBMS-specific statements in the dump. Mysqldump dumps the data into SQL format (it can also dump into other formats, such as CSV or XML) which can then easily be imported into another database. It is the most flexible way to perform a backup and restore, and a good choice when the data size is relatively small.įor large datasets, the backup file can be large, and the restore time lengthy. It is included with MariaDB 10.1.23 and later.

Mariabackup is a fork of Percona XtraBackup with added support for MariaDB 10.1 compression and data-at-rest encryption.

In the MyISAM and InnoDB storage engines, each table has an equivalent set of files.
