Bug #57906 Error in Applying an Incremental Backup to a Full Backup
Submitted: 1 Nov 2010 19:35 Modified: 9 Apr 2012 22:37
Reporter: Pavan Venkatesh Email Updates:
Status: Closed Impact on me:
Category:MySQL Enterprise Backup Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: Thava Alagu CPU Architecture:Any

[1 Nov 2010 19:35] Pavan Venkatesh
When Applying an Incremental Backup to a Full Backup, there is a error.
We cant execute full.cnf as there is no log file in fullbackup directory.

pavan-k-venkateshs-macbook-pro:meb-3.5.next-osx10.5-universal Pavan$ sudo ./ibbackup --apply-log /usr/local/fullbackup/full.cnf
ibbackup version 3.5.2 MySQL Enterprise Backup 3.5.2
Copyright (c) 2002, 2010, Oracle and/or its affiliates.
Run 'ibbackup --help' for help and 'ibbackup --version' for version info.

Contents of /usr/local/fullbackup/full.cnf:
innodb_data_home_dir got value /usr/local/fullbackup
innodb_data_file_path got value ibdata1:100M;ibdata2:10M:autoextend
datadir got value /usr/local/fullbackup
innodb_log_group_home_dir got value /usr/local/fullbackup
innodb_log_files_in_group got value 4
innodb_log_file_size got value 104857600

101014 13:16:58  InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: File name /usr/local/fullbackup/ibbackup_logfile
InnoDB: File operation call: 'open'.
InnoDB: Cannot continue operation.

How to repeat: