https://bugs.contribs.org/show_bug.cgi?id=10357
--- Comment #8 from John Crisp <[email protected]> ---
OK,
I'd already done 99.9% of this already, so here is an updated RPM for testing.
yum --enablerepo=reetp,smecontribs install smeserver-automysqlbackup
What really needs testing is that the templates are correctly generated.
These are in
/etc/automysqlbckup
/etc/cron.d/runmysqlbackup
For a config file and a cron entry to be generated it checks for two keys for
each db:
mysql55-mysql status enabled
(is it actually installed and running)
automysqlbackup Mysql55 enabled
(do we want this DB backed up?)
So you can cheat for testing and add a key for the main DB:
(the main DB should already be enabled)
config show mysqld
config set mysql55-mysqld service
config setprop mysql55-mysqld status enabled
config set mysql57-mysqld service
config setprop mysql55-mysqld status enabled
config set mariadb55-mysqld service
config setprop mariadb55-mysqld status enabled
Then check the keys in config show automysqlbackup:
automysqlbackup=webapp
Backup_local_files=
Backupdir=/root/backup/db
DbPassword=asdasdsasadsda
Dbencrypt_password=01234567899876543210
Encrypt=no
Hour=4
Mailcontent=log
Mailto=root
Minute=1
Mymaria=disabled
Mysql53=enabled
Mysql55=disabled
Mysql57=disabled
Update the configs with:
signal-event automysqlbackup-update
I haven't tinkered further, but there is no reason you couldn't add keys for
DBs to exclude/include or whatever. The actual automysqlbackup script has a lot
of other options that I haven't touched on. And it can be run manually too....
If this seems vaguely right I'll commit it to CVS.
--
You are receiving this mail because:
You are the QA Contact for the bug._______________________________________________
Mail for each SME Contribs bug report
To unsubscribe, e-mail [email protected]
Searchable archive at https://lists.contribs.org/mailman/public/contribteam/
