MySQL Bugs: #83732: Need a note "binlogs are not copied" for incremental backup with start-lsn

Bug #83732	Need a note "binlogs are not copied" for incremental backup with start-lsn
Submitted:	8 Nov 2016 1:59	Modified:	30 Jan 2017 17:35
Reporter:	Meiji Kimura	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Enterprise Backup Documentation	Severity:	S3 (Non-critical)
Version:	3.8, 4.0	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
When taking incremental backup with a combination --start-lsn and
 --incremental-backup-dir, there is a such a message and binlog is not
 copied as a result.

 -------------------
 mysqlbackup completed OK! with 1 warnings
 -------------------
 -------------------
 Binlog files will not be copied for this backup as --incremental-base is
 not specified.
 (snip)

 That's message means we have to specify '--incremental-base' for
 incremental backuping with binlog. There is no explain (or limitation)
 on the manual. The behavior is as design, we have to add a describe to
 the manual.

 https://dev.mysql.com/doc/mysql-enterprise-backup/4.0/en/backup-incremental-options.html#o...

 https://dev.mysql.com/doc/mysql-enterprise-backup/4.0/en/bugs.backup.html
 https://dev.mysql.com/doc/mysql-enterprise-backup/4.0/en/backup-capacity-options.html#opti...

 https://dev.mysql.com/doc/mysql-enterprise-backup/4.0/en/meb-files-backed-up-summary.html#...

Also not only 4.0 but also 3.8.

How to repeat:
Taking incremental backup with a combination --start-lsn and
 --incremental-backup-dir

Suggested fix:
Add description about this specification (or limitation) to the manual.

Hello Meiji-San,

Thank you for the report.

Thanks,
Umesh

Posted by developer:
 
Notes have been added to different sections in the MySQL Enterprise Backup 3.12 and 4.0 manuals as proposed.