- ZIMBRA CANNOT CONNECT TO THE ZCS UPSTREAM SERVER HOW TO
- ZIMBRA CANNOT CONNECT TO THE ZCS UPSTREAM SERVER INSTALL
- ZIMBRA CANNOT CONNECT TO THE ZCS UPSTREAM SERVER MANUAL
ResourceManager(default): 8_03:28:26 info: Releasing resource group: master IPaddr::192.168.1.50/24/eth4 drbddisk::r0 Filesystem::/dev/drbd0::/opt::ext3 zimbra Jun 08 03:28:26 master heartbeat: : info: Giving up all HA resources. Jun 08 03:28:26 master heartbeat: : info: Heartbeat shutdown in progress. Jun 08 03:18:40 master heartbeat: : info: Link master:eth4 up. Jun 08 03:18:40 master heartbeat: : info: Local status now set to: ‘up’ Jun 08 03:18:39 master heartbeat: : info: G_main_add_SignalHandler: Added signal handler for signal 17
ZIMBRA CANNOT CONNECT TO THE ZCS UPSTREAM SERVER MANUAL
Jun 08 03:18:39 master heartbeat: : info: G_main_add_TriggerHandler: Added signal manual handler Jun 08 03:18:39 master heartbeat: : info: glib: UDP Broadcast heartbeat closed on port 694 interface eth4 – Status: 1
Jun 08 03:18:39 master heartbeat: : info: glib: UDP Broadcast heartbeat started on port 694 (694) interface eth4 Jun 08 03:18:39 master heartbeat: : info: heartbeat: version 3.0.4 Jun 08 03:18:39 master heartbeat: : info: Configuration validated. Jun 08 03:18:39 master heartbeat: : WARN: Logging daemon is disabled –enabling logging daemon is recommended Jun 08 03:18:39 master heartbeat: : info: Pacemaker support: false Hooray, finally you could build Zimbra HA with DRBD+Heartbeatįor log information about HA process, you can see at /var/log/ha-log Please start again service Heartbeat on node1 or power on machineĪll running services on node2 will automatically stopped and taken over by node1 How long node2 can start all services worked again, depends how long start services (named and zimbra)
# Start service Heartbeat on node1 and then node2Īfter Zimbra running well on node1, please stop service Heartbeat on node1 or force off machineĪll services that taken over by Heartbeat will automatically stopped and taken over by node2. # Stop service Heartbeat on node2 and then node1 # Configure file /etc/ha.d/haresources on all nodes (node1 and node2) # Configure /etc/hosts and dns records on all nodes (node1 and node2)Ĭhange IP address of mail so that refers into IP 192.168.80.93. # Move folder /opt existing to another folder, do the following command on all nodes (node1 and node2) # Umount DRBD devices after rsync file/folder Zimbra at node1 For the tricks, use cp for copy data.mdb to DRBD devices ?Ĭp /opt/zimbra/data/ldap/mdb/db/data.mdb /mnt/tmp/zimbra/data/ldap/mdb/db/data.mdbĬhown zimbra.zimbra /mnt/tmp/zimbra/data/ldap/mdb/db/data.mdb
Rsync -avP -exclude=data.mdb /opt/ /mnt/tmpĭata.mdb will be huge if copied by rsync so that take a long time. # After DRBD has been worked, copy file/folder /opt/zimbra into DRBD devices. # Testing data replication DRBD that has been worked : Testing Data Replication/Synchronize on DRBD
ZIMBRA CANNOT CONNECT TO THE ZCS UPSTREAM SERVER HOW TO
# After installed Heartbeat and online failover/failback working fine, then install DRBD for data replication on all nodes (node1 and node2) as described at this link : How To Configure Data Replication/Synchronize on CentOS 6 Using DRBD
ZIMBRA CANNOT CONNECT TO THE ZCS UPSTREAM SERVER INSTALL
# After installed Zimbra, install and configure Heartbeat on all nodes (node1 and node2) as described at this link : How To Configure Online Failover/Failback on CentOS 6 Using Heartbeat # Stop Zimbra and DNS services on all nodes (node1 and node2) – Set IP address of each nodes refers into include DNS and /etc/hosts – Please change name of each nodes refers into when installing Zimbra # install Zimbra on CentOS 6 on all nodes (node1 and node2) as described at this link : How To Install Zimbra 8.6 on CentOS 6. This alias IP will be configured online failover Alias IP will be used for access clients/users.