Hi folks,
on my Debian-Servers i got ZIMBRA successfull working with heartbeat on a DRBD netraid !
Short description (how i did it): FOR TESTING ONLY !!!!
==============================================
I ASSUME, that you have a proper running installation of heartbeat & DRBD !!
1. Make 2 (!) installations of Zimbra with exactly the same parameters, on 2 different server, of course.
2. Define one server as Master (for yourself and later for heartbeat), and configure this one to your ZIMBRA-requirements.
3. Test your Master-Zimbra-Server if everything is fine, up & running
4. Remove on BOTH NODES ALL Zimbra auto-start-scripts, like
Code:
rm /etc/rc2.d/S99zimbra
rm /etc/rc3.d/S99zimbra
rm /etc/rc4.d/S99zimbra
rm /etc/rc5.d/S99zimbra
5. STOP ALL Zimbra services:
Code:
/etc/init.d/zimbra stop
6. MOVE /opt to somewhere else, e.g /opt_save, and create /opt again:
Code:
# mv /opt /opt_save
# mkdir /opt
7. Get the DRBD working on /opt as a netraid. I don't know if it will work with symlinks, so i decided to mount /opt directly with DRBD. Don't forget /etc/fstab
8. Now you have to reboot BOTH nodes, to be sure that you have a proper DRBD netraid running on /opt !!!
Check also if heartbeat is running as well and mounts /opt properly if your Master is dead !!
9. If everythings is working fine, then it's time to copy Zimbra back to production state:
Code:
mv /opt_save/zimbra /opt/
10. Edit /etc/ha.d/haresources on BOTH NODES and ADD 'zimbra' at the end of the line where you a controlling, what heartbeat should start & stop.
Code:
# nano /etc/ha.d/haresources
zimbra-01 drbddisk::netraid1 Filesystem::/dev/drbd0::/opt::ext3 YOUR_MASTER_IP zimbra
11. REBOOT both Nodes, and Zimbra should now start on the master. If the master dies, the 2nd node will takeover completly
BEWARE: ==> THIS WAS DONE JUST FOR TESTING PURPOSES !!!
==> EXACTLY ANALYSIS of Zimbra's behaviour is PENDING !!!
I hope it'll work in a production enviroment, i will test it this week with nearly 60GB email, so we will see....
/harry