For convenience while upgrading to the latest
mysqlbackup syntax, you can use the previous
ibbackup and innobackup
command names and syntax. When the mysqlbackup
command is run under one of those other names, either through a
symbolic link or by copying the executable file to a new filename,
it supports the same option syntax, output filenames, and other
behavior as in MySQL Enterprise Backup 3.5. These alternative command names are
included in the MySQL Enterprise Backup installation, using the appropriate
mechanism for each operating system. For information about the
older command names and option syntax, see
MySQL Enterprise Backup User's Guide (Version 3.5.4).
We strongly advise our customers to upgrade to the new mysqlbackup syntax. We intend to deprecate the old ibbackup and innobackup syntax soon.
Example B.1. Simple Backup Emulating ibbackup Behavior
If you have older scripts that use the ibbackup command with 2 configuration files specified on the command line, a corresponding mysqlbackup command looks like:
mysqlbackup --only-innodb --no-connection --backup-dir=/path/to/backup backup
The above command does not back up
MyISAM files as ibbackup does.
my.cnf must include 6 essential
parameters in the
[mysqld] section or in the
[mysqlbackup] section. For example, the
my.cnf might look like:
[mysqld] datadir = /backup/mysql innodb_data_file_path = ibdata1:256M;ibdata2:256M:autoextend innodb_log_group_home_dir = /backup/mysql/innodb/log innodb_data_home_dir = /backup/mysql/innodb/data innodb_log_file_size = 256M innodb_log_files_in_group = 3 [mysqlbackup] backup_innodb_log_group_home_dir = /backup/mysql/innodb/log [Optional] backup_innodb_data_file_path = ibdata1:256M;ibdata2:256M:autoextend [Optional] backup_innodb_data_home_dir = /backup/mysql/innodb/data [Optional] backup_innodb_log_file_size = 256M [Optional] backup_innodb_log_files_in_group = 3 [Optional]
backup_innodb_* options typically have the
same values as the corresponding
options, in which case you do not need to specify them.