Bug #58734 Incremental backup with per-table tablespaces failing on Windows
Submitted: 4 Dec 2010 22:05 Modified: 27 Apr 2011 17:28
Reporter: Victor Kirkebo Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Enterprise Backup Severity:S3 (Non-critical)
Version:3.5.2 OS:Any
Assigned to: Ritheesh Vedire CPU Architecture:Any
Triage: Triaged: D1 (Critical)

[4 Dec 2010 22:05] Victor Kirkebo
Description:
Running an incremental backup with per-table tablespaces on windows fails with ouput like this:

...
ibbackup: We wait 1 second before starting copying the data files...
101204 11:55:32  ibbackup: Copying H:\victor\meb\test_results\5.5.8\20101204_113316_MBR_5.5.8\var\master-data\ibdata1 (Antelope file format).
101204 11:55:41  ibbackup: Copying H:\victor\meb\test_results\5.5.8\20101204_113316_MBR_5.5.8\var\master-data\betony_features\t_part_range#p#oldest.ibd (Antelope file format).
InnoDB: Warning: cannot delete file H:\victor\meb\test_results\5.5.8\20101204_113316_MBR_5.5.8\2010-12-04_11-55-27\betony_features\t_part_range#p#oldest.ibd
InnoDB: Are you running ibbackup to back up the file?
101204 11:57:30  InnoDB: Operating system error number 3 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: Warning: cannot delete file H:\victor\meb\test_results\5.5.8\20101204_113316_MBR_5.5.8\2010-12-04_11-55-27\betony_features\t_part_range#p#oldest.ibd
InnoDB: Are you running ibbackup to back up the file?
101204 11:57:40  InnoDB: Operating system error number 3 in a file operation.
InnoDB: The error means the system cannot find the path specified.
.....

The last message repeats itself every 10 seconds a total of 200 times. After this the backup fails with:

ibbackup: Error: log scan was only able to reach 256032768,
ibbackup: but a checkpoint was at 845443880.
ibbackup: This means that the database server has overwritten
ibbackup: a part of the circular InnoDB log files before ibbackup
ibbackup: was able to read it.

---------------------

The failure in the end happens simply because ibbackup spent more than half an hour trying to delete a pertable ibd file file whose path does not exist.
This seems to happen only on Windows and only for incremental backup where pertable tablespaces are present.

How to repeat:
On Windows: set up a database with pertable tablespaces and run first a full backup and then an incremental backup
[7 Dec 2010 11:45] Satya B
Run meb.incremental_inb / incremental after creating the files incremental_inb-master.opt /incremental_ibb-master.opt with --innodb-file-per-table=1

Branch: mysql-5.1-meb
[27 Apr 2011 17:28] John Russell
Added to 3.5.3 changelog:

Running an incremental backup on a database with per-table tablespaces could fail on Windows systems.