Perform this procedure if Enterprise Manager clustering will be used in a two-tier system.
Procedure
Perform the procedure shown below.
3.7.1.1 Before constructing the environment
Prepare the resource group
Set up the shared disk, network and IP addresses
3.7.1.2 Installing on the server on the active node
Install an Enterprise Manager on the active server
Set up clustering on the active server
3.7.1.3 Installing on the server on the standby node
Install an Enterprise Manager on the standby server
Set up clustering on the standby server
This section explains how to prepare the following group and basic resources required for constructing the cluster environment:
Resource group for registering Systemwalker Service Quality Coordinator
This resource group is used to enable Systemwalker Service Quality Coordinator to operate in a cluster system.
Shared disk
The shared disk is used to store files that are shared by the Enterprise Manager on the active node and the Enterprise Manager on the standby node.
If the storage location of the performance database (PDB) and the archive files are changed, make sure to configure the storage location physical disks as shared disks.
Logical IP addresses
IP addresses that are unique within the network are newly assigned when operating the nodes in a cluster system.
Logical host names
These are network host names corresponding to logical IP addresses.
Prepare the resource group
Prepare the group to be used by Enterprise Managers. The operation mode of the cluster system determines which of the following two methods is used:
When Systemwalker Service Quality Coordinator operates in an independent cluster system
In this case, Failover Cluster Management/Cluster Administrator is used to register the resource group for this product under the following name:
Systemwalker SQC Group
When Systemwalker Service Quality Coordinator is added to a Systemwalker Centric Manager cluster system
To add the resource group to a Systemwalker Centric Manager resource group, create a Systemwalker Centric Manager cluster environment and then prepare a group named "CentricMGR Group".
Set up the shared disk, network and IP addresses
Register the basic resources with the group.
The physical disk that will store shared files used by the product, the network and the IP addresses are registered with the resource group created in "1. Prepare the resource group" above.
Install an Enterprise Manager on the active server
Install an Enterprise Manager Perform the installation process as described in "3.1.1 Installing a Manager/Enterprise Manager[EE]".
Note
Do not install an Enterprise Manager on the shared disk.
Set up clustering on the active server
Obtain disk ownership on the active server.
Use Failover Cluster Management/Cluster Administrator to obtain ownership of the following disks:
Quorum disk
Shared disk used by the product
Vary the shared disk online
Use Failover Cluster Management/Cluster Administrator to vary the shared disk online.
Terminate Failover Cluster Management/Cluster Administrator and the registry editor
Close Failover Cluster Management/Cluster Administrator and the registry editor.
Execute the cluster setup command on the active server
Execute the cluster setup command "sqcsetupclp" on the active server by referring to "A.6 Cluster Setup Commands".
The command format is as follows:
<installation directory>\bin\sqcsetupclp -m <shared disk> -h <logical host name> |
Change the storage location of the performance database (PDB) and the archive files
Refer to "6.6.1 Changing the PDB/Archive File Storage Location" for details.
Set up the Enterprise Manager
If the Agent functions included with the Enterprise Manager are used to collect performance information about the Enterprise Manager itself, create and apply a collection policy by referring to "A.1 Server Resource Information Collection Policy Creation Command".
Install an Enterprise Manager on the standby server
Perform the installation process as described in "3.1.1 Installing a Manager/Enterprise Manager[EE]".
Point
Create the same Enterprise Manager environment (same device name, shared disk and installation path) on both the active and standby nodes.
Do not install an Enterprise Manager on the shared disk.
Set up clustering on the standby server
Terminate Failover Cluster Management/Cluster Administrator and the registry editor
Close Failover Cluster Management/Cluster Administrator and the registry editor.
Execute the cluster setup command on the standby server
Execute the cluster setup command "sqcsetupclp" on the standby server by referring to "A.6 Cluster Setup Commands".
The command format is as follows:
<installation directory>\bin\sqcsetupcls -m <shared disk> |
Register the Enterprise Manager service as an MSCS resource on the active server.
Register the following service as an application resource for MSCS/failover clustering with the resource group created in "Prepare resource group":
"Systemwalker SQC DCM" service
Note
If Systemwalker Service Quality Coordinator is installed in the following environments and the [New resource Wizard] is used to add resources, set the "Resource dependencies" shown in the following table after the resources have been added.
Windows Server 2008 Enterprise
Windows Server 2008 Datacenter
"Systemwalker SQC DCM" service
Item | Setting |
|---|---|
Name | Systemwalker SQC DCM |
Resource type | Generic service |
Group | Systemwalker SQC Group or CentricMGR Group |
Executable owner | Active server and standby server |
Resource dependencies | Disk set as the shared disk, IP address |
Service name | SQC_DCM |
Use Failover Cluster Management/Cluster Administrator to vary the following Systemwalker Service Quality Coordinator service online:
"Systemwalker SQC DCM" service
This completes the process of setting up the Enterprise Manager environment in a cluster system constructed using MSCS/failover clustering.
The next step is to install and set up the environment according to the operation model that will be adopted.
Note
If a two-tier operation model environment for a Manager is being constructed, installation of the Enterprise Manager is now complete and the procedure described in "Tasks to be performed on an Enterprise Manager" can be skipped.
