- B Compatibility Information for MySQL Enterprise Backup Releases and InnoDB Hot Backup
- B.1 Compatibility with Older MySQL or InnoDB Versions
- B.2 Compatibility of Backup Data with Other MySQL Enterprise Backup Versions
- B.3 Expanded Use of Configuration Files
- B.4 Relative and Absolute Paths
- B.5 New and Changed Options in MySQL Enterprise Backup 3.6
- B.6 Comparison of MySQL Enterprise Backup and InnoDB Hot Backup
- B.7 ibbackup and innobackup Commands
Table B.1. New and Changed mysqlbackup Options in MySQL Enterprise Backup 3.6
Old Option | New Option | Notes |
|---|---|---|
--lsn= | --start-lsn= | The option name is changed for clarity. |
--use-memory=MB | --limit-memory=MB | The option name is changed for clarity. |
--compress[= | --compress and
--compress-level= | The former single option is split into two, with an explicit option to enable compression. |
--no-timestamp | --with-timestamp |
The default is reversed: no timestamp subdirectory is
created. To preserve the former behavior, specify
|
New option. | ||
New option. | ||
New option. | ||
New option. | ||
New option. | ||
New option. | ||
New option. | ||
New option. | ||
New option. | ||
New option. | ||
|
This option is promoted to a mode of operation. Instead
of specifying a configuration file and a path to the
backup data, now you specify the location of the backup
data with the | |
|
This option is promoted to a mode of operation. Instead
of specifying a configuration file, now you specify the
location of the backup data with the
| |
|
This former combination of options is promoted to a mode
of operation. Instead of supplying the paths of two
user-created configuration files, you specify the
location of the incremental and full backup directories
with the |
User Comments
Add your own comment.