--include=REGEXP

Back up only those InnoDB tables whose fully qualified names match a regular expression. If the REGEXP matches db_name.table_name, the table is included. The regular expression syntax is the extended form specified in the POSIX 1003.2 standard.

For example, --include=mydb.t[12] matches the tables t1 and t2 in the database mydb. Only applies to InnoDB tables created with the MySQL option innodb_file_per_table enabled, which are in separate files that can be included or excluded from the backup. All tables in the InnoDB system tablespace are always backed up.

Default: Backs up all InnoDB tables.

--databases=LIST

Filters the list of non-InnoDB tables to back up. To filter InnoDB tables, use the --include option. The argument specifies a space-separated list of database/table names of the following form:

"db_name[.table_name] db_name1[.table_name1] ...".

By default, all databases are backed up.

--databases-list-file=PATH

Filters the list of non-InnoDB tables to back up. The specified file contains entries for databases or fully qualified table names separated by newline or space. The format of the entries is the same as for the --databases option:

   db_name[.table_name]
   db_name1[.table_name1]
   ...

Pathname to the file that contains the list of databases to be backed up separated by newlines. Remove any surrounding whitespace, because those characters are not removed automatically. Begin a line with the # character to include a comment. No regular expressions are allowed.

By default, all tables are backed up.

--only-known-file-types

By default, all files in the data directory are included in the backup. (See Section 1.4, “Files that Are Backed Up” for details.) If the --only-known-file-types option is specified, the backup includes only the files with these file extensions:

--only-innodb

Back up only InnoDB data and log files. All .frm files and files created by other storage engines are excluded. Typically used when no connection to mysqld is allowed or when there is no need to copy MyISAM or .frm files, for example, when you are sure there are no DDL changes during the backup. See Section 3.3.4.1, “Backing Up Some or All InnoDB Tables” for instructions and examples.

Can be used in combination with the --suspend-at-end option to allow customized scripting at the end of backup. Not compatible with the --slave-info option.

Default: backups include files from all storage engines.

--only-innodb-with-frm[={all|related}]

Back up only InnoDB data, log files, and the .frm files associated with the InnoDB tables. --only-innodb-with-frm=all includes the .frm files for all InnoDB tables in the backup. --only-innodb-with-frm=related, in combination with the --include option, copies only the .frm files for the tables that are included in the partial backup; if the --include option is omitted, all the .frm files are backed up. --only-innodb-with-frm with no argument is the same as --only-innodb-with-frm=related.

This option saves you having to script the backup step for InnoDB .frm files, which you would normally do while the server is put into a read-only state by a FLUSH TABLES WITH READ LOCK statement. The .frm files are copied without putting the server into a read-only state, so that the backup operation is a true hot backup and does not interrupt database processing. You must ensure that no ALTER TABLE or other DDL statements change .frm files for InnoDB tables while the backup is in progress. If the mysqlbackup command detects changes to any relevant .frm files during the backup operation, it halts with an error. If it is not practical to forbid DDL on InnoDB tables during the backup operation, use the --only-innodb option instead and use the traditional method of copying the .frm files while the server is locked.

All files created by other storage engines are excluded. Typically used when no connection to mysqld is allowed or when there is no need to copy MyISAM files, for example, when you are sure there are no DDL changes during the backup. See Section 3.3.4.1, “Backing Up Some or All InnoDB Tables” for instructions and examples.

Can be used in combination with the --suspend-at-end option to allow customized scripting at the end of backup. Not compatible with the --slave-info option.

Default: backups include files from all storage engines.