In MySQL Enterprise Backup 3.5 and earlier, only a limited set of configuration
parameters were recognized in the my.cnf
file, and the backup commands required the paths to one or two
configuration files as command-line parameters. In MySQL Enterprise Backup 3.6
and higher, many more parameters are recognized from the
configuration file, and the configuration file is automatically
located using the same mechanism as the mysqld
server. For example, connection settings for the database can now
be read from the configuration file rather than specified as
command-line parameters. Settings such as
innodb_data_home_dir are now determined from
the database connection, rather than required to be specified in
the configuration file. Because of the enhanced processing of
configuration files and additional command-line options, the
second configuration file used by the former
ibbackup command is no longer needed.

User Comments
Add your own comment.