# su – zimbra
# zmcontrol start

Currently, the script (not this tutorial) works perfectly in a Zimbra 6.0 environment. I will post that later on as it contains a few extra steps to get the script running smoothly.

#sudo -u zimbra /opt/zimbra/bin/zmcontrol start

What I have realized is that in the line:

/opt/zimbra/bin/zmlogswatchctl: line 72: zmprov: command not found

It calls the zmprov command, and takes as the user executing it the one that has initiated the session, not the zimbra user (as invoked by “sudo – zimbra”). This only happens in version 6; now, if you have that script for this version, please post it.

Thanks in advance.

This is made to manually enter each command, assuming you would like to use the directories I listed above. While using this as a script, you may have output overflow errors in which you have to parse correctly. If you are simply placing these commands in a script and running the script every morning, you will have issues.

Needless to say, I have a backup script that will work for your purpose and can make another post if that is something you will be interested in.

About the error relating to the logger service not being enabled is confusing. All zimbra services should be halted prior to the backup. Verify you are issuing a
“sudo -u zimbra /opt/zimbra/bin/zmcontrol stop” in your script.

Starting logswatch…/opt/zimbra/bin/zmlogswatchctl: line 72: zmhostname: command not found
/opt/zimbra/bin/zmlogswatchctl: line 72: zmprov: command not found
zimbra logger service is not enabled! failed.

The only way I found is to start manually the logger.