A.3.1.1 Preparation
Cluster installation and configuration
To operate managers as cluster services (cluster applications) in a cluster system, install and configure manager software on each node. Be sure to check the device names and the mount point names when configuring the shared disks.
Information
Operations that are run where the manager is set up as cluster service (cluster application) is referred to as manager operations is respectively. Collectively, these operations are called Manager operations.
See
For details about PRIMECLUSTER, refer to the version of "PRIMECLUSTER Installation and Administration Guide" for the respective operating System.
Resource configuration
Manager installation on a cluster system requires the following resources.
Resources used in the cluster system
Takeover IP addresses for the admin servers
Allocate new unique IP addresses in the network that are used for the admin servers in the cluster system with PRIMECLUSTER Ipaddress resource creation. This step can be skipped if the IP addresses for the existing cluster services (cluster applications) are used.
Shared disks for the admin servers
Configure PRIMECLUSTER GDS volumes that will store shared data for the admin servers. The number of required volumes is as follows.
Name | Number | Content |
|---|---|---|
Shared data disk for the server | 1 (Note 1) | Shared data storage destination for the server |
Note1: When a server operates as the server, both the admin servers use one shared disk.
Note2: Necessary when Interstage Application Server Smart Repository is installed.
Resources used outside the cluster system
Port numbers for the admin servers
Allocate the port numbers for the admin servers, which are set as described in "4.1.4.1 /etc/services configuration" (in Solaris OS) or "4.2.4.1 /etc/services configuration" (in Linux).
Shared disk space
The ETERNUS SF Storage Cruiser shared disks include the following directories that are used with ETERNUS SF Storage Cruiser.
For the admin server
Required disk space is calculated from the sum of static disk space and dynamic disk space. For details, please refer to "4.1.1.2.5 Static disk space" and "4.1.1.2.6 Dynamic disk space" (in Solaris OS) or "4.2.1.2.5 Static disk space" and "4.2.1.2.6 Dynamic disk space" (in Linux).
Section number | Directory | Required disk space (Unit : MB) |
|---|---|---|
1 | /etc | 6 |
2 | /var | 552 + Repository for storage resource manager (Note 1) |
Note 1: For how to calculate the "repository for storage resource manager", please refer to "Repository for Manager" in "4.1.1.2.6 Dynamic disk space" (in Solaris OS) or "Repository for Manager" in "4.2.1.2.6 Dynamic disk space" (in Linux).
A.3.1.2 Installation
Install manager.
Using similar steps on the primary node and the secondary node, perform the procedure from the beginning of "4.1.3 Installation procedure" (in Solaris OS) or "4.2.3 Installation procedure" (in Linux) for manager.
Note
Please do not install software on the shared disks.
Please do not perform the procedure described in "4.1.4 Post-installation setup" (in Solaris OS) or "4.2.4 Post-installation setup" (in Linux) for manager at this point.
