That's what I figured and was wondering.
I used to make backups of a very large and very busy mysql table by connecting, doing a lock, making an lvm snapshot, unlocking and backing up the lvm.
It allowed perfect recovery everytime I tried, and I tested it a few times per day, for the first month, and periodically after that.
At most I'd have to do REPAIR TABLE `blah`, type work; but all in all, it was a safe way to backup since the entire database is consistent (lvm snapshot).
I just wondered if the same could be true for zimbra.
As I'm the only user of my zimbra, it makes no sense for me to go to NE; and I like learning about it and managing my own server since my old job had me accustomed to maintaining the zimbra machines.
But, BES has a retry fail count for which they use IMAP idle; after a certain unknown number of retries to connect, they give up and default to a 15min polling. If I can limit the number of times zimbra shutsdown and for how long, the retries reset and I won't have to keep messing with my mail settings.
I'll probably just do a weekly or monthly full, and just use the REST url to backup my mailbox for the "just in case".
Maybe I'll try restoring from a hot-snapshot on a test box and see what happens. I wonder if stopping the MTA would keep it safe; anything except the imap server (zmmailbox).
My current setup is:
1. Rsync into temp dir
2. Shutdown
3. Rsync again
4. Startup
5. tar and rsync to backup server
I used to have a "cold standby" that was configured with everything (including the IP) that would pull that tar down and extract it, run zmfixperms, and all that; and the eth0 was just disabled, and would do it using eth1. So a ifup eth0, and a zmcontrol start would bring it online. I used it once, worked well.
Anyway.. now I'm rambling
