On Dec.01 MySQL-zrm was updated from 2.2.0-1 to 2.2.0-2.
"/usr/bin/zrm-pre-scheduler --action backup --backup-set dailyrun --backup-level 0 --interval daily"
brings the following error message :
pre-schedule:INFO: ZRM for MySQL Community Edition - version 2.2.0
Logging to /var/log/mysql-zrm/zrm-pre-scheduler.log
--add To add a mysql-zrm schedule entry
--query To query existing mysql-zrm schedule entry
--delete To delete an mysql-zrm schedule entry
Use --start to delete entry with specific start time
--interval <interval> Default: weekly
valid value: daily, weekly or monthly
--start-time <start-time> e.g: 15:30 [start at 3:30pm]
--day-of-week <day> e.g: 0 to start on Sunday, 1-3 to start on Mon, Tue and Wed.
--day-of-month <day> e.g: 1 to start on first day of the month,
10-13 to start on the 10th, 11th, 12th and 13th day of the month.
--backup-level <level> Full(0) or incremental(1)
--backup-set <backupSet name>
--now To start mysql-zrm now
a rebuild from src.rpm without the Patch
and the parameter --action functioned
The Function --action in mysql-zrm-scheduler was not found, and MySQL-backups without funtion.
MySQL-zrm-2.2.0-3.el6 has been submitted as an update for Fedora EPEL 6.
* should fix your issue,
* was pushed to the Fedora EPEL 6 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=epel-testing MySQL-zrm-2.2.0-3.el6'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
MySQL-zrm-2.2.0-3.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.