titleistfour
May 22nd, 2013, 09:23 AM
Hello,
We have been using ZRM 2.2 for some time and really like it. Recently we noticed that ZRM 3.0 (beta) has support mydumper. I wanted to test this out to see if we could enable threading of our backups for better performance. I have a CentOS 6.4 x86_64 server with mydumper 0.2.3 and MySQL-zrm-3.0beta-1.noarch.rpm installed. I've setup my config file for testing like so:
# Daily_myserver01 backup test
comment=MySQL Backup - myserver01
backup-level=0
backup-mode=logical
destination=/backup/mysql/myserver01
retention-policy=35D
compress=1
all-databases=1
user="******"
password="******"
host="myserver01"
routines=1
single-transaction=only-innodb
verbose=1
mailto="[email protected]"
html-reports=backup-status-info
logical-parallel=1
extra-mysqldumper-options="--threads=4"
I run my test backup using "mysql-zrm-backup --backup-set Daily_myserver01"
But I get a mydumper error
Daily_myserver01:backup:INFO: Command used for logical mydumper backup is mydumper --user="******" --password="*****" --host="myserver01" --outputdir /backup/mysql/myserver01/Daily_myserver01/20130522111713 --logfile /tmp/ILWgW9766T --compress --verbose=3
option parsing failed: Unknown option --logfile, try --help
Daily_myserver01:backup:WARNING: Could not read file /tmp/ILWgW9766T
Daily_myserver01:backup:ERROR: mydumper failed
It looks like mydumper doesn't support the --logfile option, at least not the version I have, which I installed from the REMI repository. Seems ZRM is expecting it to support that option though. Should I be using a different version or am I missing configuration options?
Thanks for any help!
Jay
We have been using ZRM 2.2 for some time and really like it. Recently we noticed that ZRM 3.0 (beta) has support mydumper. I wanted to test this out to see if we could enable threading of our backups for better performance. I have a CentOS 6.4 x86_64 server with mydumper 0.2.3 and MySQL-zrm-3.0beta-1.noarch.rpm installed. I've setup my config file for testing like so:
# Daily_myserver01 backup test
comment=MySQL Backup - myserver01
backup-level=0
backup-mode=logical
destination=/backup/mysql/myserver01
retention-policy=35D
compress=1
all-databases=1
user="******"
password="******"
host="myserver01"
routines=1
single-transaction=only-innodb
verbose=1
mailto="[email protected]"
html-reports=backup-status-info
logical-parallel=1
extra-mysqldumper-options="--threads=4"
I run my test backup using "mysql-zrm-backup --backup-set Daily_myserver01"
But I get a mydumper error
Daily_myserver01:backup:INFO: Command used for logical mydumper backup is mydumper --user="******" --password="*****" --host="myserver01" --outputdir /backup/mysql/myserver01/Daily_myserver01/20130522111713 --logfile /tmp/ILWgW9766T --compress --verbose=3
option parsing failed: Unknown option --logfile, try --help
Daily_myserver01:backup:WARNING: Could not read file /tmp/ILWgW9766T
Daily_myserver01:backup:ERROR: mydumper failed
It looks like mydumper doesn't support the --logfile option, at least not the version I have, which I installed from the REMI repository. Seems ZRM is expecting it to support that option though. Should I be using a different version or am I missing configuration options?
Thanks for any help!
Jay