Top
ETERNUS SF Storage Cruiser V16.9.1 / AdvancedCopy Manager V16.9.1 Cluster Environment Setup Guide
FUJITSU Storage
Chapter 5 Customization for Management Server Transaction > 5.2 Customization for Solaris/Linux Clustered System > 5.2.2 Customization for Secondary Node
PreviousNext

5.2.2 Customization for Secondary Node

This section explains the customization procedure for a secondary node.

5.2.2.1 Startup Settings for ETERNUS SF Manager

Setup the starting process of ETERNUS SF Manager to be controlled by cluster software instead of operating system.

5.2.2.2 File Setup for Shared Disk

On the secondary node, create symbolic links to the directories in the shared disk for shared data. The procedure is as follows:

  1. On the secondary node, mount the shared disk for shared data that is used by the ETERNUS SF Manager.

  2. Rename the following directories.

    • /etc/opt/FJSVesfcm

    • /var/opt/FJSVesfcm

    • /var/opt/FJSVesflm

    Example

    The following is an example of the case of changing a directory name by putting "_bak" at the end of a file name.

    # mv /etc/opt/FJSVesfcm /etc/opt/FJSVesfcm_bak
# mv /var/opt/FJSVesfcm /var/opt/FJSVesfcm_bak
# mv /var/opt/FJSVesflm /var/opt/FJSVesflm_bak

  3. Create symbolic links to the directories in the shared disk for shared data.

    Specify in logicalNodeName the logical node name that was prepared in "4.1 Confirmation of Customization Items".

    Link Source Directory

    Link Target Directory
    (Symbolic Link File)

    <Mountpoint-of-shared-disk-for-shared-data>/etc/opt/FJSVesfcm

    /etc/opt/FJSVesfcm

    <Mountpoint-of-shared-disk-for-shared-data>/etc/opt/swstorage

    /etc/opt/swstorage/logicalNodeName

    <Mountpoint-of-shared-disk-for-shared-data>/var/opt/FJSVesfcm

    /var/opt/FJSVesfcm

    <Mountpoint-of-shared-disk-for-shared-data>/var/opt/FJSVesflm

    /var/opt/FJSVesflm

    <Mountpoint-of-shared-disk-for-shared-data>/var/opt/swstorage

    /var/opt/swstorage/logicalNodeName

    Example

    The example of creating symbolic links is as follows.

    # ln -s /esfmnt/etc/opt/FJSVesfcm /etc/opt/FJSVesfcm
# ln -s /esfmnt/etc/opt/swstorage /etc/opt/swstorage/acmnode1
# ln -s /esfmnt/var/opt/FJSVesfcm /var/opt/FJSVesfcm
# ln -s /esfmnt/var/opt/FJSVesflm /var/opt/FJSVesflm
# ln -s /esfmnt/var/opt/swstorage /var/opt/swstorage/acmnode1

5.2.2.3 Preparation of Generic Script

Follow the procedure below to prepare a generic script to be used on the secondary node.

  1. In the ETERNUS SF Manager program directory on the secondary node, store the generic script file that you created in "4.1 Confirmation of Customization Items".

  2. Set up the access privilege for the stored generic script file.

    Specify the authority that the root (super user) can access.

5.2.2.4 File Setup for Local Disk

  1. Create backup directories for AdvancedCopy Manager CCM environment setup files.

    On the secondary node, create the following directories:

    • /opt/FJSVccm/noncluster/bin

    • /opt/FJSVccm/noncluster/micc/sys

    • /opt/FJSVccm/noncluster/sys

    Point

    • Set "root (super user)" to the directory owner.

    • Set "755" to the directory permissions.

    Example

    The example of creating directories is as follows.

    # mkdir -p /opt/FJSVccm/noncluster/bin
# chmod -R 755 /opt/FJSVccm/noncluster/bin
# chown -R root:root /opt/FJSVccm/noncluster/bin
# mkdir -p /opt/FJSVccm/noncluster/micc/sys
# chmod -R 755 /opt/FJSVccm/noncluster/micc/sys
# chown -R root:root /opt/FJSVccm/noncluster/micc/sys
# mkdir -p /opt/FJSVccm/noncluster/sys
# chmod -R 755 /opt/FJSVccm/noncluster/sys
# chown -R root:root /opt/FJSVccm/noncluster/sys

  2. Back up AdvancedCopy Manager CCM environment setup files.

    On the secondary node, copy the following files to the copy destination.

    Copy Source File

    Copy Destination File

    /opt/FJSVccm/micc/sys/.install.sys

    /opt/FJSVccm/noncluster/micc/sys/.install.sys

    /opt/FJSVccm/bin/.stxc_install.sys

    /opt/FJSVccm/noncluster/bin/.stxc_install.sys

    /opt/FJSVccm/sys/sys.properties

    /opt/FJSVccm/noncluster/sys/sys.properties

    Example

    The copy execution example is as follows.

    # cp -p /opt/FJSVccm/micc/sys/.install.sys /opt/FJSVccm/noncluster/micc/sys/.install.sys
# cp -p /opt/FJSVccm/bin/.stxc_install.sys /opt/FJSVccm/noncluster/bin/.stxc_install.sys
# cp -p /opt/FJSVccm/sys/sys.properties /opt/FJSVccm/noncluster/sys/sys.properties

    Note

    The copied files are required for "Chapter 13 Deletion of Cluster Environment for Management Server Transactions".

  3. Edit AdvancedCopy Manager CCM environment setup files.

    On the secondary node, edit the path name from *1 to *4 of files below:

    ["/opt/FJSVccm/micc/sys/.install.sys" file]

    stxs_optdir= (Do not modify these settings!)
stxs_etcdir= (Do not modify these settings!)
stxs_vardir=*1
stxs_jredir= (Do not modify these settings!)

    ["/opt/FJSVccm/bin/.stxc_install.sys" file]

    stxc_optdir= (Do not modify these settings!)
stxc_etcdir=*2
stxc_jredir= (Do not modify these settings!)

    ["/opt/FJSVccm/sys/sys.properties" file]

    com.fujitsu.eternussf.acm.ccm.optpath= (Do not modify these settings!)
com.fujitsu.eternussf.acm.ccm.etcpath=*3
com.fujitsu.eternussf.acm.ccm.varpath=*4
com.fujitsu.eternussf.acm.ccm.micc.path= (Do not modify these settings!)
com.fujitsu.eternussf.acm.ccm.grapi.path= (Do not modify these settings!)
com.fujitsu.eternussf.acm.ccm.language= (Do not modify these settings!)

    The setting values from *1 to *4 are as follows.
    The sample setting values use "/esfmnt" for <Mountpoint-of-shared-disk-for-shared-data>.

    Setting
    Item

    Setting Value

    Sample Setting

    *1

    <Mountpoint-of-shared-disk-for-shared-data>/var/opt/FJSVccm/micc

    /esfmnt/var/opt/FJSVccm/micc

    *2

    <Mountpoint-of-shared-disk-for-shared-data>/etc/opt/FJSVccm/accc/etc

    /esfmnt/etc/opt/FJSVccm/accc/etc

    *3

    <Mountpoint-of-shared-disk-for-shared-data>/etc/opt/FJSVccm/

    /esfmnt/etc/opt/FJSVccm/

    *4

    <Mountpoint-of-shared-disk-for-shared-data>/var/opt/FJSVccm/

    /esfmnt/var/opt/FJSVccm/

  4. Register a port number.

    Use the "vi" command etc. of OS, and describe the port number and the following service name of the transaction communication daemon in the "/etc/services" file.

    • Transaction communication daemon: stgxfws_logicalNodeName

    Note

    Describe the same port number on the primary node and all secondary nodes.
    Specify in logicalNodeName the logical node name that was prepared in "4.1 Confirmation of Customization Items".

  5. Edit the "/opt/FJSVswstf/cluster/swcluster.ini" file.

    Table 5.6 Setting Items of "swcluster.ini" File

    Item Name

    Explanation

    Env_N

    Logical node name.
    Specify the logical node name that was prepared in "4.1 Confirmation of Customization Items".
    For N, specify a non-duplicate value from 1 to 20.

    BusiType

    AdvancedCopy Manager server type.
    Specify "1".

    Business

    Name of cluster transaction.

    ShareEtc

    Name of the environment setting directory for cluster transactions.
    <Mountpoint-of-shared-disk-for-shared-data>/etc/opt

    ShareVar

    Name of working directory for cluster transactions.
    <Mountpoint-of-shared-disk-for-shared-data>/var/opt

    MountPoint

    Mount point of shared disk for shared data.

    IPVersion

    IP version of the takeover IP address.
    Specify the following value according to the IP version of the takeover IP address to be used:

    • If using IPv4 address only: IPv4

    • If using IPv6 address only: IPv6

    • If using both IPv4 and IPv6 addresses: Dual

    IPAddr

    Takeover IP address.
    Specify the IPv4 address if using IPv4 address only or if using both IPv4 and IPv6 addresses.

    IPv6Addr

    Takeover IP address.
    Specify the IPv6 address if using IPv6 address only or if using both IPv4 and IPv6 addresses. The specified IPv6 address should one that is usable with the cluster software.

    NodeName

    Name of primary node (Host name of primary node).

    Modify or add the portions in italics according to your system environment.

    [ClusterCommon]
Cluster=ON
Max=20
StartTimeOut=300
StopTimeOut=300
System=GEN
Env_N=<Logical node name>
[<Logical node name>]
Type=Secondary
BusiType=<AdvancedCopy Manager server type>
Business=<Name of cluster transaction>
ShareEtc=<Mountpoint-of-shared-disk-for-shared-data>/etc/opt
ShareVar=<Mountpoint-of-shared-disk-for-shared-data>/var/opt
MountPoint=<Mountpoint-of-shared-disk-for-shared-data>
IPVersion=<IP version of IP address>
IPAddr=<Takeover IPv4 address>
IPv6Addr=<Takeover IPv6 address>
IPUseType=0
IPRscName=
Hostname=
NodeName=<Name of primary node (Host name of primary node)>
ClusterName=
DiskName=
GroupName=
SubNetMask=
MSCSNetName=
Date=00/00/00 00:00:00
Setup=YES
ResourceType=Procedure

    Example

    When creating the first cluster transactions on the same server, the example for editing the "swcluster.ini" file is as follows.

    [Before editing]

    [ClusterCommon]
Cluster=OFF
Max=20
StartTimeOut=300
StopTimeOut=300

    [After editing: for using IPv4 only]

    The italicized portions are the changes and additions to the original file.

    [ClusterCommon]
Cluster=ON
Max=20
StartTimeOut=300
StopTimeOut=300
System=GEN
    Env_1=acmnode1
    [acmnode1]
    Type=Secondary
    BusiType=1
    Business=acmbiz01
    ShareEtc=/esfmnt/etc/opt
    ShareVar=/esfmnt/var/opt
    MountPoint=/esfmnt
    IPVersion=IPv4
    IPAddr=192.0.2.10
    IPv6Addr=
    IPUseType=0
    IPRscName=
    Hostname=
    NodeName=m40001
    ClusterName=
    DiskName=
    GroupName=
    SubNetMask=
    MSCSNetName=
    Date=00/00/00 00:00:00
    Setup=YES
    ResourceType=Procedure

    [After editing: for using IPv6 only]

    The italicized portions are the changes and additions to the original file.

    [ClusterCommon]
Cluster=ON
Max=20
StartTimeOut=300
StopTimeOut=300
System=GEN
    Env_1=acmnode1
    [acmnode1]
    Type=Secondary
    BusiType=1
    Business=acmbiz01
    ShareEtc=/esfmnt/etc/opt
    ShareVar=/esfmnt/var/opt
    MountPoint=/esfmnt
    IPVersion=IPv6
    IPAddr=
    IPv6Addr=2001:db8::1234:0:0:1
    IPUseType=0
    IPRscName=
    Hostname=
    NodeName=m40001
    ClusterName=
    DiskName=
    GroupName=
    SubNetMask=
    MSCSNetName=
    Date=00/00/00 00:00:00
    Setup=YES
    ResourceType=Procedure

    [After editing: for using both IPv4 and IPv6]

    The italicized portions are the changes and additions to the original file.

    [ClusterCommon]
Cluster=ON
Max=20
StartTimeOut=300
StopTimeOut=300
System=GEN
    Env_1=acmnode1
    [acmnode1]
    Type=Secondary
    BusiType=1
    Business=acmbiz01
    ShareEtc=/esfmnt/etc/opt
    ShareVar=/esfmnt/var/opt
    MountPoint=/esfmnt
    IPVersion=Dual
    IPAddr=192.0.2.10
    IPv6Addr=2001:db8::1234:0:0:1
    IPUseType=0
    IPRscName=
    Hostname=
    NodeName=m40001
    ClusterName=
    DiskName=
    GroupName=
    SubNetMask=
    MSCSNetName=
    Date=00/00/00 00:00:00
    Setup=YES
    ResourceType=Procedure

    Example

    When using IPv4 only and when cluster transactions have already been created on the same server, the example for editing the "swcluster.ini file" is as follows.

    [Before editing]

    [ClusterCommon]
Cluster=ON
Max=20
StartTimeOut=300
StopTimeOut=300
System=GEN
Env_2=acmnode2
[acmnode2]
Type=Secondary
BusiType=2
Business=acmbiz02
ShareEtc=/esfmnt02/etc/opt
ShareVar=/esfmnt02/var/opt
MountPoint=/esfmnt02
IPAddr=
IPUseType=0
IPRscName=
Hostname=
NodeName=m40001
ClusterName=
DiskName=
GroupName=
SubNetMask=
MSCSNetName=
Date=00/00/00 00:00:00
Setup=YES
ResourceType=Procedure

    [After editing]

    The italicized portions are the additions to the original file.

    [ClusterCommon]
Cluster=ON
Max=20
StartTimeOut=300
StopTimeOut=300
System=GEN
Env_2=acmnode2
Env_1=acmnode1
[acmnode2]
Type=Secondary
BusiType=2
Business=acmbiz02
ShareEtc=/esfmnt02/etc/opt
ShareVar=/esfmnt02/var/opt
MountPoint=/esfmnt02
IPAddr=
IPUseType=0
IPRscName=
Hostname=
NodeName=m40001
ClusterName=
DiskName=
GroupName=
SubNetMask=
MSCSNetName=
Date=00/00/00 00:00:00
Setup=YES
ResourceType=Procedure
[acmnode1]
    Type=Secondary
    BusiType=1
    Business=acmbiz01
    ShareEtc=/esfmnt/etc/opt
    ShareVar=/esfmnt/var/opt
    MountPoint=/esfmnt
    IPVersion=IPv4
    IPAddr=192.0.2.10
    IPv6Addr=
IPUseType=0
    IPRscName=
    Hostname=
    NodeName=m40001
    ClusterName=
    DiskName=
    GroupName=
    SubNetMask=
    MSCSNetName=
    Date=00/00/00 00:00:00
    Setup=YES
    ResourceType=Procedure

  6. Edit the "/etc/opt/swstorage/swstg.ini" file.

    Table 5.7 Setting Items of "swstg.ini" File

    Item Name

    Explanation

    Type

    AdvancedCopy Manager local transaction server type.
    Specify "2".

    Note

    After starting operation, the program in this product may add/modify/delete parameters other than those of "Table 5.7 Setting Items of "swstg.ini" File" for the "swstg.ini" file. For this reason, do not add/modify/delete parameters other than those of "Table 5.7 Setting Items of "swstg.ini" File".

    Modify the portions in italics according to your system environment.

    [Common]
Edition=EE
Version=V16.9.1
Type=<AdvancedCopy Manager local transaction server type>
AFSType=1
Language=ENGLISH
BaseDir_Opt=/opt
BaseDir_Var=/var/opt
BaseDir_Etc=/etc/opt
[Install]
FJSVswstf=20101116
FJSVswtrc=20101116
FJSVgrapi=20101116
FJSVswsts=20101116
FJSVswsrp=20101116

    Example

    The example for editing the "swstg.ini" file is as follows. The italicized portions are the changes to the original file.

    [Common]
Edition=EE
Version=V16.9.1
Type=2
AFSType=1
Language=ENGLISH
BaseDir_Opt=/opt
BaseDir_Var=/var/opt
BaseDir_Etc=/etc/opt
[Install]
FJSVswstf=20101116
FJSVswtrc=20101116
FJSVgrapi=20101116
FJSVswsts=20101116
FJSVswsrp=20101116

5.2.2.5 Execution of Cluster Setup Command

Follow the procedure below to set up a secondary node.

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

  2. On the secondary node, execute the cluster setup command of the Storage Cruiser's manager.

    On the secondary node, execute the following command after blocking other users from accessing the shared disk for shared data.

    # /opt/FJSVssmgr/cluster/esc_clsetup -k Secondary -m <Mountpoint-of-shared-disk-for-shared-data>

  3. Check the setup object.

    Information specified by the command is displayed.

    # /opt/FJSVssmgr/cluster/esc_clsetup -k Secondary -m /esfmnt
ETERNUS SF Storage Cruiser settings are as follows.
Cluster system : PRIMECLUSTER
Node type : Secondary
Mount point : /esfmnt
IP Address : 192.0.2.10
Manager cluster setup : Are you sure? [y,n,?]

    After confirming the displayed information, input "y". The secondary node is set up.
    To interrupt the cluster environmental setting processing, input "n".

  4. Confirm that the displayed message is as follows.

    FJSVrcx:INFO:27701:esc_clsetup:secondary node setup completed

  5. On the secondary node, execute the cluster setup command of the AdvancedCopy Manager's manager.

    Execute the following commands in the given sequence.
    If the value of the environment variable PATH is more than 800 characters, after changing it to 800 characters or less, execute the "StgDbSetup" command.

    Sequence of Execution

    Command Name

    1

    "clset_FJSVswstf" command

    2

    "clset_FJSVswsts" command

    3

    "clset_FJSVswsrp" command

    4

    "StgDbSetup" command

    Example

    The command execution example is as follows.

    # /opt/FJSVswstf/bin/clset_FJSVswstf -f /esfmnt/etc/opt/swstorage/clsetup.ini -t Secondary
clset_FJSVswstf completed
# /opt/FJSVswsts/bin/clset_FJSVswsts -f /esfmnt/etc/opt/swstorage/clsetup.ini -t Secondary
clset_FJSVswsts completed
# /opt/FJSVswsrp/bin/clset_FJSVswsrp -f /esfmnt/etc/opt/swstorage/clsetup.ini -t Secondary
clset_FJSVswsrp completed
# /opt/FJSVswstf/bin/StgDbSetup -f /esfmnt/etc/opt/swstorage/clsetup.ini -t Secondary

5.2.2.6 Unmount of Shared Disk

On the secondary node, unmount the shared disk for shared data that is used by the ETERNUS SF Manager.

5.2.2.7 Settings Required to Register Storage Devices (When Using the ETERNUS DX S2 series Only)

To manage the ETERNUS DX S2 series, follow the procedure below on the secondary node.

  1. Back up the settings file.
    Copy the following file to the backup destination directory.

    • For Solaris environments

      File to be Backed up

      Backup Destination Directory

      /opt/FJSVesfcm/JRE/lib/security/java.security

      /opt/FJSVesfcm/tomcat/webapps/esf/WEB-INF/config

      /opt/FJSVccm/jre/lib/security/java.security

      /opt/FJSVccm/tools

      The command execution example is as follows.

      # cp -p /opt/FJSVesfcm/JRE/lib/security/java.security /opt/FJSVesfcm/tomcat/webapps/esf/WEB-INF/config/
# cp -p /opt/FJSVccm/jre/lib/security/java.security /opt/FJSVccm/tools/

    • For Linux environments

      File to be Backed up

      Backup Destination Directory

      /opt/FJSVesfcm/JRE/conf/security/java.security

      /opt/FJSVesfcm/tomcat/webapps/esf/WEB-INF/config

      /opt/FJSVccm/jre/conf/security/java.security

      /opt/FJSVccm/tools

      The command execution example is as follows.

      # cp -p /opt/FJSVesfcm/JRE/conf/security/java.security /opt/FJSVesfcm/tomcat/webapps/esf/WEB-INF/config/
# cp -p /opt/FJSVccm/jre/conf/security/java.security /opt/FJSVccm/tools/

  2. Copy the following file over the copy destination file.

    • For Solaris environments

      Copy Source File

      Copy Destination File

      /opt/FJSVesfcm/tomcat/webapps/esf/WEB-INF/config/java.security.forS2.solaris

      /opt/FJSVesfcm/JRE/lib/security/java.security

      /opt/FJSVccm/tools/java.security.forS2.solaris

      /opt/FJSVccm/jre/lib/security/java.security

      The command execution example is as follows.

      # cp -p /opt/FJSVesfcm/tomcat/webapps/esf/WEB-INF/config/java.security.forS2.solaris /opt/FJSVesfcm/JRE/lib/security/java.security
# cp -p /opt/FJSVccm/tools/java.security.forS2.solaris /opt/FJSVccm/jre/lib/security/java.security

    • For Linux environments

      Copy Source File

      Copy Destination File

      /opt/FJSVesfcm/tomcat/webapps/esf/WEB-INF/config/java.security.forS2.linux

      /opt/FJSVesfcm/JRE/conf/security/java.security

      /opt/FJSVccm/tools/java.security.forS2.linux

      /opt/FJSVccm/jre/conf/security/java.security

      The command execution example is as follows.

      # cp -p /opt/FJSVesfcm/tomcat/webapps/esf/WEB-INF/config/java.security.forS2.linux /opt/FJSVesfcm/JRE/conf/security/java.security
# cp -p /opt/FJSVccm/tools/java.security.forS2.linux /opt/FJSVccm/jre/conf/security/java.security

Point

To delete the registration of the ETERNUS DX S2 series from the product after the settings in this section are performed and operations are started, the settings content must be restored. For the procedure to restore the settings content, refer to "Work Required After Device Deletion of the ETERNUS DX S2 series" in the Installation and Setup Guide.

PreviousNext
Copyright 2013-2024 Fujitsu Limited