Bug #59911 Invalid values of start_lsn option when performing incremental backup passes
Submitted: 3 Feb 2011 0:27 Modified: 4 Feb 2011 9:32
Reporter: Hema Sridharan Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Enterprise Backup Severity:S3 (Non-critical)
Version:MEB 3.6 OS:Linux
Assigned to: Thava Alagu CPU Architecture:Any

[3 Feb 2011 0:27] Hema Sridharan 
Description:
- Execute backup
- Note down the highest modified page lsn number from the backup logs
- This number should be used to perform incremental backup by specifying --incremental --start-lsn options.
- But incremental backup passes even if invalid value is specified in --start-lsn option. This value can be negative number, letters, decimals, fractions.

Use the latest MEB 3.6 version from bzrroot/meb/sbin-repo/single-bin

How to repeat:
Use any invalid value in --start-lsn option when performing incremental backup like abdcfhg, -987677, 5.78839, junkdata, 'aaaaaaaaaaaabbbbbbbbbbbbbbbbbbbbbbbb'

The backup will pass. Instead it should issue an error message for invalid values.

Test case will be provided if required.
[4 Feb 2011 9:32] Thava Alagu 
Closing the bug since the fix has been checked into the prototype repository.