| Bug #64904 | innodb-log-files-in-group must be specified for copy-back (default not used) | ||
|---|---|---|---|
| Submitted: | 8 Apr 2012 0:35 | Modified: | 28 Feb 2013 16:05 |
| Reporter: | Ronald Bradford | Email Updates: | |
| Status: | Not a Bug | Impact on me: | |
| Category: | MySQL Enterprise Backup | Severity: | S3 (Non-critical) |
| Version: | 3.7.0 | OS: | Linux (Ubuntu 11.10 64bit) |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | copy-back, innodb-log-files-in-group, mysqlbackup | ||
[9 Apr 2012 16:07]
Sveta Smirnova
Thank you for the report. We already discuss this issue internally. Current reasoning is: User can specify different locations for copy-back operation during restore time. Therefore such options as datadir or innodb_data_file_path, innodb_log_group_home and innodb_data_home_dir can be changed. mysqlbackup can not get these options from running server, because it must be stopped for copy-back operation. Also there was idea to check sanity of specified values for innodb_log_files_in_group and innodb_log_file_size. This currently does not happen. So setting bug to "Verified" and linking to Internal bug report.
[28 Feb 2013 16:05]
Sanjay Manwani
MEB Team: Mysqlbackup reads the server configuration as well as the backup configuration. It checks them for compatibility before it copies back. If it would just take the backup configuration for the server configuration, the server would refuse to start if its configuration is incompatible to the backup configuration. In most cases it is not necessary to specify the server configuration explicitly as it is searched at the standard places. There was some ambiguity in the discussion. If there was a case where mysqlbackup did not notice a configuration incompatibility, please report a new bug for it.
Description: When attempting to perform a restore using mysqlbackup, the option innodb-log-files-in-group must be specified. The default value (aka unspecified) is not used. This variable is not defined but defaults for running backups. i.e. $ time /opt/meb/bin/mysqlbackup --incremental --incremental-base=dir:/mysql/backup/meb/first --incremental-backup-dir=/mysql/backup/meb/first-inc backup MySQL Enterprise Backup version 3.7.0 [2011/12/19] Copyright (c) 2003, 2011, Oracle and/or its affiliates. All Rights Reserved. INFO: Starting with following command line ... /opt/meb/bin/mysqlbackup --incremental --incremental-base=dir:/mysql/backup/meb/first --incremental-backup-dir=/mysql/backup/meb/first-inc backup -------------------------------------------------------------------- Server Repository Options: -------------------------------------------------------------------- datadir = /var/lib/mysql/ innodb_data_home_dir = innodb_data_file_path = ibdata1:5000M:autoextend innodb_log_group_home_dir = /var/lib/mysql/ innodb_log_files_in_group = 2 innodb_log_file_size = 134217728 How to repeat: $ /opt/meb/bin/mysqlbackup --defaults-file=/etc/mysql/my.cnf --backup-dir=/mysql/backup/meb/first copy-back MySQL Enterprise Backup version 3.7.0 [2011/12/19] Error: Server innodb_log_files_in_group is missing or invalid mysqlbackup: ERROR: Server repository configuration problem found. $ /opt/meb/bin/mysqlbackup --defaults-file=/etc/mysql/my.cnf --backup-dir=/mysql/backup/meb/first --innodb-log-files-in-group=2 copy-back MySQL Enterprise Backup version 3.7.0 [2011/12/19] Copyright (c) 2003, 2011, Oracle and/or its affiliates. All Rights Reserved. Suggested fix: Apply the default, as per when running a backup