Bug #71224 | Unable to restore from incremental backup with MySQL Workbench | ||
---|---|---|---|
Submitted: | 24 Dec 2013 19:00 | Modified: | 9 Jan 2015 16:03 |
Reporter: | Nicolas De Rico | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Workbench | Severity: | S3 (Non-critical) |
Version: | 6.0.7 | OS: | MacOS (10.9) |
Assigned to: | Juan Rene Ramirez Monarrez | CPU Architecture: | Any |
Tags: | incremental, restore, workbench |
[24 Dec 2013 19:00]
Nicolas De Rico
[24 Dec 2013 20:17]
Nicolas De Rico
Re-worded synopsis.
[7 Jan 2015 14:27]
Juan Rene Ramirez Monarrez
Posted by developer: Original bug was properly identified and tacked as for version 6.1 This bug remained open by a problem restoring an incremental backup associated to the restore logic in WB. With the introductio of the copy-back-and-apply-log option in MEB the whole restore logic for partial backups changed in WB. In the past, the restore logic for incremental backups was as: 1) Identify previous full backup. 2) Identify all in between incremental backups. 3) Apply the incremental backups to the full backup 4) Restore the full backup to the server. It changed as follows: 1) Identify previous full backup. 2) Identify all in between incremental backups. 3) Restore the full backup to the server. 4) Restore each incremental backup into the server. QA confirmed they had not troubles restoring different scenarios of incremental backups. Closing bug.