tmpdir configuration option in mysql-zrm.conf

[D43m0n]

I'm running mysql-zrm 1.1.5

when I specify a different tmpdir on the mysql server to be used for backup, I see strange things happening:

I created a new logical volume and mounted it under /tmp2. In mysql-zrm.conf I specified tmpdir=/tmp2 to be used for temporary storage. When I run the backup (mysql-zrm-scheduler --now --backup-set daily) I get the message:

Logging to /var/log/mysql-zrm/mysql-zrm-scheduler.log
INFO: ZRM for MySQL Community Edition - version 1.1.5
ERROR: /tmp2 does not exist
ERROR: /usr/bin/mysql-zrm did not finish successfully

But it does exist on the remote dabase host... However, when I create a symlink to /tmp on the mysql-zrm server, the backup command succeeds...

That's weird, why would I need to have a same directory name on the mysql-zrm server as on the database server??

Is this a bug?

Thanks in advance

[kkg]

Hi,

This is expected behavior. mysql-zrm also needs to use a tmp directory on the zrm server for two reasons.
a) The ZRM server could also be a mysql server.
b) For some tmp files that it creates while backup happens.

So instead of having to specify two different tmp directories, ZRM uses the same tmpdir for all temporary operation on both the zrm server and remote servers.

--kkg

[D43m0n]

OK,

keeping the configuration as simple and short as possible is also my idea.

Perhaps an idea to mention this somewhere in the documentation (by tomorrow this thread can also be found on Google anyway ;-)