This section explains the customization procedure for a secondary node.
This section explains the required procedure for customizing a secondary node for ETERNUS SF Manager.
Setup the starting process of ETERNUS SF Manager to be controlled by cluster software instead of operating system.
Execute the following command on the secondary node.
# ls /etc/rc*.d/*SFmanager* |
Rename all of the files exported by executing the command above.
Add "X" to the start of the file names.
The example for executing command is shown below.
# mv /etc/rc2.d/S99startSFmanager /etc/rc2.d/XS99startSFmanager |
On the secondary node, set up links to the directories on the shared disk for shared data.
Mount the shared disk for shared data and the shared disk for repository for ETERNUS SF Manager in the secondary node.
Change the directory name in reference to step 2 in "5.2.1.1.3 Copying of dynamic disk files".
Set up symbolic links in reference to "5.2.1.1.4 Link setup for shared disk".
Follow the procedure below to prepare a generic script to be used on the secondary node.
Store the generic script file created in "4.1.1 Shared resources" under the ETERNUS SF Manager program directory in the secondary node.
The storage location of the generic script file must be the same path which specified in the primary node.
Customize a secondary node according to the following procedure.
Execute the cluster setup command on the secondary node.
On the secondary node, execute the following cluster setup 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> |
Check the setup object.
Information specified by the command is displayed.
After confirming the displayed information, input "y". The secondary node is set up.
# /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 : 10.10.10.10 Manager cluster setup : Are you sure? [y,n,?] |
To interrupt the cluster environmental setting processing, input "n".
Confirm that the displayed message is as follows:
FJSVrcx:INFO:27701:esc_clsetup:secondary node setup completed |
Create the resources for Storage Cruiser.
Use the cluster software "userApplication Configuration Wizard" to create the following resources in the cluster application (transaction). Then, register them on the cluster application (transaction).
Cmdline resource
Select "Cmdline" for Resource creation in the userApplication Configuration Wizard to create the resources through path input, and make the following configurations.
Type | Input pathname |
|---|---|
Start script | /opt/FJSVssmgr/cluster/cmd/rcxclstartcmd |
Stop script | /opt/FJSVssmgr/cluster/cmd/rcxclstopcmd |
Check script | /opt/FJSVssmgr/cluster/cmd/rcxclcheckcmd |
If the Optimization option is installed, also create the following "Cmdline" resources using the same procedure shown above.
Type | Input pathname |
|---|---|
Start script | /opt/FJSVssast/cluster/cmd/rcxclstartcmd |
Stop script | /opt/FJSVssast/cluster/cmd/rcxclstopcmd |
Check script | /opt/FJSVssast/cluster/cmd/rcxclcheckcmd |
Point
If shared with the operations Management Server or division Management Server for Storage Cruiser's manager, make settings so that Cmdline resources are started after Systemwalker Centric Manager.
See
Refer to the PRIMECLUSTER Installation and Administration Guide for details.
Customize the secondary node.
Follow the procedure below to prepare a generic script to be used on the secondary node.
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".
Set up the access restrictions for the stored generic script file.
Specify the authority that the root user can access.
Customize the secondary node.
Information
This section uses the following values for explanatory purposes:
Value | Description |
|---|---|
$SHARE_MNT | "Mount point" of shared disk for shared data |
For the path name of "$SHARE_MNT", only single-byte alphanumeric characters with no spaces can be used. The path name can be specified with a maximum of 70 characters.
Create backup directories for the AdvancedCopy Manager CCM setup files.
Create the following directories on secondary nodes.
/opt/FJSVccm/noncluster/bin
/opt/FJSVccm/noncluster/micc/sys
/opt/FJSVccm/noncluster/sys
Point
Specify the following values for each directory.
Set "root (super user)" to owner.
Execute chmod command with 755 as the argument to set the access restrictions.
Copy the .install.sys, stxc_install.sys, and sys.properties files.
Copy the following files from the source directories to the destinations on secondary nodes.
Copy source directory | Copy destination directory |
|---|---|
/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 |
Note
The copied files are required for "Chapter 13 Deletion of Cluster Environment for Management Server Transactions".
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 : /opt/FJSVccm/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 : /opt/FJSVccm/bin/.stxc_install.sys
stxc_optdir= (Do not modify these settings!) stxc_etcdir=*2 stxc_jredir= (Do not modify these settings!) |
File name : /opt/FJSVccm/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!) |
Setting item | Setting value | Sample setting |
|---|---|---|
*1 | $SHARE_MNT/var/opt/FJSVccm/micc | /esfmnt/var/opt/FJSVccm/micc |
*2 | $SHARE_MNT/etc/opt/FJSVccm/accc/etc | /esfmnt/etc/opt/FJSVccm/accc/etc |
*3 | $SHARE_MNT/etc/opt/FJSVccm/ | /esfmnt/etc/opt/FJSVccm/ |
*4 | $SHARE_MNT/var/opt/FJSVccm/ | /esfmnt/var/opt/FJSVccm/ |
The sample setting values use "/esfmnt" for $SHARE_MNT.
Register the generic script file for AdvancedCopy Manager CCM created in "4.1.4 Resources required for AdvancedCopy Manager CCM".
See
Refer to the PRIMECLUSTER Installation and Administration Guide for details.
Customize the secondary node.
Prepare the start up/shut down script for AdvancedCopy Manager daemon using on the secondary node, according to the following procedure.
Store the start up/shut down script for AdvancedCopy Manager daemon, which is created in "4.1.3 Resources required for AdvancedCopy Manager's manager", under ETERNUS SF Manager program directory for the secondary node.
Set up the access restrictions for the start up/shut down script for AdvancedCopy Manager daemon.
Specify the authority that the root user can access.
To set up a secondary node, use the procedure below.
Perform "Customization procedure for secondary node" in "A.2.2 Customization Procedure".
Register the start up/shut down script for AdvancedCopy Manager daemon on the cluster application (transaction).
Register the start up/shut down script for AdvancedCopy Manager daemon prepared in "5.2.2.4.1 Preparation for start up/shut down script for AdvancedCopy Manager daemon". Refer to your cluster software manuals for details.
Dismount the shared disk for shared data and the shared disk for repository for ETERNUS SF Manager in the secondary node.
