This article is for Zmanda Recovery Manager for MySQL (ZRM)
If the ZRM Server needs to run as a different user than the default mysql user, additional configuration on both the ZRM Server and on the ZRM client is required to support this change. In this example, we will use the following user and group:
mysqldba
dba
Please ensure that ZRM Server 3.7 or greater is installed. If the MySQL host is separate from the ZRM server, ZRM Client 3.7 or greater must also be installed on the client host.
service zmc_zrm stop
/opt/zmanda/zrm/apache2/conf/httpd.conf
User mysql Group mysql
to:
User mysqldba Group dba
root
/usr/bin/mysql-zrm-migrate-file-ownership --user mysqldba --group dba
The following instructions are run on the the ZRM client/MySQL host if it is separate from the ZRM server. If you are running MySQL on the ZRM server itself, use localhost as the host parameter in the Backup|What page. This bypasses fetching through a socket by directly using the cp command to copy data without invoking any xinetd-socket mechanism. For a remote client:
localhost
Backup|What
cp
xinetd-socket
service zmc_zrm start
You might see some messages such as:
Could not find /etc/mysql-zrm Could not find /opt/zmanda/zrm/logs Could not find /opt/zmanda/zrm/apache2/htdocs/zmanda-zrm Could not find /opt/zmanda/zrm/bin Could not find /opt/zmanda/zrm/lib Could not find /opt/zmanda/zrm/tmp Could not find /opt/zmanda/zrm/apache2/logs/fastcgi/ Could not find /opt/zmanda/zrm/php/tmp Could not find /opt/zmanda/zrm/php/data
/etc/xinetd.d/mysql-zrm-socket-server
xinetd
/etc/init.d/xinetd restart