You are on page 1of 20

VMware Zimbra Collaboration Server

Cluster Installation
Single-Node Configuration

Network Edition 7.1

March 2011
Legal Notices
Copyright ©2005-2011 VMware, Inc. All rights reserved. This product is protected by U.S. and
international copyright and intellectual property laws. VMware products are covered by one or more
patents listed at http://www.vmware.com/go/patents.
VMware and Zimbra are registered trademarks or trademarks of VMware, Inc. in the United states and/
or other jurisdiction. All other marks and names mentioned herein may be trademarks of their respective
companies.
VMware, Inc.
3401 Hillview Avenue
Palo Alto , California 94304 USA
www.zimbra.com
ZCS 7.1
March 2011
ZCS Cluster Installation- Single-Node Configuration Guide

This guide describes configuring one active node and one standby node in a
single-node cluster environment.
Topics in this chapter include:
Pre-configuration Requirements
Cluster Installation Overview
Preparing the SAN
Downloading the ZCS Software
Installing and Configuring Active Node Cluster Services
Installing the ZCS Cluster on the Standby Node
Preparing Red Hat Cluster Suite for ZCS
Configuring Red Hat Cluster for ZCS
Start the Red Hat Cluster Suite Daemons
Testing the Cluster Set up
Configuring ZCS in VCS
View Zimbra Cluster Status
Before you install your cluster enviornment, also read the following guides:
 Red Hat Installation Modifications for ZCS guide about preparing the Red
Hat Enterprise Linux operating system for ZCS
 Network Edition of ZCS 7.1 Quick Start Installation Guide about ZCS single
server installation and determine the system requirements
To get the latest copy of the documentation, go to http://www.zimbra.com/
support/documentation.html.
For cluster integration to provide high availability, VMware Zimbra
Collaboration Server (ZCS) 7.1 can integrate with the following:
 Red Hat® Cluster Suite running on Red Hat Enterprise Linux® AS or ES
• Release 4, Update 5
• Release 5, Update 3
In the single-node cluster implementation, all Zimbra servers are part of a
cluster under the control of the Red Hat Cluster Manager.

Note: Red Hat Cluster Suite consists of Red Hat Cluster Manager and
Linux Virtual Server Cluster. For ZCS, only Red Hat Cluster
Manager is used. In this guide, Red Hat Cluster Suite refers only to
Cluster Manager.

 Veritas™ Cluster Server by Symantec (VCS) version 5.0 with maintenance


pack 1 or later.

VMware Zimbra Collaboration Server Network Edition 7.1 9


ZCS Cluster Installation- Single-Node Configuration Guide

Note: This guide does not explain how to use the cluster management
software. Before setting up the ZCS cluster enviornment, you should
know the concepts and terminology of the software you are using to
manage high availability.

Pre-configuration Requirements
Both active and standby servers must meet the requirements described in the
ZCS Quick Start Installation Guide, in addition to the requirements described
here.

ZCS Server Requirements


For ZCS clustering, the server operating system must be either Red Hat
Enterprise Linux AS/ES
 Release 4, Update 5
 Release 5, Update 3
The operating system must be configured as described in the Red Hat
Installation Modifications for ZCS guide before you begin.

Hardware for the Cluster Environment


The following hardware is required.
 SAN (shared disk storage device) with partitions to store the data for each
of the Zimbra servers. The size of the shared storage device depends on
your expected site capacity.
 If using Red Hat Cluster Manager, a network power control switch to
connect cluster nodes is required. The power control switch is used as the
fence device for I/O fencing during a failover.

Cluster Managers For Clustering


One of the following cluster management tools must be installed on every
server.
 Red Hat Enterprise Linux Cluster Suite for the Red Hat Enterprise Linux
software you are running.
If you are using Red Hat Cluster Manager, go to the Red Hat Cluster Suite
website for specific system requirements for cluster configurations using
Red Hat Cluster Suite. If you are not familiar with the Red Hat Cluster
Suite, read the documentation to understand how each of the components
works to provide high availability.
 Veritas Cluster Server by Symantec (VCS) version 5.0 with maintenance
pack 1 or later.

10 Network Edition 7.1 VMware Zimbra Collaboration Server


ZCS Cluster Installation- Single-Node Configuration Guide

If you are using Veritas Cluster Server, go to the Symantec website for
specific system requirements for cluster configurations. If you are not
familiar with Veritas Cluster Server, read the Veritas Cluster Server User’s
Guide.

Cluster Installation Overview


Cluster integration requires planning the cluster design and precisely
executing the configuration. The Zimbra Cluster software automates the setup
on the nodes. The scripts in the ZCS software configure the servers cluster
integration.
Red Hat Cluster Manager. In many cases, you may not need to use Red
Hat’s graphical Cluster Configuration Tool to configure the Zimbra cluster. If
you do, refer to the Red Hat Cluster Suite documentation for detailed
configuration and management instructions.
Veritas Cluster Server. Configure VCS to manage the ZCS servers. See
Configuring ZCS in VCS on page 24 for information about configuring ZCS.

Flow of Cluster Installation


The ZCS cluster install process starts with the Active node. On the Active
node this process does the following:
 Installs the necessary files, defines users and groups, and creates the
mount points for the clustered service
 Installs ZCS
 Mounts the SAN volume(s)
 If using Red Hat Cluster Manager, the following is also done:
• Runs the cluster postinstall.pl program
• Runs the cluster configurator script to prepare the Red Hat Cluster Suite
• February 2010Copies the cluster config. file to the standby node
• Starts Red Hat Cluster Suite daemons
 If using Veritas Cluster Server, after the SAN volume(s) are mounted, use
the VCS configuration interface to configure ZCS. See Configuring ZCS in
VCS on page 24.
On the Standby node, this process does the following:
• Installs the necessary files, defines users and groups, and creates the
mount points for the clustered service
• Installs the necessary cluster files, define users and groups, and installs
the ZCS software
• If using Red Hat Cluster Manager, starts Red Hat Cluster Suite
daemons on the standby node

VMware Zimbra Collaboration Server Network Edition 7.1 11


ZCS Cluster Installation- Single-Node Configuration Guide

Cluster Screen Shot Example Scenario


The screen shots in this guide describe configuring a cluster enviornment with
one active node and one standby node. The naming conventions used in the
screen shots are as follows
 Active node: node1.example.com
 Standby node: node2.example.com
 Cluster service hostname: cluster.example.com
 Mount label: cluster01

Preparing the SAN

Note: You can place all service data on a single volume or choose to place
the service data in multiple volumes.

Configure the SAN device and create the partitions for the volumes. Refer to
the cluster software documentation for configuration requirements.
 If you select to configure the SAN in one volume with subdirectories, all
service data goes under a single SAN volume.
 If you select to partition the SAN into multiple volumes, the SAN device is
partitioned to provide the multiple volumes for each Zimbra mailbox server
in the cluster. Example of the type of volumes that can be created follows.

 conf Volume for the service-specific configuration files


 log Volume for the local logs for Zimbra mailbox
server
 redolog Volume for the redo logs for the Zimbra mailbox
server
 db/data Volume for the MySQL data files for the data
store
 store Volume for the message files
 index Volume for the search index files
 backup Volume for the backup files
 logger/db/data Volume for the MySQL data files for logger
service’s MySQL instance
 data/ldap Volume for OpenLDAP data
 postfix/spool Volume for Postfixspool

Downloading the ZCS Software


For the latest Zimbra software, go to www.zimbra.com/downloads/. Download
and save the ZCS network edition to the computer from which you will install
the software.

12 Network Edition 7.1 VMware Zimbra Collaboration Server


ZCS Cluster Installation- Single-Node Configuration Guide

Installing and Configuring Active Node Cluster Services


Log in as root to the Zimbra mailbox server and cd to the directory where the
ZCS software file is saved and unpack the ZCS tar file.

1. Bring up the cluster service IP address on the active node.


[root@node1 ~]# ip addr add xx.xx.xxx.xx dev eth0

2. Unpack the ZCS .tgz file


tar xzvf <zcsname.tgz>

3. Change directories to the unpacked file and type the following command to
begin the cluster install.
./install.sh --cluster active

4. The node requires Zimbra and Postfix users and groups. Type the Zimbra
group ID and Zimbra user ID to be used. The same user and group IDs
must be used on both active and standby nodes.
a. Type the Zimbra group ID (GID) to be used. The default is 500.
b. Type the Postfix group ID. The default is 501.
c. Type the Postdrop group ID. The default is 502.
d. Type the Zimbra user ID (UID) to be used. The default is 500.
e. Type the Postfix user ID. The default is 501.
The root directory for the mount points is created.

VMware Zimbra Collaboration Server Network Edition 7.1 13


ZCS Cluster Installation- Single-Node Configuration Guide

Each Zimbra cluster node needs zimbra and postfix users and groups.
The same user and group IDs must be used on all nodes. If not,
some nodes will not be able to access files on SAN owned by these
users/groups.

Enter zimbra group ID: [500]


... groupadd -g 500 zimbra
groupadd: group zimbra exists

Enter postfix group ID: [501]


... groupadd -g 501 postfix
groupadd: group postfix exists

Enter postdrop group ID: [502]


... groupadd -g 502 postdrop
groupadd: group postdrop exists

Enter zimbra user ID: [500]


... useradd -u 500 -g zimbra -G postfix,tty -d /opt/zimbra -s /bin/
bash zimbra useradd: user zimbra exists
... chown root:root /opt/zimbra

Enter postfix user ID: [501]


... useradd -u 501 -g postfix -d /opt/zimbra/postfix -s /bin/bash
postfix useradd: user postfix exists
... chown root:root /opt/zimbra/postfix
chown: cannot access `/opt/zimbra/postfix': No such file or
directory

Creating root directory for mount points


... mkdir -p /opt/zimbra-cluster/mountpoints

5. On the active node, create mount points for the cluster services. Enter one
service name per prompt. If you are installing on one volume as in this
example, you create only one mount point.
• Type the cluster service hostname, press Enter.
• Type done, when all mount points are created.

14 Network Edition 7.1 VMware Zimbra Collaboration Server


ZCS Cluster Installation- Single-Node Configuration Guide

On every mailbox server node you need to create mount points for all
cluster services. Enter one service name per prompt.

Enter cluster service name ("done") to finish: cluster.example.com


... mkdir -p /opt/zimbra-cluster/mountpoints/cluster.example.com
... mkdir -p /opt/zimbra-cluster/mountpoints/cluster.example.com/conf
... mkdir -p /opt/zimbra-cluster/mountpoints/cluster.example.com/log
... mkdir -p /opt/zimbra-cluster/mountpoints/cluster.example.com/
redolog
... mkdir -p /opt/zimbra-cluster/mountpoints/cluster.example.com/db/
data
... mkdir -p /opt/zimbra-cluster/mountpoints/cluster.example.com/store
... mkdir -p /opt/zimbra-cluster/mountpoints/cluster.example.com/index
... mkdir -p /opt/zimbra-cluster/mountpoints/cluster.example.com/backup
... mkdir -p /opt/zimbra-cluster/mountpoints/cluster.example.com/
logger/db/data
... mkdir -p /opt/zimbra-cluster/mountpoints/cluster.example.com/data/
ldap
... mkdir -p /opt/zimbra-cluster/mountpoints/cluster.example.com/
postfix/spool

Enter cluster service name ("done") to finish: done

Mount points were created for the following cluster services:

cluster.example.com

6. Enter the cluster service hostname that will be active on this node. This is
the same as the public host name. This is not the same as the node
hostname.

Enter the active cluster service name for this node:


[node1.example.com]cluster.example.com

7. Mount the SAN volume (s). You can mount one volume for all services or
you can mount separate volumes. The following command is to mount one
volume for all services . To mount by label, as root type:

mount -v LABEL=<labelname> /opt/zimbra-cluster/mountpoints/


<clusterservicehostname.com>

Please mount all the SAN volumes and rerun install.sh -


cluster active.
[root@node1 zcs-NETWORK 5.0.0_RC2_1703.RHEL4_
64.20071105125148]# mount -v LABEL=cluster01 ./opt/zimbra-
cluster/mountpoints/cluster.example.com

Now you rerun install.sh cluster active to install the ZCS software.

VMware Zimbra Collaboration Server Network Edition 7.1 15


ZCS Cluster Installation- Single-Node Configuration Guide

Installing ZCS
Refer to the Installing Zimbra Software section of the Zimbra Collaboration
Server 7.1 Single Server Installation Guide, Network Edition, for complete
ZCS installation instructions. Make the following changes to those
installation instructions:

1. Instead of step 1, to start the ZCS installation, type:


./install.sh --cluster active -l /<director>/ZCSLicense.xml

Note: Adding -l /<director>/ZCSLicense.xml to the command line, installs the


Zimbra License.

2. For step 5, select the Zimbra packages to install, including the Zimbra-
Cluster package, which is marked Y.

3. When the DNS error to resolve MX displays, enter Yes to change the
domain name. Modify the domain name to the cluster service hostname
(not the active node name).

4. Review the Common Configuration menu to verify that the host name and
LDAP master host name have been changed to the cluster service
hostname. When the ZCS installation is complete, there should be no
reference to the active node name.
When Configuration Complete - press return to exit displays, the cluster install
on the active node is complete.
Now you install the standby node.

Installing the ZCS Cluster on the Standby Node


For the standby node, you define the same group ID and user ID and identify
the cluster services names. The ZCS software is installed but not configured
on the standby node.
1. Bring up the service IP address on the active node.
[root@node1 ~]# ip addr add xx.xx.xxx.xx dev eth0

2. Unpack the ZCS .tgz file


tar xzvf <zcsname.tgz>

3. Change directories to the unpacked file and type the following command to
begin the cluster install.
./install.sh --cluster standby

4. Type the Zimbra group ID (GID) and Zimbra user ID (UID) to be used. The
same user and group IDs must be used on both nodes.
a. Type the Zimbra group ID (GID) to be used. The default is 500.

16 Network Edition 7.1 VMware Zimbra Collaboration Server


ZCS Cluster Installation- Single-Node Configuration Guide

b. Type the Postfix group ID. The default is 501.


c. Type the Postdrop group ID. The default is 502.
d. Type the Zimbra user ID (UID) to be used. The default is 500.
e. Type the Postfix user ID. The default is 501.

5. To create mount points for the cluster services on the standby node, type
the active node cluster service hostname. Press Enter. Mount point(s) are
created for the cluster. These are the same service names as on the active
host.
6. Type done, to finish the mount point configuration.

7. The ZCS install automatically starts to install the ZCS software packages.
Select the same Zimbra packages as installed on the active host. There are
no modifications necessary to installing the packages.
The Zimbra processes are stopped, various cluster-specific adjustments
are made to the ZCS installation and unnecessary data files are deleted.
After the software installation is complete, you are asked to enter the active
cluster service name for this standby node. This creates the symlink /opt/
zimbra.

Software Installation complete!

Operations logged to /tmp/install.log.730

Generating ssh keys for cluster standby node...done.


Installing ssh key into authorized_keys...done.

Enter the active cluster service name for this node:


[cluster.example.com]

[root@node2 zcs-NETWORK-5.0.2_1703.RHEL4_64.20071105125148]#

Preparing Red Hat Cluster Suite for ZCS


If you are using the Red Hat Cluster Suite, after the active and standby nodes
have ZCS and cluster installed, the ZCS Cluster Configurator script is run on
the active node to prepare Red Hat Cluster Suite to run ZCS. The cluster
configurator script is run only on the active mailbox node.
The cluster configurator asks a series of questions to gather information about
the cluster and generate the cluster configuration file, /etc/cluster/cluster.conf.
This is the main configuration file of Red Hat Cluster Suite.
The cluster configurator installs the generated configuration file on the active
cluster node as /etc/cluster/cluster.conf.
The ZCS Cluster Configurator configures the following:

VMware Zimbra Collaboration Server Network Edition 7.1 17


ZCS Cluster Installation- Single-Node Configuration Guide

 Fence Device. This is the network power switch. The active node is plugged
into the fence device. The cluster uses the fence device for I/O fencing
during failover.
 Cluster Nodes. The active node is added as a member to the cluster and
the fence device setting is configured for the active node.
 Managed Resources. The preferred node for each service and the list of
volumes to be mounted from the SAN are configured.

ZCS Cluster Configurator steps

1. When ZCS installation is complete on both the active and standby nodes,
on the active node, change directories to the directory where the ZCS .tgz
file was unpacked and start the configure-cluster.pl. Type
./bin/configure-cluster.pl
Press Enter to continue.
The configurator checks to verify that the server installation is correct.

[root@node1 bin]# bin/configure-cluster.pl

Zimbra Collaboration Suite Cluster Configurator

This script will guide you through creating an initial


configuration file for Red Hat Cluster Suite. A series of
questions will be asked to collect the necessary
information. At the end, the configuration data will be
saved to a file and the file will be copied to all cluster
nodes, as /etc/cluster/cluster.conf on each node.

---------------------------------------------------------

Each Zimbra cluster on the network must have a unique name.


Enter the cluster name:cluster.example.com

2. Each Zimbra cluster on the network must have a unique name to avoid
interfering with another Red Hat Cluster Suite cluster. Enter a name to
identify this cluster. The maximum number of characters for this name is
16. Press Enter.

3. Select the network power switch type that is used as the fence device. For
ZCS configuration, you must select either APC or WTI as the network
power switch device, even if this is not the device you are using. After the
cluster configuration is complete, you can change the generated
configuration file from the Red Hat Cluster Manager Console system-
config-cluster GUI tool.
a. Enter the number the corresponds to the fence device vendor:
• 1 for APC
• 2 for WTI
b. Enter the fence device hostname/IP address, login, and password

18 Network Edition 7.1 VMware Zimbra Collaboration Server


ZCS Cluster Installation- Single-Node Configuration Guide

Choose fence device vendor:


1) APC
2) WTI
Choose from above (1-2): 1
Enter fence device hostname/IP address: apce- -- build-apc
Enter fence device login [apc]:xx
Enter fence device password: apc

4. Enter the active node’s fully-qualified hostname and the plug number of the
fence device associated with the node’s power cord. When the node is
identified, type Done.

For each cluster node you must provide its fully-qualified


hostname and the plug number on the fence device.

Enter node hostname ("done" if no more): node1.example.com


Enter fence device plug number for node1.example.com: 1

Enter node hostname ("done" if no more): node2.example.com


Enter fence device plug number for node2.example.com: 2

Enter node hostname ("done" if no more): done

5. For each service, you need to choose a preferred node to run on and enter
the list of volumes to be mounted from the SAN. In a single server cluster
configuration, only one service is available.
Select the cluster service. Select 1.
Type Done when complete.

VMware Zimbra Collaboration Server Network Edition 7.1 19


ZCS Cluster Installation- Single-Node Configuration Guide

For each service you need to choose a preferred node to run


on, and enter the list of volumes to be mounted from the
SAN.

Choose a service:
1) cluster.example.com
2) Done
Choose from above (1-2): 1

Choose preferred node on which to run service


cluster.example.com:
1) node1.example.com
2) node2.example.com
Choose from above (1-2): 1

A Zimbra cluster service must mount service-specific data


volumes. Two choices are provided in this configuration
process. All service data can be placed on a single volume,
or multiple volumes can be used for different types of data
files. In the multiple-volumes case eight volumes are used
per service.

6. A Zimbra cluster service must mount service-specific data volumes.


Choose the volume setup type.
• 1) Single volume. All service data can be placed on a single volume.
• 2) Multiple volumes. Different types of data files are placed on multiple
volumes.

Choose volume setup type:


1) single volume
2) multiple volumes
Choose from above (1-2): 1

7. Enter the cluster mount label defined for the active node.

Volume cluster.example.com-vol:
mount point = /opt/zimbra-cluster/mountpoints/
cluster.example.com
Enter device name (e.g. /dev/sda5, LABEL=mylabel):
A value must be entered!

Enter device name (e.g. /dev/sda5, LABEL=mylabel):


LABEL=cluster01

8. When Choose a service..., displays, select 2 (Done). The configuration is


complete.

20 Network Edition 7.1 VMware Zimbra Collaboration Server


ZCS Cluster Installation- Single-Node Configuration Guide

Choose a service:
1) cluster.example.com
2) Done
Choose from above (1-2): 2

9. Press Enter to view a summary of the cluster configuration.


After viewing the summary, save the configuration to a file. You can either
accept the default name or rename the configuration file.

Finished collecting information.


Press Enter to view summary of the configuration.

Configuration Summary
--------------------

Cluster Name: cluster.example.com

Fence Device:
name: fence-device
agent: fence_apc
ipaddr: apce- -- -- -- -build-apc
login: apc
passwd: apc

Nodes:
node1.example.com - fence port 1
node2.example.com - fence port 2

Services:
cluster.example.com
ipaddr: 10.10.141.200
preferred node: node1.example.com
volumes:
cluster.example.com-vol
mountpoint: /opt/zimbra-cluster/mountpoints/
cluster.example.com
device: LABEL=cluster01

-----------------------------------------------------------

About to save configuration file.


Enter filename [/tmp/cluster.conf.29843]:

------------------------------------------------------------
cluster.conf to all nodes.

Press Enter to continue.

10. The configuration file must be copied to the standby node. The ZCS
configurator script can copy the files or you can do it manually. If you want
the script to copy the file to the standby node, enter Y. Enter the root
password, if prompted.

VMware Zimbra Collaboration Server Network Edition 7.1 21


ZCS Cluster Installation- Single-Node Configuration Guide

When asked, press Enter, to continue.

Cluster configuration saved in /tmp/cluster.conf.29843


This file must be copied to all cluster nodes now. This
script can do it for you using scp, or you can do it
manually.
Copy to all cluster nodes using scp? (Y/N) y

Copying /tmp/cluster.conf.29843 to node1.example.com:/etc/


cluster/cluster.conf
... scp /tmp/cluster.conf.29843 root@node1.example.com:/etc/
cluster/cluster.conf
root@node1.example.com's password:
cluster.conf.29843 100% 1560
1.5KB/s 00:00

Copying /tmp/cluster.conf.29843 to node2.example.com:/etc/


cluster/cluster.conf
... scp /tmp/cluster.conf.29843 root@node2.example.com:/etc/
cluster/cluster.conf
root@node2.example.com's password:
cluster.conf.29843 100% 1560
1.5KB/s 00:00

Configuration generated and pushed to all cluster nodes.

If necessary, use system-config-cluster GUI tool to further


customize the cluster configuration.

Configuring Red Hat Cluster for ZCS


When the cluster software is installed and the Zimbra installation is complete
on the active and standby nodes, run the Zimbra cluster configurator script to
prepare Red Hat Cluster Suite to run the ZCS. The cluster configurator script
is run on only the active mailbox node.

Start the Red Hat Cluster Suite Daemons


After the cluster configuration file is copied to the standby node, you can start
the Red Hat Cluster Suite Daemons.

Important: In order to start the cluster daemons correctly, you must be


logged on to each node before proceeding, and to see any errors, you should
have two sessions open for each node. You enter a command for one node,
then enter the same command for the second. You must enter each command
on both nodes, before proceeding to the next command.

Important:
 Log on to each node as root.
 Run tail -f /var/log/messages, on each node to watch for any errors.
 Open another session for each node.

22 Network Edition 7.1 VMware Zimbra Collaboration Server


ZCS Cluster Installation- Single-Node Configuration Guide

To start the Red Hat Cluster Service on a member, type the following
commands in this order. Remember to enter the command on each node
before proceeding to the next command.

1. service ccsd start. This is the cluster configuration system daemon that
synchronizes configuration between cluster nodes.

2. service cman start. This is the cluster heartbeat daemon. It returns when
both nodes have established heartbeat with one another.

3. service fenced start. This is the cluster I/O fencing system that allows
cluster nodes to reboot a failed node during failover.

4. service rgmanager start. This manages cluster services and resources.

The service rgmanager start command returns immediately, but initializing the
cluster and bringing up the ZCS application for the cluster services on the
active node may take some time.
After all commands have been issued on both nodes, run clustat command
on the active node, to verify all cluster services have been started.
Continue to enter the clustat command, until it reports all nodes have joined
the cluster, and all services have been started.
Because nodes may not join the cluster in sequence, some of the services
may start on nodes that are different from the configured preferred nodes. This
is expected and eventually will be restarted on the configured preferred node.
When clustat shows all services are running on the active node, the cluster
configuration is complete.

What to do if cluster services does not relocate to preferred node

If the services does not relocate to the active node after several minutes, you
can issue Red Hat Cluster Suite utility commands to manually correct the
situation.

Note: Not starting correctly on the preferred node usually is an issue that
happens only the first time the cluster is started.

For the cluster service that is not running on the active node, run clusvcadm -d
<cluster service name>, as root on the active node.

[root@node1.example.com]#clusvcadm -d mail1.example.com

This disables the service by stopping all associated Zimbra processes,


releasing the service IP address, and unmounting the service’s SAN volumes.
To enable a disabled service, run clusvcadm -e <service name> -m <node name>.
This command can be run on any cluster node. It instructs the specified node

VMware Zimbra Collaboration Server Network Edition 7.1 23


ZCS Cluster Installation- Single-Node Configuration Guide

to mount the SAN volumes of the service, bring up the service IP address, and
start the Zimbra processes.

[root@node1.example.com]#clusvcadm -e mail1.example.com -m
node1.example.com

Testing the Cluster Set up


To perform a quick test to see if failover works:

1. Log in to the remote power switch and turn off the active node.

2. Run tail -f /var/log/messages on the standby node. You will observe the cluster
becomes aware of the failed node, I/O fence it, and bring up the failed
service on the standby node.

Configuring ZCS in VCS


Each ZCS instance is represented in VCS as a service group having one
public IP address, one or more file systems, and an application agent. Use
VCS configuration interface to configure ZCS as you would any other
clustered application, with the following caveat:
 Two ZCS instances cannot run on the same host simultaneously. Because
VCS by default allows this type of operation, additional configuration is
needed to prevent it. This is done using the VCS concepts called limits and
prerequisites.
Set a prerequisite called ZCSInstance to 1 on each ZCS service group, and
set a limit called ZCSInstance to 1 on each host. This means running a ZCS
instance will cost "1", and each host is limited to the capacity of "1".
Therefore no host will be able to run 2 or more ZCS instances.
 An application agent script must be defined for the ZCS instance. Its name
should be the ZCS instance name. Set StartProgram property to:
/opt/zimbra-cluster/bin/zmcluctl start cluster.example.com
Set StopProgram property to:
/opt/zimbra-cluster/bin/zmcluctl stop cluster.example.com
Set MonitorProgram property to:
/opt/zimbra-cluster/bin/zmcluctl status cluster.example.com

Note: "cluster.example.com" should be replaced with the actual ZCS


instance name.

 Define dependencies in the service group. Make sure all file systems for
the ZCS instance are mounted in the correct order and public IP address is
brought up, before the application is started.

24 Network Edition 7.1 VMware Zimbra Collaboration Server


ZCS Cluster Installation- Single-Node Configuration Guide

View Zimbra Cluster Status


Go to the Zimbra administration console to check the status of the Zimbra
cluster. The Server Status page shows the cluster server, the node, the
services running on the cluster server, and the time the cluster was last
checked. The standby node is displayed as standby. If a service is not running,
it is shown as disabled.

VMware Zimbra Collaboration Server Network Edition 7.1 25


ZCS Cluster Installation- Single-Node Configuration Guide

26 Network Edition 7.1 VMware Zimbra Collaboration Server