Documentation Home
MySQL Enterprise Backup 3.7 User's Guide
PDF (US Ltr) - 0.8Mb
PDF (A4) - 0.8Mb
EPUB - 171.6Kb

MySQL Enterprise Backup 3.7 User's Guide  /  ...  /  Source Repository Parameters

### 4.2.1 Source Repository Parameters

The following parameters are supported in configuration files under the `[mysqlbackup]` group. The underscore characters in parameter names can be replaced with dashes and treated as synonyms, similar to mysqld parameters that use this same convention. (See Using Options on the Command Line in the MySQL Reference Manual for details.) The documentation typically lists the names with underscores, to match the output of the ```SHOW VARIABLES``` statement.

For information about how these options are specified for the MySQL server, click the option name to see the description in the MySQL Reference Manual.

• This is the `datadir` value used by the MySQL instance. The `.frm` files live here inside subdirectories named after the databases inside the instance.

When a database connection exists, the value is retrieved automatically and overrides any value you specify. This is a crucial parameter for both the MySQL server and MySQL Enterprise Backup.

• Specifies the directory where InnoDB data files live. Usually the same as `datadir`, but can be different.

This parameter, together with `innodb_data_file_path`, determines where the InnoDB data files such as `ibdata1`, `ibdata2`, and so on, are situated within the MySQL server.

Typically, you do not need to specify this option, because its value is retrieved automatically using the database connection.

Its value is derived as follows:

• If `innodb_data_home_dir` is not specified, it inherits the value of `datadir`.

• If `innodb_data_home_dir` is a relative path, that path is located relative to (that is, underneath) the `datadir` value.

• An `innodb_data_home_dir` of `""` refers to the `/` root directory.

• If `innodb_data_home_dir` is an absolute path, its value is used as-is.

• Specifies InnoDB data file names and sizes. Examples:

```ibdata1:32M;ibdata2:32M:autoextend
/abs/path/ibdata1:32M:autoextend
innodb-dir/ibdata1:32M:autoextend
```

When a database connection exists, the value is retrieved automatically and overrides any value you specify.

This parameter together with innodb_data_home_dir determines where the InnoDB data files (such as `ibdata1`, `ibdata2`, and so on) live in server repository.

Typically, you do not need to specify this option, because its value is retrieved automatically using the database connection. If no database connection is available, you must specify it.

Whether the initial filename begins with a `/` character or not, the files are located relative to the `innodb_data_home_dir` value.

• Specifies where InnoDB logs live within the server repository. Usually the same as `datadir`, but can be different.

Its value is derived as follows:

• If `innodb_log_group_home_dir` is not specified, it inherits the value of `datadir`.

• If `innodb_log_group_home_dir` is a relative path, that path is located relative to (that is, underneath) the `datadir` value.

• If `innodb_log_group_home_dir` is an absolute path, its value is used as-is.

• Specifies the number of InnoDB log files before being rotated.

Typically, you do not need to specify this option, because its value is retrieved automatically using the database connection. If no database connection is available, you must specify it.

When a database connection exists, the value is retrieved automatically and overrides any value you specify.

• Specifies maximum single InnoDB log file size before switching to next log file. Example: 20M.

Typically, you do not need to specify this option, because its value is retrieved automatically using the database connection. If no database connection is available, you must specify it.

When a database connection exists, the value is retrieved automatically and overrides any value you specify.