Comment 1 for bug 741021

Revision history for this message
Henrik Ingo (hingo) wrote :

Similarly, when doing an incremental backup:

  $XTRABACKUP --backup --target-dir=$INC --incremental-basedir=$APPLY_DIR 2>>$INC/$BACKUPNAME.log

I get these lines in stderr/the log file:

xtrabackup: uses posix_fadvise().
xtrabackup: cd to /var/lib/mysql
xtrabackup: Target instance is assumed as followings.
xtrabackup: innodb_data_home_dir = ./
xtrabackup: innodb_data_file_path = ibdata1:10M:autoextend
xtrabackup: innodb_log_group_home_dir = ./
xtrabackup: innodb_log_files_in_group = 2
xtrabackup: innodb_log_file_size = 5242880
>> log scanned up to (0 21014228)
>> log scanned up to (0 21014228)

And these lines in stdout/console:

xtrabackup_51 Ver 1.5 Rev 203 for 5.1.52 pc-linux-gnu (i686)
incremental backup from 0:21013878 is enabled.
[01] Copying ./ibdata1
     to //data/backups/hingo-nokia-vm/12/inc1/ibdata1.delta
[01] ...done
xtrabackup: The latest check point (for incremental): '0:21014228'
xtrabackup: Stopping log copying thread.
xtrabackup: Transaction log of lsn (0 21014228) to (0 21014228) was copied.