Novell PLATESPIN ORCHESTRATE 2.0.2 - HIGH AVAILABILITY CONFIGURATION GUIDE 06-17-2009, Руководство по настройке

Страница: 14 / 36

14 PlateSpin Orchestrate 2.0 High Availability Configuration Guide
no
vd
ocx
(e
n)
13
Ma
y 20
09
Figure 1-2
The Main Settings Page in the Heartbeat 2 Graphical Interface
The value in this field controls how long Heartbeat 2 waits for services to start. The default value is
20 seconds. The PlateSpin Orchestrate Server requires more time than this to start. We recommend
that you specify the value in this field at
120s
. More time might be required if your PlateSpin
Orchestrate grid is very large.
1.2.4 Setting Up OCFS2
OCFS2 is a general-purpose journaling file system that is fully integrated in the Linux 2.6 and later
kernel that ships with SLES 10 SP2. OCFS2 allows you to store application binary files, data files,
and databases on devices in a SAN. All nodes in a cluster have concurrent read and write access to
the file system. A distributed lock manager helps prevent file access conflicts. OCFS2 supports up to
32,000 subdirectories and millions of files in each directory. The O2CB cluster service (a driver)
runs on each node to manage the cluster.
To set up the high availability environment for PlateSpin Orchestrate, you need to first install the
High Availability pattern in YaST (this includes the
ocfs2-tools
and
ocfs2console
software
packages) and configure the Heartbeat 2 cluster management system on each physical machine that
participates in the cluster, and then provide a SAN in OCFS2 where the PlateSpin Orchestrate files
can be stored. For information on setting up and configuring OCFS2, see the
“Oracle Cluster File
System 2” (http://www.novell.com/documentation/sles10/sles_admin/data/ocfs2.html) section of
the SLES 10 Administration Guide .
Shared Storage Requirements for Creating a High Availability Environment
If you want data to be highly available, we recommend that you set up a Fibre Channel Storage Area
Network (SAN) to be used by your PlateSpin Orchestrate cluster.