By default, all the files under the database subdirectories in the data directory are included in the backup, so that the backup includes data from all MySQL storage engines, any third-party storage engines, and even any non-database files in that directory. This section explains options you can use to selectively back up or exclude data.
There are various ways to create different kinds of partial backup with MySQL Enterprise Backup:
Including or excluding specific tables by their names. This uses the
--include-tablesor--exclude-tablesoption.Each table is checked against the regular expression specified with the
--include-tablesor--exclude-tablesoption. If the regular expression matches the fully qualified name of the table (in the form ofdb_name.table_name), the table is included or excluded for the backup. The regular expression syntax used is the extended form specified in thePOSIX 1003.2 standard. The options have been implemented with the RE2 regular expression library.Including some or all InnoDB tables, but not other table types. This uses the
--only-innodboption.Leaving out files that are present in the MySQL data directory but not actually part of the MySQL instance. This uses the
--only-known-file-typesoption.Achieving a multiple of selection effects by using a combination of the above mentioned options.
Backing up a selection of InnoDB tables usingtransportable tablespaces (TTS). This uses the
--use-ttsand the--include-tablesor--exclude-tables(or both) options.
For syntax details on all the options involved, seeSection 20.8, “Partial Backup and Restore Options”.
Typically, a partial backup is more difficult to restore than a full backup, because the backup data might not include the necessary interrelated pieces to constitute a complete MySQL instance. In particular, InnoDB tables have internal IDs and other data values that can only be restored to the same instance, not a different MySQL server. Always fully test the recovery procedure for any partial backups to understand the relevant procedures and restrictions.
The following are some command samples for partial backups.
Including all tables with names starting with“emp” into the backup:
mysqlbackup \ --host=localhost --user=mysqluser --protocol=TCP --port=3306 \ --backup-dir=$MEB_TEMP_BACKUP_DIR --backup-image=$MEB_BACKUPS_DIR/my.mbi \ --include-tables="\.emp" \ backup-to-imageTaking a backup of all tables except tables from the“mysql” and“performance_schema” databases:
mysqlbackup \ --host=localhost --user=mysqluser --protocol=TCP --port=3306 \ --backup-dir=$MEB_TEMP_BACKUP_DIR --backup-image=$MEB_BACKUPS_DIR/my.mbi \ --exclude-tables="^(mysql|performance_schema)\." \ backup-to-imageTaking a backup of all tables in the“sales” database, but excludes the table with the name“hardware”
mysqlbackup \ --host=localhost --user=mysqluser --protocol=TCP --port=3306 \ ---backup-dir=$MEB_TEMP_BACKUP_DIR --backup-image=$MEB_BACKUPS_DIR/my.mbi \ --include-tables="^sales\." --exclude-tables="^sales\.hardware$" \ backup-to-imageTaking a backup of all tables in the“sales reps” database, but excludes the table with the name“euro-asia” (special characters like spaces or dashes are supported by the partial backup options):
mysqlbackup \ --host=localhost --user=mysqluser --protocol=TCP --port=3306 \ --backup-dir=$MEB_TEMP_BACKUP_DIR --backup-image=$MEB_BACKUPS_DIR/my.mbi \ --include-tables="^sales reps\." --exclude-tables="^sales reps\.euro-asia" \ backup-to-imageBacking up all InnoDB tables:
mysqlbackup \ --host=localhost --user=mysqluser --protocol=TCP --port=3306 \ --backup-dir=$MEB_TEMP_BACKUP_DIR --backup-image=$MEB_BACKUPS_DIR/my.mbi \ --only-innodb \ backup-to-imageYou can also makecompressed and other kinds of selective backups by using the appropriate command options.
Making a Partial Backup with the Legacy Options (Deprecated)
Information in this subsection is only for using the legacy option of--include, which has been deprecated. For creating partial backups, use the--include-tables and--exclude-tables options instead.
Typically, a partial backup is more difficult to restore than a full backup, because the backup data might not include the necessary interrelated pieces to constitute a complete MySQL instance. In particular, InnoDB tables have internal IDs and other data values that can only be restored to the same instance, not a different MySQL server. Always fully test the recovery procedure for any partial backups to understand the relevant procedures and restrictions.
With its--include option,mysqlbackup can make a backup that includes some InnoDB tables but not others:
A partial backup with the
--includeoption always contains the InnoDB system tablespace and all the tables inside it.For the InnoDB tables stored outside the system tablespace, the partial backup includes only those tables whose names match the regular expression specified with the
--includeoption.
This operation requires the tables being left out to be stored in separatetable_name.ibdinnodb_file_per_table MySQL configuration option is enabled. Each.ibd file holds the data and indexes of one table only.
Those InnoDB tables created withinnodb_file_per_table turned off are stored as usual in the InnoDBsystem tablespace, and cannot be left out of the backup.
For each table with a per-table data file a string of the formdb_name.table_name is checked against the regular expression specified with the--include option. If the regular expression matches the complete stringdb_name.table_name, the table is included in the backup. The regular expression syntax used is the extended form specified in thePOSIX 1003.2 standard. On Unix-like systems, quote the regular expression appropriately to prevent interpretation of shell meta-characters. This feature has been implemented with the RE2 regular expression library.
The backup directory produced contains a backup log file and copies of InnoDB data files.
IMPORTANT: Because the InnoDB system tablespace holds metadata about InnoDB tables from all databases in an instance, restoring a partial backup on a server that includes other databases could cause the system to lose track of those InnoDB tables in other databases. Always restore partial backups on a fresh MySQL server instance without any other InnoDB tables that you want to preserve.
Example 4.22 Making an Uncompressed Partial Backup of InnoDB Tables
In this example, we have configured MySQL so that some InnoDB tables have their own tablespaces. We make a partial backup including only those InnoDB tables intest database whose name starts withib. The contents of the database directory fortest database are shown below. Of these 10 tables six (alex1,alex2,alex3,blobt3,ibstest0,ibstest09) are stored in per-table data files (.ibd files).
$ ls /sqldata/mts/testalex2.ibd ibstest0.ibd alex1.ibd blobt3.ibd alex3.ibd ibtest09.ibd We run themysqlbackup with the--include option:
# Back up some InnoDB tables.$ mysqlbackup --defaults-file=/home/dbadmin/my.cnf --include="^test\.ib.*" backup# Contents in the backup directory's subdirectory for the test database:$ ls /sqldata-backup/testibstest0.ibd ibtest09.ibd The backup directory's subdirectory for thetest database contains only backups ofibstest0 andibtest09 tables, because other InnoDB tables do not match the include pattern^test\.ib.*.
Example 4.23 Making a Compressed Partial Backup
We have configured MySQL so that every InnoDB table has its own tablespace. We make a partial backup including only those InnoDB tables whose name starts withalex orblob. The contents of the database directory fortest database is shown below.
$ ls /sqldata/mts/testalex2.ibd ibstest0.ibd alex1.ibd blobt3.ibd alex3.ibd ibtest09.ibd We runmysqlbackup with the--compress and--include options:
$ mysqlbackup --defaults-file=/home/dbadmin/my.cnf --compress \ --include=".*\.(alex|blob).*" backup The backup directory for the databasetest is shown below. The.ibz files are compressed per-table data files.
$ ls /sqldata-backup/testalex1.ibz alex2.ibz alex3.ibz blobt3.ibz