This section contains instructions for configuring an asymmetric high availability Calendar Server cluster.
This sections contains the following topics:
Create a file system on the shared disk. The /etc/vfstab should be identical on all the nodes of the cluster.
For CFS, it should look similar to the following example.
## Cluster File System/Global File System ## /dev/md/penguin/dsk/d400 /dev/md/penguin/rdsk/d400 /cal ufs 2 yes global,logging
For example, for FFS:
## Fail Over File System/Local File System ## /dev/md/penguin/dsk/d400 /dev/md/penguin/rdsk/d400 /cal ufs 2 no logging
The fields in these commands are separated by tabs, not just spaces.
For all nodes of the cluster, create a directory, /Cal, on the shared disk where configuration and data is held. For example, do the following command for every shared disk:
mkdir -P /Cal
This section contains instructions for the tasks involved in installing and configuring high availability for Calendar Server.
Perform each of the following tasks in turn to complete the configuration:
Install Calendar Server on the Primary and Secondary nodes of the cluster, using the Communications Suite 5 installer.
Be sure to specify the same installation root on all nodes.
At the Specify Installation Directories panel, answer with the installation root for both nodes.
This will install the Calendar Server binaries in the following directory:/install-root/SUNWics5/cal. This directory is called the Calendar Server base (cal-svr-base).
Choose the Configure Later option.
After the installation is complete, verify that the files are installed.
# pwd /cal-svr-base # ls -rlt total 16 drwxr-xr-x 4 root bin 512 Dec 14 12:52 share drwxr-xr-x 3 root bin 512 Dec 14 12:52 tools drwxr-xr-x 4 root bin 2048 Dec 14 12:52 lib drwxr-xr-x 2 root bin 1024 Dec 14 12:52 sbin drwxr-xr-x 8 root bin 512 Dec 14 12:52 csapi drwxr-xr-x 11 root bin 2048 Dec 14 12:52 html
Run the Directory Preparation Script (comm_dssetup.pl) against your existing Directory Server LDAP.
This prepares your Directory Server by setting up new LDAP schema, index, and configuration data.
For instructions and further information about running comm_dssetup.pl, see Chapter 8, Directory Preparation Tool (comm_dssetup.pl), in Sun Java Communications Suite 5 Installation Guide.
Use the Sun Cluster command line interface as indicated to set up HA on the first node.
Refer to 6.5 Naming Conventions for All Examples in this Deployment Example for Configuring High Availability in Calendar Server Version 6.3 as a key for directory names and Sun Cluster resource names in the examples.
Register the Calendar Server and HAStoragePlus resource
./scrgadm -a -t SUNW.HAStoragePlus ./scrgadm -a -t SUNW.scics
Create a failover Calendar Server resource group.
For example, the following instruction creates the calendar resource group CAL-RG with the primary node as Node1 and the secondary, or failover, node as Node2.
./scrgadm -a -g CAL-RG -h node1,node2
Create a logical hostname resource in the Calendar Server resource group and bring the resource group online.
For example, the following instructions create the logical hostname resource LOG-HOST-RS, and then brings the resource group CAL-RG online.
./scrgadm -a -L -g CAL-RG -l LOG-HOST-RS ./scrgadm -c -j LOG-HOST-RS -y \ R_description="LogicalHostname resource for LOG-HOST-RS" ./scswitch -Z -g CAL-RG
Create and enable the HAStoragePlus resource.
For example, the following instructions create and enable the HAStoragePlus resource CAL-HASP-RS.
scrgadm -a -j CAL-HASP-RS -g CAL-RG -t SUNW.HAStoragePlus:4 -x FilesystemMountPoints=/cal scrgadm -c -j CAL-HASP-RS -y R_description="Failover data service resource for SUNW.HAStoragePlus:4" scswitch -e -j CAL-HASP-RS
Run the configuration program.
For example, from the /cal-svr-base/sbin directory:
# pwd /cal-svr-base/sbin # ./csconfigurator.sh
For further information about running the configuration script, see Chapter 2, Initial Runtime Configuration Program for Calendar Server 6.3 software (csconfigurator.sh)also in this guide.
At the Run Time Configuration panel, deselect both Calendar Server startup options.
At the Directories panel, configure all directories on a shared disk. Use the following locations:
Once you have finished specifying the directories, choose Create Directory.
At the Archive and Hot Backup panel, specify the following choices:
When you have finished specifying the directories, choose the Create Directory option.
Verify that the configuration is successful.
Look at the end of the configuration output to make sure it says: “All Tasks Passed.” The following example shows the last part of the configuration output.
... All Tasks Passed. Please check install log /var/sadm/install/logs/Sun_Java_System_Calendar_Server_install.B12141351 for further details.
For a larger sample of the output, see 6.11 Example Output from the Calendar Configuration Program (Condensed)
Click Next to finish configuration.
Switch to the secondary node.
Using the Sun Cluster command line interface, switch to the secondary node. For example, the following command switches the resource group to the secondary (failover) node, Node2:
scswitch -z -g CAL-RG -h Node2
Create a symbolic link from the Calendar Server config directory to the config directory of the Shared File System.
For example, perform the following commands:
# pwd /cal-svr-base # ln -s /share-disk-dir/config .
Do not forget the dot (.) at the end of the ln command.
Configure Calendar Server on the secondary node using the state file from the primary node configuration.
Share the configuration of the primary node by running the state file created when you ran the configuration program.
For example, run the following command:
# /cal-svr-base/sbin/csconfigurator.sh -nodisplay -noconsole -novalidate
Check that all the tasks passed as with the first time you ran the configuration program.
Edit the Configuration File (ics.conf)
Edit the ics.conf file by adding the following parameters to the end of the file. The logical hostname of the calendar resource is LOG-HOST-RS.
Back up your ics.conf file before performing this step.
! The following are the changes for making Calendar Server ! Highly Available ! local.server.ha.enabled="yes" local.server.ha.agent="SUNWscics" service.http.listenaddr="IPAddress" local.hostname="LOG-HOST-RS" local.servername="LOG-HOST-RS" service.ens.host="LOG-HOST-RS" service.http.calendarhostname="LOG-HOST-RS-Domain.com" local.autorestart="yes" service.listenaddr="IPAddress"
Create the Calendar Server resource group and enable it.
For this example, the resource group name is CAL-SVR-RS. You will also be required to supply the logical host resource name and the HAStoragePlus resource name.
./scrgadm -a -j CAL-SVR-RS -g CAL-RG -t SUNW.scics -x ICS_serverroot=/cal-svr-base -y Resource_dependencies=CAL-HASP-RS,LOG-HOST-RS ./scrgadm -e -j CAL-SVR-RS
Test the successful creation of the calendar resource group by performing a fail over.
./ scswitch -z -g CAL-RG -h Node1
When you have finished this step, you have completed the creation and configuration of the asymmetric high availability system for Calendar Server. The section that follows explains how to set up logging on Sun Cluster for debug purposes.
You have now finished the installation and configuration of an asymmetric Calendar Server HA system.