Top
ETERNUS SF Storage Cruiser V16.9.1 / AdvancedCopy Manager V16.9.1 Cluster Environment Setup Guide
FUJITSU Storage

3.3 Installation Procedure of ETERNUS SF Manager (for Solaris/Linux)

The installation procedure of ETERNUS SF Manager (for Solaris/Linux) is performed as follows:

Note

The port number for the communication daemon to be specified by installation is for communication daemon for local transactions. For setting port number of the cluster transaction communication daemon, refer to "Chapter 8 Customization for Managed Server Transactions" to perform the procedure according to the cluster software to be used.

  1. Assign a user ID used by the ETERNUS SF Manager internally. (For example, 15999)
    Refer to the /etc/passwd file for the primary node and secondary node to assign an unused user ID.

  2. Perform the following steps on the primary node.

    1. Specify the following install parameters and perform a custom installation of ETERNUS SF Manager. However, do not install it on a shared disk.

      Install Parameter

      Content to Be Specified

      esfpostgres_UID

      User ID determined in step 1

      Management_server_IP_address

      Physical IP address of the Management Server (*1)

      *1: Do not specify the logical IP address.

      Refer to "Installation of ETERNUS SF Manager" in the Installation and Setup Guide for information on how to install ETERNUS SF Manager.

    2. Set up ETERNUS SF Manager.

      Refer to "Setup of ETERNUS SF Manager" in the Installation and Setup Guide for details. However, the procedures of "Settings Required to Register Storage Devices (When Using the ETERNUS DX S2 series Only)" and "Updating Management Server IP address information" are not required.

    3. Create a shared disk as required.

    4. Stop the daemons.

      Execute the following shell script.

      # /opt/FJSVesfcm/bin/stopesf.sh

      The following daemons are stopped:

      • ETERNUS SF Manager Apache daemon

      • ETERNUS SF Manager Tomcat daemon

      • ETERNUS SF Manager Postgres daemon

      • ETERNUS SF AdvancedCopy Manager daemon

      • SNMP Trap daemon

      • ETERNUS SF Storage Cruiser Optimization Option daemon

  3. Perform the following steps on the secondary node.

    1. Specify the following install parameters and perform a custom installation of ETERNUS SF Manager. However, do not install it on a shared disk.

      Install Parameter

      Content to Be Specified

      esfpostgres_UID

      User ID determined in step 1

      Management_server_IP_address

      Physical IP address of the Management Server (*1)

      *1: Do not specify the logical IP address.

      Refer to "Installation of ETERNUS SF Manager" in the Installation and Setup Guide for information on how to install ETERNUS SF Manager.
      For the installation target, specify the same path as the one specified for the primary node.

    2. Set up ETERNUS SF Manager.

      Refer to "Setup of ETERNUS SF Manager" in the Installation and Setup Guide for details. However, the procedures of "Settings Required to Register Storage Devices (When Using the ETERNUS DX S2 series Only)" and "Updating Management Server IP address information" are not required.

    3. Stop the daemons.

      Execute the following shell script.

      # /opt/FJSVesfcm/bin/stopesf.sh

      The following daemons are stopped:

      • ETERNUS SF Manager Apache Service

      • ETERNUS SF Manager Tomcat Service

      • ETERNUS SF Manager Postgres daemon

      • ETERNUS SF AdvancedCopy Manager daemon

      • SNMP Trap daemon

      • ETERNUS SF Storage Cruiser Optimization Option daemon