Top
ETERNUS SF Storage Cruiser V15.3/ AdvancedCopy Manager V15.3 Cluster Environment Setup Guide
ETERNUS
Chapter 5 Customization for Management Server Transaction > 5.1 Customization for Windows version > 5.1.2 Customization for Secondary Node
PreviousNext

5.1.2 Customization for Secondary Node

This section explains the customization procedure for secondary nodes.

5.1.2.1 Common setting

This section explains the required procedure for customizing secondary nodes for ETERNUS SF Manager.

5.1.2.1.1 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.1 Shared resources".

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

    Run the following command for the stored generic script file:

    >cacls fileName /P "NT AUTHORITY\SYSTEM:F" "BUILTIN\Administrators:F" <RETURN>
5.1.2.1.2 Taking of ownership

Take ownership of the shared disk and of the transactions that are used by the Quorum disk and ETERNUS SF Manager.

5.1.2.1.3 Link setup for shared disk

On the secondary node, set up links to the directories on the shared disk for shared data.

  1. Use Explorer or a similar tool to modify the following directory names:

    • programDir\Common\etc\db

    • programDir\Common\etc\message

    • programDir\Common\sys\apache\conf

    • programDir\Common\sys\apache\logs

    • programDir\Common\var

    • programDir\Common\sys\tomcat\conf

    • programDir\Common\sys\tomcat\logs

    • programDir\Common\sys\tomcat\webapps\esfv15\WEB-INF\log

    Note

    If another program is using any files in the above directories, modification of the directory names may fail.
    If modification of the directory names fails, reboot the server and try again.

  2. Set up symbolic links from the directories on the local disks on the secondary node to the directories on the shared disk.

    Setup of symbolic links is required for the following directories:

    Local disk (linked source)

    Shared disk (link target)

    programDir\Common\etc\db

    driveName:\ETERNUS_SF\db

    programDir\Common\etc\message

    driveName:\ETERNUS_SF\message

    programDir\Common\sys\apache\conf

    driveName:\ETERNUS_SF\apache\conf

    programDir\Common\sys\apache\logs

    driveName:\ETERNUS_SF\apache\logs

    programDir\Common\var

    driveName:\ETERNUS_SF\var

    programDir\Common\sys\tomcat\conf

    driveName:\ETERNUS_SF\tomcat\conf

    programDir\Common\sys\tomcat\logs

    driveName:\ETERNUS_SF\tomcat\logs

    programDir\Common\sys\tomcat\webapps\esfv15\WEB-INF\log

    driveName:\ETERNUS_SF\tomcat\webapps\esfv15\WEB-INF\log

    Implement the following procedure for all directories:

    1. Move each directory that you copied according to "5.1.1.1.4 Copying of dynamic disk files" to the directory one level above the original directory.

    2. Execute the following command:

      >mklink /d srcDir dstDir <RETURN>

      For srcDir, specify the directory on the local disk from which to set the link.
      For dstDir, specify the directory on the shared disk to which the link is to be set.

  3. Edit the registry.

    Use the registry editor to modify the registry key that stores the var directory for the license manager.

    Change the registry key that is written in the registry of the secondary node to the value that you set in the registry for the primary node in "5.1.1.1.5 Link setup for shared disk".

5.1.2.1.4 Setup of access restrictions to database folder

Set up the access restrictions for the ETERNUS SF Manager database folder that you copied to the shared disk.

On the secondary node, execute the following command:

>cacls driveName:\ETERNUS_SF\db\data /T /G "esfpostgres:C" /E <RETURN>

5.1.2.2 Customization for Storage Cruiser's manager

Customize a secondary node according to the following procedure.

Perform step 4 and later are required when Optimization option is installed

  1. Edit the registry.

    Change the registry key that is written in the registry of the secondary node to the value that you set in the registry for the primary node in "5.1.1.2 Customization for Storage Cruiser's manager".

  2. Edit the setup file.

    Change the setting value that is written in the setup file of the secondary node to the value that you set in the setup file for the primary node in "5.1.1.2 Customization for Storage Cruiser's manager".

  3. Delete the directories.

    Use Explorer or a similar tool to delete the following directories of ETERNUS SF Manager from the secondary node.

    • environmentDir\ESC\Manager\etc

    • workDir\ESC\Manager\var

  4. Take ownership of the shared disk and of the transactions that are used by the Quorum disk and ETERNUS SF Manager.

  5. Use Explorer or a similar tool to modify the following directory names:

    • environmentDir\AST\Manager\etc\opt\FJSVssast\data

    • workDir\AST\Manager\var\opt\FJSVssast\data

    Examples to change the directory name are shown below:

    • C:ETERNUS_SF\AST\Manager\etc\opt\FJSVssast\data_original

    • C:ETERNUS_SF\AST\Manager\var\opt\FJSVssast\data_original

    Note

    If another program is using any files in the above directories, modification of the directory names may fail.
    If modification of the directory names fails, reboot the server and try again.

  6. On the secondary node, set up links to the directories on the shared disk for shared data.

    Local disk (linked source)

    Shared disk (link target)

    environmentDir\AST\Manage\etc\opt\FJSVssast\data

    sharedDisk\AST\etc\data

    workDir\AST\Manage\var\opt\FJSVssast\data

    sharedDisk\AST\var\data

    Execute the following command for all directories:

    >mklink /d srcDir dstDir <RETURN>

    For srcDir, specify the directory on the local disk from which to set the link.
    For dstDir, specify the directory on the shared disk to which the link is to be set.

5.1.2.3 Customization for AdvancedCopy Manager CCM

Customize the secondary node.

5.1.2.3.1 Preparation of generic script for AdvancedCopy Manager CCM

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

  1. In the program directory for ETERNUS SF Manager or AdvancedCopy Manager CCM on the secondary node, store the generic script file that you created in "4.1.4 Resources required for AdvancedCopy Manager CCM".

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

    Execute the following command to the stored generic script file.

    >cacls fileName /P "NT AUTHORITY\SYSTEM:F" "BUILTIN\Administrators:F" <RETURN>
5.1.2.3.2 Customization procedure

Customize the secondary node.

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

    On the secondary node, create the following directories.

    • $INS_DIR\CCM\noncluster\bin

    • $INS_DIR\CCM\noncluster\micc\sys

    • $INS_DIR\CCM\noncluster\sys

    $INS_DIR : "Program Directory" as specified during ETERNUS SF Manager or AdvancedCopy Manager CCM installation

  2. Copy the .install.sys, stxc_install.sys, and sys.properties files.

    On the secondary node, copy the following files from the following source directories to the destinations.

    Copy source directory

    Copy destination directory

    $INS_DIR\CCM\micc\sys\.install.sys

    $INS_DIR\CCM\noncluster\micc\sys\.install.sys

    $INS_DIR\CCM\bin\.stxc_install.sys

    $INS_DIR\CCM\noncluster\bin\.stxc_install.sys

    $INS_DIR\CCM\sys\sys.properties

    $INS_DIR\CCM\noncluster\sys\sys.properties

    Note

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

  3. Edit the .install.sys, stxc_install.sys, and sys.properties files.

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

    • File name: $INS_DIR\CCM\micc\sys\.install.sys

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

    • File name: $INS_DIR\CCM\bin\.stxc_install.sys

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

    • File name: $INS_DIR\CCM\sys\sys.properties

      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!)
    Table 5.3 Contents of setting values

    Setting item

    Setting value

    Sample setting

    *1

    $SHARE_DL:$SHARE_TOP\var\micc

    G:\ccmdata\var\micc

    *2

    $SHARE_DL:$SHARE_TOP\etc

    G:\ccmdata\etc

    *3

    $SHARE_DL\:$SHARE_TOP\\etc\\

    G\:\\ccmdata\\etc\\

    *4

    $SHARE_DL\:$SHARE_TOP\\var\\

    G\:\\ccmdata\\var\\

    The sample setting values use drive "G:" for $SHARE_DIR and "ccmdata" for $SHARE_TOP.

    Note

    If $SHARE_TOP of *3 or *4 is located on multiple directory levels, use "\\" as a delimiter.

5.1.2.4 Customization for AdvancedCopy Manager's manager

Customize a secondary node according to the following procedure.

Note

  • For Windows Server 2012, install the Failover Cluster Command Interface before performing the cluster setup.

  • The Windows "Computer Browser service" must be activated if a user belonging to the Administrators of the domain wants to perform customization for the Windows version of WSFC.

  • Do not use the Telnet Server service.

  1. Execute the cluster setup command.

    Execute the following cluster setup command on the secondary node:

    programDir\ACM\bin\stgclset_mscs

  2. Select the node type and shared disk.

    The initial window of the cluster setup command is displayed.

    Each item is explained below. Make the required entries and then click OK.

    Item

    Explanation

    Server Type

    Confirm that the server is a "Storage Management Server".

    Node Type

    Select "Secondary Node".

    Physical Disk Resource

    Select the resource for the shared disk for shared data.
    Select the same resource as for the primary node.

    Drive

    The drive letter corresponding to the physical disk resource is displayed.

    Required Disk Space

    The minimum disk size required for the cluster environment is displayed.

    Free Disk Space

    The amount of free disk space of the specified drive is displayed.

  3. Confirm the cluster information for the secondary node.

    The values set for the primary node will be displayed (Only the Node Type needs to be changed to "Secondary Node".).

    After confirming each item, click OK.

  4. Set the port number and service.

    The following page will display the value that was set for the primary node. If a port number and service has already been set, this page is not displayed.

    Click OK.

  5. The port number and service settings have been completed.

    Click OK.

  6. Confirm the database information.

    The values set for the primary node are displayed in the following page. Confirm each setting, and click Continue.

  7. Confirm the database access user.

    The values set for the primary node are displayed in the following page. Confirm each setting, and click Settings.

    Note

    The Windows "Computer Browser service" must be activated if a user belonging to the Administrators of the domain wants to perform customization for the Windows version of WSFC. If the customization is performed when the Computer Browser service is not started, the database setup processing might fail and the "Machine information cannot be obtained" message will be displayed.

  8. Confirm the setting information.

    When the setting information for the database is displayed, confirm the displayed information and click Start.

  9. The database setup process starts.

  10. The following progress bar will be displayed, when the process is completed. Click Close.

  11. The cluster setup of the secondary node has been completed.

    When the cluster setup completion window is displayed, click OK.

  12. Specify the resource dependency.

    If the shared disk for AdvancedCopy Manager repository and the shared disk for shared data are separated, add the shared disk resource for AdvancedCopy Manager repository to the dependency of the following resources by using Failover Cluster Manager.
    Refer to the Windows Server Failover Clustering manuals for information on how to add the resource dependency.

    • SymfoWARE RDB RDBSWSTF

    If you execute Management Server transactions and Managed Server transactions, or execute backup management in the Managed Server, add the disk resources for transactions to the following resource by using Failover Cluster Manager.

    • AdvancedCopy COM Service_logicalNodeName

    Note

    When a volume is added, or when it is deleted, it is necessary to again set up the above-mentioned dependency. Refer to "Notes on Cluster Operation" in the ETERNUS SF AdvancedCopy Manager Operation Guide (for Windows) for more information about this.

PreviousNext
Copyright 2012-2013 FUJITSU LIMITED