BACKUP DATABASE backs up database and table definitions, table data, stored routines, triggers, events, and views. TEMPORARY tables are not included. Tablespace backup support is limited to the Falcon storage engine. For anything else not explicitly listed, assume that it is not backed up. This includes but is not limited to items such as privileges, UDF definitions and files, logs, and option files.

The BACKUP DATABASE statement does not back up the mysql or INFORMATION_SCHEMA databases.

There is no way to determine the contents of a backup image produced with BACKUP DATABASE. That is, you cannot determine which databases are in a given backup image and will be restored by using it with RESTORE.

RESTORE is a destructive operation. Each restored database is first dropped and then created and populated with the tables contained in the backup image. There is no warning about existing data being overwritten.

BACKUP DATABASE and RESTORE cannot be used in stored routines, triggers, or events.

BACKUP DATABASE and RESTORE cannot be used as prepared statements.