Bug #59928 The ---comments option is not recognized in mysqlbackup command line syntax
Submitted: 3 Feb 2011 22:06 Modified: 5 Mar 2011 12:42
Reporter: Hema Sridharan Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Enterprise Backup Severity:S3 (Non-critical)
Version:MEB 3.6 OS:Linux
Assigned to: CPU Architecture:Any

[3 Feb 2011 22:06] Hema Sridharan 
Description:
Execute MEB by giving --comments option
The backup will fail giving error as 
mysqlbackup: unknown variable 'comments='

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

As per design of new mysqlbackup command line syntax, we have --comments option newly added to 3.6 version.

How to repeat:
$MYSQLBACKUP --port=13000 --protocol=tcp --user=root --backup-dir=/export/home2/tmp/mysql-5.1-meb-testing/mysql-test/var/tmp/meb_bup_dir --comments="TESTING MYSQL BACKUP" backup

the above command results in an error as
mysqlbackup: unknown variable 'comments=TESTING MYSQL BACKUP'

Suggested fix:
--comments option should be recognized.
[3 Feb 2011 22:17] Hema Sridharan 
Also the --comments-file option which is newly introduced in MEB 3.6 version is also not recognized and issues an error message as
"mysqlbackup: unknown variable 'comments-file=/export/home2/tmp/mysql-5.1-meb-testing/mysql-test/comment.txt'" 

Both --comments and --comments-file option should be recognized as stated in design.
[5 Feb 2011 12:42] Sveta Smirnova 
Thank you for the report.

I can not repeat described behavior. Please check if problem is repeatable in your environment with revision:

revno: 279
committer: Thava Alagu <thavamuni.alagu@sun.com>
branch nick: single-bin
timestamp: Sat 2011-02-05 01:58:19 +0530
message:
  WL#5497 Support for single backup image.
  
  This patch adds support for backup-dir-to-image command.
[6 Mar 2011 0:00] Bugs System 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".