Top
Systemwalker Service Quality Coordinator Installation Guide
Systemwalker

3.7.2 Tasks to perform on a Manager

Perform this procedure if Manager clustering is to be used.


Procedure

Perform the procedure shown below.


3.7.2.1 Before constructing the environment


This section explains how to prepare the following group and basic resources that will be needed to construct the cluster environment:

  1. Prepare the resource group

    Prepare the group that the Manager will use. Use whichever of the following methods suits the operation mode of the cluster system.

    • When Systemwalker Service Quality Coordinator operates in an independent cluster system
      Use Failover Cluster Management/Cluster Administrator 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
      If Systemwalker Service Quality Coordinator is to be added to a Systemwalker Centric Manager resource group, create the Systemwalker Centric Manager cluster environment and prepare a group named "CentricMGR Group".


  2. Set up the shared disk, network and IP addresses

    Register the basic resources with the group.

    Register the physical disk that will be used to store the shared files of this product, the network and IP addresses with the resource group prepared in "Prepare resource group".


3.7.2.2 Installing on the server on the active node


  1. Install a Manager on the active server
    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.


  2. Set up clustering on the active server

    1. Obtain disk ownership on the active server

      Use Failover Cluster Management/Cluster Administrator to obtain the ownership of the following disk:

      • Quorum disk

      • Shared disk used by the product


    2. Vary the shared disk online

      Use Failover Cluster Management/Cluster Administrator to vary the shared disk online.


    3. Terminate Failover Cluster Management/Cluster Administrator and the registry editor

      Close Failover Cluster Management/Cluster Administrator and the registry editor.


    4. 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>


    5. 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.


    6. Set up the Manager

      If the Agent functions included with the Manager will be used to collect performance information about the Manager itself, create and deploy a collection policy by referring to "A.1 Server Resource Information Collection Policy Creation Command".


3.7.2.3 Installation on the standby node server


  1. Install a Manager on the standby server
    Perform the installation by referring to "3.1.1 Installing a Manager/Enterprise Manager[EE]".

    Point

    Create the same 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.


  2. Set up clustering on the standby server

    1. Terminate Failover Cluster Management/Cluster Administrator and the registry editor

      Close Failover Cluster Management/Cluster Administrator and the registry editor.


    2. 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>


3.7.2.4 Registering resources

Register the Manager service as an MSCS/failover clustering resource on the active server.


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


"Systemwalker SQC sqcschdle" service

Item

Setting

Name

Systemwalker SQC sqcschdle

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

Sqcschdle


"Systemwalker SQC dbrefsv" service

Item

Setting

Name

Systemwalker SQC dbrefsv

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

Systemwalker SQC-A dbrefsv


"Systemwalker SQC dbregsv" service

Item

Setting

Name

Systemwalker SQC dbregsv

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

Systemwalker SQC-A dbregsv


3.7.2.5 Starting services


Use Failover Cluster Management/Cluster Administrator to vary the following Systemwalker Service Quality Coordinator service online:

This completes the process of setting up the Manager environment in a cluster system constructed using MSCS/failover clustering.

The next step is to install and set up the Manager according to the operation model that will be adopted.


The Manager environment settings in an MSCS cluster system are now complete.

The next step is to install and set up the environment according to the operation model that will be adopted.


Note

Installation of the Manager is now complete, so the procedure described in "Tasks to be performed on a Manager" can be skipped.