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:
None 
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
Description:
When I try to restore from an incremental backup, the restore fails with this:

Traceback (most recent call last):
  File "/Applications/MySQLWorkbench.app/Contents/Resources/libraries/workbench/wizard_progress_page_widget.py", line 180, in thread_work
    self.func()
  File "/Applications/MySQLWorkbench.app/Contents/PlugIns/wba_meb/wb_admin_meb_restore.py", line 516, in process_incremental_backups
    self.context.server_interface.backup_apply_incremental(self.prep_full_backup.data_path, b.data_path, self.process_log)
  File "/Applications/MySQLWorkbench.app/Contents/PlugIns/wba_meb/wb_admin_meb_syshelpers.py", line 373, in backup_apply_incremental
    self.move_file(incremental_path, archive_path)
  File "/Applications/MySQLWorkbench.app/Contents/PlugIns/wba_meb/wb_admin_meb_syshelpers.py", line 645, in move_file
    command = self._context.ctrl_be.list2cmdline("mv", from_path, to_path)
AttributeError: 'WbAdminControl' object has no attribute 'list2cmdline'
ERROR: Prepare and apply incremental backup files for recovery: 'WbAdminControl' object has no attribute 'list2cmdline'
Failed

How to repeat:
Perform a full backup.
Perform an incremental backup.
Perform an incremental backup.
Restore 1st or 2nd incremental backup (uncheck "Use most recent backup").
Fails in "Prepare and apply incremental backup files for recovery" phase.
[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.