MySQL Bugs: #60058: Backup history logs does not show Image as backup

Bug #60058	Backup history logs does not show Image as backup_format
Submitted:	9 Feb 2011 18:46	Modified:	16 Feb 2011 9:43
Reporter:	Hema Sridharan	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Enterprise Backup	Severity:	S3 (Non-critical)
Version:	MEB 3.6	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
Execute backup to image using --backup-image option of new mysqlbackup command.
Once backup is completed, check the history logs and we can notice that backup_format always shows as "Directory" even if backup is performed to an image.

How to repeat:
--echo # Run mysqlbackup to image
--exec $MYSQLBACKUP --port=$MASTER_MYPORT  --protocol=tcp --user=root --backup-image=$MYSQLTEST_VARDIR/tmp/backupabs.mbi --backup-dir=$BACKUP_TARGET_DIR backup-to-image > $BACKUP_LOG 2>&1

SELECT * FROM mysql.backup_history;;
backup_id       BACKUP_ID
tool_name       MYSQLBACKUP --port=[#####] --protocol=tcp --user=root --backup-image=MYSQLTEST_VARDIR/tmp/backupabs.mbi --backup-dir=MYSQLTEST_VARDIR/tmp/mysqlbackup backup-to-image
start_time      START_TIME
end_time        STOP_TIME
binlog_pos      BINPOS
binlog_file     BINLOG-DISABLED
compression_level       0
engines MEMORY:MyISAM:InnoDB:CSV:
innodb_data_file_path   ibdata1:10M;ibdata2:10M:autoextend
innodb_file_format      Antelope
start_lsn       SLSN
end_lsn ELSN
incremental_base_lsn    ILSN
backup_type     FULL
backup_format   DIRECTORY --------------> Should have been "IMAGE"
mysql_data_dir  MYSQLTEST_VARDIR/mysqld.1/data/
innodb_data_home_dir    MYSQLTEST_VARDIR/mysqld.1/data
innodb_log_group_home_dir       MYSQLTEST_VARDIR/mysqld.1/data
innodb_log_files_in_group       10
innodb_log_file_size    10485760
backup_destination      MYSQLTEST_VARDIR/tmp/mysqlbackup
lock_time       LOCK_TIME
exit_state      SUCCESS
last_error      NO_ERROR
last_error_code 0

Verified on Mac OS X. Actually, my backup was unsuccessful:

...
Adding File[139] [Size:8622]: u/pet.frm
 mysqlbackup: INFO: A copied database page was modified at 1750030.
          (This is the highest lsn found on page)
          Scanned log up to lsn 1751804.
          Was able to parse the log up to lsn 1751804.
          Maximum page number for a log record 401
Adding File[140] [Size:2560]: ibbackup_logfile
110210 21:20:12 mysqlbackup: INFO: All tables unlocked
 mysqlbackup: INFO: All MySQL tables were locked for 0.000 seconds
Adding File[141] [Size:18]: meta.dir/ibbackup_binlog_info
 mysqlbackup: WARNING: Problem while adding meta file into image: /tmp/backup/meta.dir/backup-my.cnf
Adding File[142] [Size:141]: meta.dir/ibbackup_export_variables.txt
Error: operation failed.

-------------------------------------------------------------
   Parameters Summary         
-------------------------------------------------------------
   Start LSN                  : 1750016
   End LSN                    : 1751804
   Highest modified page LSN  : 1750030
-------------------------------------------------------------

But still backup_format is wrong:

*************************** 3. row ***************************
                backup_id: 12973656101648770
                tool_name: bin/mysqlbackup -uroot --backup-image=/tmp/test.mbi --backup-dir=/tmp/backup backup-to-image 
               start_time: 2011-02-10 21:20:10
                 end_time: 2011-02-10 21:20:12
               binlog_pos: -1
              binlog_file: BINLOG-DISABLED
        compression_level: 0
                  engines: MEMORY:MyISAM:CSV:PERFORMANCE_SCHEMA:InnoDB:
    innodb_data_file_path: ibdata1:10M:autoextend
       innodb_file_format: Antelope
                start_lsn: 1750016
                  end_lsn: 1751804
     incremental_base_lsn: 1750030
              backup_type: FULL
            backup_format: DIRECTORY
           mysql_data_dir: /Users/openxs/dbs/5.5/data/
     innodb_data_home_dir: 
innodb_log_group_home_dir: /Users/openxs/dbs/5.5/data/
innodb_log_files_in_group: 2
     innodb_log_file_size: 5242880
       backup_destination: /tmp/backup
                lock_time: 0.000
               exit_state: FAILURE
               last_error: NO_ERROR
          last_error_code: 0

This has been fixed in the latest patch.