Bug #84529 | Wrong error message (MEB restore) | ||
---|---|---|---|
Submitted: | 17 Jan 2017 11:23 | Modified: | 26 Jan 2017 5:41 |
Reporter: | Jörg Brühe (OCA) | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Enterprise Backup | Severity: | S3 (Non-critical) |
Version: | 4.0.3 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | message |
[17 Jan 2017 11:23]
Jörg Brühe
[19 Jan 2017 12:49]
MySQL Verification Team
Hello Jörg Brühe, Thank you for the report and feedback. Could you please provide exact commands used to trigger this issue? In my tests I'm seeing relatively different error with the steps from how to. ============== mysqlbackup: ERROR: Can not perform copy-back operation using raw backup snapshot. The backup_variables.txt meta file of the backup indicates that the apply-log operation has not been performed yet. Please run apply-log operation first before copy-back. Thanks, Umesh
[25 Jan 2017 15:09]
Jörg Brühe
I stand corrected: In the call that generated the misleading error message, I had also given the wrong value of "--backup-dir". I had copied too much of the "backup-to-image" call, included the "--backup-dir" option, without paying attention to its totally different meaning in a restore call. With a correct value for "--backup-dir", I also get the correct error message. IMNSHO it is a bad interface design to use the same option with two totally different meanings: - On backup, it is the root of the tree holding the backup images. - On restore, it is a directory for temporary files. But it is probably too late to fix that. Returning to this bug report: My fault, sorry. Please close it as "Not a bug", that status is not offered to me.
[26 Jan 2017 5:41]
MySQL Verification Team
Thank you Jörg Brühe for confirming. Closing as !bg. Thanks, Umesh