Bug #57260 | Using both --incremental and --backup-and-apply-log should not be allowed | ||
---|---|---|---|
Submitted: | 5 Oct 2010 19:32 | Modified: | 28 Jan 2011 18:18 |
Reporter: | Victor Kirkebo | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Enterprise Backup | Severity: | S3 (Non-critical) |
Version: | 3.5 | OS: | Any |
Assigned to: | Ritheesh Vedire | CPU Architecture: | Any |
[5 Oct 2010 19:32]
Victor Kirkebo
[15 Oct 2010 4:30]
Ritheesh Vedire
Assigning Thava as a reviewer and I think one review is sufficient.
[15 Oct 2010 7:43]
Thava Alagu
The patch looks good and OK to push.
[15 Oct 2010 8:02]
Ritheesh Vedire
Pushed to meb-3.5-next branch; revid: revision-id: ritheesh.vedire@sun.com-20101015075823-dfy44p9d57pqzsfh
[2 Dec 2010 0:00]
John Russell
If there is some new restriction or a restriction lifted by this patch, please supply the details to better judge if something needs to be mentioned in the doc.
[2 Dec 2010 14:56]
Ritheesh Vedire
--backup-and-apply-log takes the full backup and does --apply-log on that backup implicitly. mysqlbackup has all the resources to do a apply-log on the full backup. However, with --backup-and-apply-log, the resources to apply-log for incremental backup is not available for mysqlbackup (ex:INCREMENTAL_BACKUP.CNF). So, --incremental (for incremental backup) should not be allowed for --backup-and-apply-log. We can have a note in the documentation, that --backup-and-apply-log is only for full backup.