MAIL COMMAND FAILED
This article is for Zmanda Recovery Manager For MySQL (ZRM) Error Message mail command failed Error Description ZRM for MySQL could...
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:
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.
Configuring the ZRM Serverservice zmc_zrm stop
User mysql
Group mysql
to:
User mysqldba
Group dba
/usr/bin/mysql-zrm-migrate-file-ownership --user mysqldba --group dbaConfiguring the ZRM client
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:
service zmc_zrm start
/usr/bin/mysql-zrm-migrate-file-ownership --user mysqldba --group dba
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
User mysql Group mysql
to:
User mysqldba Group dba4. Restart the xinetd service as the root user:
/etc/init.d/xinetd restart
Contact us for a free 30-minute consultation and learn how our fully managed solution can protect your business and streamline your operations. Get started with Zmanda Pro today!
Book a meeting