This section explains the customization procedure for a primary node.
Follow the procedure below to prepare a generic script to be used on the primary node.
In the ETERNUS SF Manager program directory on the primary node, store the generic script file that you created in "4.1 Confirmation of Customization Items".
Set the access privilege for the stored generic script file.
Execute the following command by specifying the stored generic script file in fileName.
>cacls fileName /P "NT AUTHORITY\SYSTEM:F" "BUILTIN\Administrators:F" <RETURN>
Example
The command execution example is as follows.
C:\ETERNUS_SF>cacls apache.vbs /P "NT AUTHORITY\SYSTEM:F" "BUILTIN\Administrators:F" Are you sure (Y/N)?y Processing file: C:\ETERNUS_SF\apache.vbs
Create the cluster resources to be used on the primary node.
For Adding ETERNUS SF Manager to Already Existing Cluster Services (Transactions)
Use the Failover Cluster Manager screen to stop all transactions of the relevant cluster service.
However, keep the shared disk being used by ETERNUS SF Manager online.
For Creating ETERNUS SF Manager in Newly Created Cluster Services (Transactions)
Follow the procedure below to create cluster resources for ETERNUS SF Manager in the cluster service.
The screen name and item name may be different depending on operating systems.
For explanation purposes, the name of the "Role" for ETERNUS SF Manager is set to "ESF-manager".
Start the Failover Cluster Manager screen and connect to the clustered system.
Create a Role for ETERNUS SF Manager.
Right-click Roles in the Failover Cluster Manager tree, and, in the subsequently displayed menu, select Create Empty Role.
Under Roles, the New Role is created.
Right-click New Role and then select Properties.
The New Role Properties dialog box is displayed.
On the General tab, modify the Name. Then, under Preferred Owners, select the resource name for the primary node, and click Apply.
After applying the settings, click OK.
Allocate a shared disk to the Role for ETERNUS SF Manager.
Right-click Roles > ESF-manager, and then select Add Storage.
The Add Storage screen is displayed.
From Available disks, select the shared disk for ETERNUS SF Manager and click OK.
Allocate a client access point to the Role for ETERNUS SF Manager.
Right-click Roles > ESF-manager, and then select Add Resource > Client Access Point.
The New Resource Wizard screen is displayed.
Set the following items and click Next.
Name
Set the network name that you prepared in "4.1 Confirmation of Customization Items".
Networks
Check the network to be used.
Address
Set the Logical IP address resources (the IP address resources) that you prepared in "4.1 Confirmation of Customization Items".
Check the contents on the Confirmation screen and click Next.
Check the contents on the Summary screen and click Finish.
Make sure that the settings have been applied.
At the center of the screen, under ESF-manager, confirm that the set resources have been added to the Server Name in the Resources tab.
Move the Quorum disk, the shared disk that is used by ETERNUS SF Manager, and transactions.
Refer to your cluster software manuals for information on how to move them.
Copy files on the dynamic disks of ETERNUS SF Manager on the primary node to the shared disk for ETERNUS SF Manager.
Follow the procedure below to copy files.
If you recreate a cluster environment and the old environment files remain on the shared disk, after deleting them, perform the procedure below.
Use Explorer or a similar tool to create the following directories on the shared disk.
Directories to Be Created on Shared Disk | Explanation |
|---|---|
storeDirForCommonData | This is a stored directory for shared data of ETERNUS SF Manager common. Create it in the shared disk with the following name:
|
storeDirForEscData | This is a stored directory for shared data of Storage Cruiser's manager. Create it in the shared disk with any name:
|
storeDirForAstData | This is a stored directory for shared data of Storage Cruiser's manager Optimization option. Create it in the shared disk with any name:
|
storeDirForCcmData | This is a stored directory for shared data of AdvancedCopy Manager CCM. Create it in the shared disk with any name:
|
Point
The characters that can be used for the directory path name that is created under the shared disk are alphanumeric characters excluding space character. The specifiable length of the path name is 76 characters or less including driveNameOfSharedDisk.
Use Explorer or a similar tool to copy the files from the local disks on the primary node to the shared disk.
Copy files in the copy source directory to the copy destination directory.
The programDir is "Program Directory" specified at the ETERNUS SF Manager installation, the envDir is "Environment Directory", and the workDir is "Working Directory".
Local Disk (Copy Source) | Shared Disk (Copy Destination) |
|---|---|
programDir\Common\sys\apache\conf | storeDirForCommonData\apache\conf |
programDir\Common\sys\apache\logs | storeDirForCommonData\apache\logs |
programDir\Common\sys\tomcat\conf | storeDirForCommonData\tomcat\conf |
programDir\Common\sys\tomcat\logs | storeDirForCommonData\tomcat\logs |
programDir\Common\sys\tomcat\webapps\esf\WEB-INF\log | storeDirForCommonData\tomcat\webapps\esf\WEB-INF\log |
envDir\Common\etc\db | storeDirForCommonData\db |
envDir\Common\etc\message | storeDirForCommonData\message |
envDir\ESC\Manager\etc | storeDirForEscData\ESC\Manager\etc |
envDir\AST\Manager\etc\opt\FJSVssast\data | storeDirForAstData\AST\etc\data |
envDir\CCM\etc | storeDirForCcmData\etc |
workDir\Common\var | storeDirForCommonData\var |
workDir\LM\var | storeDirForCommonData\LM\var |
workDir\ESC\Manager\var | storeDirForEscData\ESC\Manager\var |
workDir\AST\Manager\var\opt\FJSVssast\data | storeDirForAstData\AST\var\data |
workDir\CCM\var | storeDirForCcmData\var |
Use Explorer or a similar tool to rename the following directories:
programDir\Common\sys\apache\conf
programDir\Common\sys\apache\logs
programDir\Common\sys\tomcat\conf
programDir\Common\sys\tomcat\logs
programDir\Common\sys\tomcat\webapps\esf\WEB-INF\log
envDir\Common\etc\db
envDir\Common\etc\message
envDir\ESC\Manager\etc
envDir\AST\Manager\etc\opt\FJSVssast\data
workDir\Common\var
workDir\ESC\Manager\var
workDir\AST\Manager\var\opt\FJSVssast\data
Note
If another program is using any files in the above directories, rename of the directory may fail.
If rename of the directory fails, reboot the server and try again.
On the primary node, create symbolic links to the directories in the shared disk for shared data.
Create symbolic links from the following directories on the local disks on the primary node to the directories on the shared disk.
Link | Target |
|---|---|
programDir\Common\sys\apache\conf | storeDirForCommonData\apache\conf |
programDir\Common\sys\apache\logs | storeDirForCommonData\apache\logs |
programDir\Common\sys\tomcat\conf | storeDirForCommonData\tomcat\conf |
programDir\Common\sys\tomcat\logs | storeDirForCommonData\tomcat\logs |
programDir\Common\sys\tomcat\webapps\esf\WEB-INF\log | storeDirForCommonData\tomcat\webapps\esf\WEB-INF\log |
envDir\Common\etc\db | storeDirForCommonData\db |
envDir\Common\etc\message | storeDirForCommonData\message |
envDir\ESC\Manager\etc | storeDirForEscData\ESC\Manager\etc |
envDir\AST\Manager\etc\opt\FJSVssast\data | storeDirForAstData\AST\etc\data |
workDir\Common\var | storeDirForCommonData\var |
workDir\ESC\Manager\var | storeDirForEscData\ESC\Manager\var |
workDir\AST\Manager\var\opt\FJSVssast\data | storeDirForAstData\AST\var\data |
Symbolic links can be created by using the "mklink" command of Windows.
Example
The example of creating a symbolic link from programDir\Common\sys\apache\conf to storeDirForCommonData\apache\conf is shown below.
>mklink /d programDir\Common\sys\apache\conf storeDirForCommonData\apache\conf
Create backup directories for AdvancedCopy Manager CCM environment setup files.
On the primary node, create the following directories:
The programDir is "Program Directory" specified at the ETERNUS SF Manager installation.
programDir\CCM\noncluster\bin
programDir\CCM\noncluster\micc\sys
programDir\CCM\noncluster\sys
Back up AdvancedCopy Manager CCM environment setup files.
On the primary node, copy the following files to the copy destination.
Copy Source File | Copy Destination File |
|---|---|
programDir\CCM\micc\sys\.install.sys | programDir\CCM\noncluster\micc\sys\.install.sys |
programDir\CCM\bin\.stxc_install.sys | programDir\CCM\noncluster\bin\.stxc_install.sys |
programDir\CCM\sys\sys.properties | programDir\CCM\noncluster\sys\sys.properties |
Note
The copied files are required for "Chapter 13 Deletion of Cluster Environment for Management Server Transactions".
Edit AdvancedCopy Manager CCM environment setup files.
On the primary node, edit the path name from *1 to *4 of files below:
[programDir\CCM\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!)
[programDir\CCM\bin\.stxc_install.sys file]
stxc_optdir= (Do not modify these settings!) stxc_etcdir=*2 stxc_jredir= (Do not modify these settings!)
[programDir\CCM\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!)
Note
In *3 and *4, use "\:" as a drive separate character.
In *3 and *4, use "\\" as a path separate character of storeDirForCcmData.
The setting values from *1 to *4 are as follows.
The sample setting values use "G:\ccmdata" for storeDirForCcmData.
Setting Item | Setting Value | Sample Setting |
|---|---|---|
*1 | storeDirForCcmData\var\micc | G:\ccmdata\var\micc |
*2 | storeDirForCcmData\etc | G:\ccmdata\etc |
*3 | storeDirForCcmData\\etc\\ | G\:\\ccmdata\\etc\\ |
*4 | storeDirForCcmData\\var\\ | G\:\\ccmdata\\var\\ |
Edit the detailed setting file (storeDirForEscData\ESC\Manager\etc\opt\FJSVssmgr\current\sanma.conf) of the storage management.
Use the text editor to add the line of "LOGICAL_MANAGER_IP" and/or "LOGICAL_MANAGER_V6IP" in the detailed setting file. Additional line is different according to the takeover IP address for Management Server transaction as follows:
For only IPv4 address
LOGICAL_MANAGER_IP="takeoverIPAddressForManagementServerTransaction(IPv4Format)";
For only IPv6 address
LOGICAL_MANAGER_V6IP="takeoverIPAddressForManagementServerTransaction(IPv6Format)";
For IPv4 address and IPv6 address
LOGICAL_MANAGER_IP="takeoverIPAddressForManagementServerTransaction(IPv4Format)"; LOGICAL_MANAGER_V6IP="takeoverIPAddressForManagementServerTransaction(IPv6Format)";
Refer to "LOGICAL_MANAGER_IP" and "LOGICAL_MANAGER_V6IP" in "sanma.conf Parameter" in the Storage Cruiser Operation Guide for information on the detailed setting file.
Edit the registry.
As described below, change the path, that is written in the registry key, of the "var" directory of the license manager function by using the registry editor.
The workDir is "Working Directory" specified at the ETERNUS SF Manager installation.
Before Change | After Change |
|---|---|
workDir\LM\var | storeDirForCommonData\LM\var |
[Sample display for registry key]
HKEY_LOCAL_MACHINE
SOFTWARE
Fujitsu
ETERNUS SF License Manager
CurrentVersion
VarPathNameSet up the access privilege for the directories on the shared disk.
Set up the access privilege for the log directory.
On the primary node, execute the following command.
>cacls storeDirForCommonData\var\log /T /P "NT AUTHORITY\SYSTEM:F" "BUILTIN\Administrators:F"
Set up the access privilege for the database directory.
On the primary node, execute the following command.
>cacls storeDirForCommonData\db\data /T /P "NT AUTHORITY\SYSTEM:F" "BUILTIN\Administrators:F" "esfpostgres:C"
Follow the procedure below to set up a primary node.
Note
Perform the procedures using Administrator privileges. The Windows "Computer Browser service" must be activated if a user belonging to the Administrators of the domain wants to perform customization. If the other products are not using "Computer Browser Service", after this operation is completed, "Computer Browser Service" can be stopped without causing any problems.
Install the Failover Cluster Command Interface before performing the cluster setup.
Do not use the Telnet Server service.
Instruct the start of the cluster setup.
On the primary node, execute the following cluster setup command.
The programDir is "Program Directory" specified at the ETERNUS SF Manager installation.
programDir\ACM\bin\stgclset_mscs
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 "Primary Node". |
Physical Disk Resource | Select the "Disk resource of shared disk for shared data" that was prepared in "4.1 Confirmation of Customization Items". |
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. |
Set the cluster information for the primary node.
The setting screen 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 | Confirm that the node is "Primary Node". |
Drive | The drive letter corresponding to the physical disk resource is displayed. |
Logical Node Name | Enter the "Logical node name" as defined in "4.1 Confirmation of Customization Items". |
Service Name | Enter the "Transaction name" as defined in "4.1 Confirmation of Customization Items". |
Cluster Name | Enter the "Cluster name" as confirmed in "4.1 Confirmation of Customization Items". |
IP Address Resource | Select "Exist". |
IP Version | Select the IP version of IP address. |
IPv4 Address | Enter the "Logical IP address" as defined in "4.1 Confirmation of Customization Items". |
IPv6 Address | Enter the "Logical IP address" as defined in "4.1 Confirmation of Customization Items". |
Storage Management Server Operation | Select this item. |
Set the port number and service.
The following page is displayed. If the port number and service has already been set, this page is not displayed.
Each item is explained below. Make the required entries and then click OK.
Item | Explanation |
|---|---|
Communication Service | Enter the "Communication service/daemon port number for transaction" as defined in "4.1 Confirmation of Customization Items". |
The following page is displayed. Click OK.
The cluster setup of the primary node has been completed.
When the cluster setup completion window is displayed, click OK.
To manage the ETERNUS DX S2 series, follow the procedure below on the primary node.
Back up the settings file.
Copy the following file to the backup destination directory.
File to be Backed up | Backup Destination Directory |
|---|---|
$INS_DIR\Common\jre\conf\security\java.security | $INS_DIR\Common\sys\tomcat\webapps\esf\WEB-INF\config |
$INS_DIR\CCM\jre\conf\security\java.security | $INS_DIR\CCM\tools |
$INS_DIR is "Program Directory" specified at the ETERNUS SF Manager installation.
Copy the following file over the copy destination file.
Copy Source File | Copy Destination File |
|---|---|
$INS_DIR\Common\sys\tomcat\webapps\esf\WEB-INF\config\java.security.forS2.windows | $INS_DIR\Common\jre\conf\security\java.security |
$INS_DIR\CCM\tools\java.security.forS2.windows | $INS_DIR\CCM\jre\conf\security\java.security |
$INS_DIR is "Program Directory" specified at the ETERNUS SF Manager installation.
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.