Silenus
July 8th, 2014, 12:19 PM
Hi,
I'm testing out ZRM for backup and recovery of our MySQL database, and I would like to use the pre-scheduler-plugin to delay a backup if one of the 2 applications that write data to the database is running.
When I tried to schedule a backup with a pre-scheduler-plugin defined per the sample/default mysql-zrm.conf file, I get the following error:
-bash-4.1$ mysql-zrm-scheduler --add --interval daily --backup-set test --start 14:25
schedule:INFO: ZRM for MySQL Community Edition - version 3.0
schedule:WARNING: Unknown parameter pre-scheduler-plugin="/usr/share/mysql-zrm/plugins/pre-scheduler.pl" in /etc/mysql-zrm/mysql-zrm.conf. Assuming this is a custom parameter meant for one of the plugins
Logging to /var/log/mysql-zrm/mysql-zrm-scheduler.log
DONE
Digging a little deeper, I found that the zrm-pre-scheduler was trying to parse out "pre-scheduler" instead of "pre-scheduler-plugin". Changing the config variable pre-scheduler-plugin to pre-scheduler in the mysql-zrm.conf resolved this
Just something others might want to be aware of.
I'm testing out ZRM for backup and recovery of our MySQL database, and I would like to use the pre-scheduler-plugin to delay a backup if one of the 2 applications that write data to the database is running.
When I tried to schedule a backup with a pre-scheduler-plugin defined per the sample/default mysql-zrm.conf file, I get the following error:
-bash-4.1$ mysql-zrm-scheduler --add --interval daily --backup-set test --start 14:25
schedule:INFO: ZRM for MySQL Community Edition - version 3.0
schedule:WARNING: Unknown parameter pre-scheduler-plugin="/usr/share/mysql-zrm/plugins/pre-scheduler.pl" in /etc/mysql-zrm/mysql-zrm.conf. Assuming this is a custom parameter meant for one of the plugins
Logging to /var/log/mysql-zrm/mysql-zrm-scheduler.log
DONE
Digging a little deeper, I found that the zrm-pre-scheduler was trying to parse out "pre-scheduler" instead of "pre-scheduler-plugin". Changing the config variable pre-scheduler-plugin to pre-scheduler in the mysql-zrm.conf resolved this
Just something others might want to be aware of.