Quote:
Originally Posted by jholder  Code: # Live sync before stopping Zimbra to minimize sync time with the services down
# Comment out the following line if you want to try single cold-sync only
rsync -avHK /opt/zimbra/ /backup/zimbra We generally do not recommend "live" syncing of the Zimbra server.
Such an action could result in a loss of data, and may be your current issue. |
This is not a true "live" sync, and if anyone were to use only this portion of the script they would wind up with an ugly mess on their hands. I put this in the script (at the recommendation of another user) to minimize the amount of time that the server is down. The "live" rsync alone would, as you point out, contain some in-process files that we DON'T want to use as backups, but by pre-syncing the whole /opt/zimbra directory BEFORE stopping the Zimbra services, those files that do not change between the started and stopped states get updated. Then, with Zimbra services stopped, a second rsync cleans up those elements that are open during running services, which is why the resultant backup is truly a "cold" backup.
It is, of course, possible to comment out that "live" presync and run the script with the "cold" sync only, if you prefer.
I wonder, though about your suggestion that this would be what keeps frankb's Tomcat from restarting; it seems to me that the two things should be completely unrelated. Frankb, I'm curious; if you comment out all the backup lines and just use the zimbra stop and zimbra start lines, does Tomcat still fail to restart? For that matter, try the following:
Log on as root
su - zimbra
zmcontrol stop
(now wait half a minute or so)
zmcontrol start
Do your processes, including Tomcat, start properly? It may be that the issue is not the script at all. . .at least that's where I would start looking.
Cheers,
Dan