To set up a Storage Management Server transaction and a Storage Server transaction, use the following procedure:
Restart the system.
If the system is restarted as an extension of the installation process of AdvancedCopy Manager, proceed to step 2.
Check the preparations.
Check each item of "3.3 Confirmation of itemss," for the userApplication to be set up.
Mount the shared disk on the primary node.
For a Storage Management Server transaction, mount the shared disk for AdvancedCopy Manager shared data and that for the AdvancedCopy Manager repository on the primary node.
For a Storage Server transaction, mount the shared disk for shared data on the primary node.
Stop the userApplication.
To add a Storage Management Server transaction and a Storage Server transaction to an existing userApplication, use the RMS Wizard to stop the applicable userApplication.
Register port number
Register the port number for the transaction communication in /etc/services. Use an OS command such as vi to register it in /etc/services.
Transaction communication daemon: stgxfws_Logical-Node-Name
Note
Register the same port number on the primary node and the secondary node.
Execute the cluster setup command on the primary node.
For a Storage Management Server transaction, on the primary node, execute the cluster setup command shown below after blocking other users from accessing the shared disk for shared data and that for the repository. When this command is executed, a repository is created in addition to the cluster being set up. For more information, see the chapter on database creation.
If status transition procedure resources are used:
Example
# /opt/swstorage/bin/stgclset_lxprm -k Primary -m /STGMGRDISK -n nodeMGR -s manager_service -i 10.10.10.10 -f mgr |
If command line resources are used:
Example
# /opt/swstorage/bin/stgclset_lxprm -k Primary -m /STGMGRDISK -n nodeMGR -s manager_service -i 10.10.10.10 -f mgr -r cmd |
Note
For a Storage Management Server transaction to be performed, use the same location specified during Storage Management Server installation.
In combined operation with the scalable class, the IP address for a Storage Management Server transaction specified with the -i option must be the "takeover IP address for AdvancedCopy Manager" prepared for the Storage Management Server transaction. Do not specify the logical IP address of the transaction in the scalable class.
For a Storage Management Server transaction, on the primary node, execute the following cluster setup command after blocking other users from accessing the shared disk for shared data:
If status transition procedure resources are used:
Example
# /opt/swstorage/bin/stgclset_lxprm -k Primary -m /CTTEST3 -n nodeAGT -s agent_service |
If command line resources are used:
Example
# /opt/swstorage/bin/stgclset_lxprm -k Primary -m /CTTEST3 -n nodeAGT -s agent_service -r cmd |
Refer to "8.2.4 stgclset_lxprm (Linux edition PRIMECLUSTER environment setup command)" for command details.
Check the setup object.
Information about the logical node specified by the command is displayed. After confirming the displayed information, press the Enter key.
For a Storage Management Server transaction (using status transition procedure resources):
# /opt/swstorage/bin/stgclset_lxprm -k Primary -m /STGMGRDISK -n nodeMGR -s manager_service -i 10.10.10.10 -f mgr
AdvancedCopy Manager settings are as follows.
Cluster system : PRIMECLUSTER
Node type : Primary
IP Address : 10.10.10.10
Mount point : /STGMGRDISK
Node name : nodeMGR
Service : manager_service
Resource : Procedure
Function : Management Server
Do you want to continue with setting of AdvancedCopy Manager cluster? [default:y] |
For a Storage Server transaction (using command line resources):
# /opt/swstorage/bin/stgclset_lxprm -k Primary -m /CTTEST3 -n nodeAGT -s agent_service -r cmd
AdvancedCopy Manager settings are as follows.
Cluster system : PRIMECLUSTER
Node type : Primary
Mount point : /CTTEST3
Node name : nodeAGT
Service : agent_service
Resource : CmdLine
Function : Server
Do you want to continue with setting of AdvancedCopy Manager cluster? [default:y] |
To interrupt cluster environmental setting processing, input "n". To continue processing, input "y", or press the Enter key.
Note
If the transaction is the Storage Management Server transaction, proceed to step 8.
If the transaction is the Storage Server transaction, proceed to step 13.
Start the creation of a common environment for Storage Management Server transactions.
The initial window for setting the common environment opens. Confirm the displayed information, enter "y", and press the Enter key.
+----------------------------------------------------------------+
| A common environment for the AdvancedCopy Manager |
| Storage Management Server will be created. |
| [Notes] |
| Prepare the following directories before starting processing.|
| ============================================================== |
| |
| 1) Directory for the DB file |
| 2) Directory for the RDB dictionary |
| 3) Directory for the RDB log file |
| 4) Directory for the DB space to store the repository data |
| |
+----------------------------------------------------------------+
Do you want to continue with processing? [y/n] ==> y |
For a Storage Management Server transaction, specify the DB device.
The window shown below opens. Enter the directory name for the DB file system according to the information in [Notes], and press the Enter key.
-----------------------< DB device setting >----------------------
Enter the directory name for the DB file.
[Notes]
Enter the absolute path name of the directory.
Enter ==> /ACMMnt/Vol202/DBFile |
A similar setting window opens for input of the directory names for the RDB dictionary, RDB log file, and the DB space where repository data is stored. Enter a directory name for each item, and press the Enter key after each entry.
After setting up the directory name for DB space where repository data is stored, the setting window for inputting the size of repository data is opened. Enter the size of repository data, and press the Enter key.
For a Storage Management Server transaction, check the DB directory settings.
The four directory names and the size of repository data specified in step 9 are displayed. Confirm the displayed information, enter "y", and press the Enter key.
=================================================================================
Directory name for the DB file ............................./ACMMnt/Vol202/DBFile
Directory name for the RDB dictionary ....................../ACMMnt/Vol203/DBDic
Directory name for the RDB log file ......................../ACMMnt/Vol204/DBLog
Directory name for the DB space for saving repository data ....../ACMMnt/Vol205/DBSpa
Repository data Size ....................................... 65MB
================================================================================
Okay? [y/n] ==> y |
For a Storage Management Server transaction, confirm the continuation of processing.
After the window for confirming the continuation of processing opens, enter "y", and press the Enter key.
+----------------------------------------------------------------+
| Creation of the AdvancedCopy Manager Storage management |
| server environment will start. |
| ============================================================== |
| |
| Once processing has started, system information is rewritten.|
| Make sure that the environment allows execution |
| before proceeding. |
| |
+----------------------------------------------------------------+
Do you want to continue with processing? [y/n] ==> y |
For a Storage Management Server transaction, perform the repository access settings.
The window for setting repository access opens. Enter a user name and password, and press the Enter key.
Point
For security reasons, it is recommended to log on as a general user and not a root user which has frequent password changes.
Enter the user name and password for accessing
the repository of AdvancedCopy Manager.
[Notes]
We recommend you to input a general user other than root.
Username : acmuser
Password :
Password(Re-enter) : |
Note
If user settings were entered as shown above, and the user is deleted or the password is changed from the operating system, perform the setup processing again. Refer to "User deletion or password change in repository access user settings" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide (Linux)".
Finish the cluster setup command on the primary node.
The window indicating password registration and cluster setup command completion opens.
swstf8100 The cluster setup of the primary node has been completed. Next, create the cluster environment of the secondary node. # |
Dismount the shared disks on the primary node.
For a Storage Management Server transaction, dismount the shared disk for shared data and the one for the repository on the primary node.
For a Storage Server transaction, dismount the shared disk for shared data on the primary node.
Mount the shared disks on the secondary node A.
For a Storage Management Server transaction, mount the shared disk for shared data and the one for the repository on the secondary node A.
For a Storage Server transaction, mount the shared disk for shared data on the secondary node A.
Execute the cluster setup command on the secondary node A.
For a Storage Management Server transaction, on the secondary node A, execute the cluster setup command shown below after blocking other users from accessing the shared disk for shared data and that for the repository. When this command is executed, a repository is created in addition to the cluster being set up. For more information, see the chapter on database creation.
For a Storage Server transaction, on the secondary node A, execute the following
Cluster setup command after blocking other users from accessing the shared disk for shared data:
Example
# /opt/swstorage/bin/stgclset_lxprm -k Secondary -m /STGMGRDISK |
Refer to "8.2.4 stgclset_lxprm (Linux edition PRIMECLUSTER environment setup command)" for command details.
Note
For a Storage Management Server transaction to be performed, use the locale that is specified when the Storage Management Server is installed.
Check the setup object.
Information about the logical node specified by the command is displayed. After confirming the displayed information, press the Enter key.
For a Storage Management Server transaction:
# /opt/swstorage/bin/stgclset_lxprm -k Secondary -m /STGMGRDISK
AdvancedCopy Manager settings are as follows.
Cluster system : PRIMECLUSTER
Node type : Secondary
IP Address : 10.10.10.10
Mount point : /STGMGRDISK
Node name : nodeMGR
Service : manager_service
Resource : Procedure
Function : Management Server
Do you want to continue with setting of AdvancedCopy Manager cluster? [default:y] |
For a Storage Server transaction:
# /opt/swstorage/bin/stgclset_lxprm -k Secondary -m /CTTEST3
AdvancedCopy Manager settings are as follows.
Cluster system : PRIMECLUSTER
Node type : Secondary
Mount point : /CTTEST3
Node name : nodeAGT
Service : agent_service
Resource : CmdLine
Function : Server
Do you want to continue with setting of AdvancedCopy Manager cluster? [default:y] |
To interrupt cluster environmental setting processing, input "n". To continue processing, input "y", or press the Enter key.
Note
If the transaction is the Storage Management Server transaction, proceed to step 18.
If the transaction is the Storage Server transaction, proceed to step 19.
Start the creation of a common environment for AdvancedCopy Manager management server transactions.
After the window for confirming the continuation of processing opens, enter "y", and press the Enter key.
+----------------------------------------------------------------+
| Creation of the AdvancedCopy Manager Storage management |
| server environment will start. |
| ============================================================== |
| |
| Once processing has started, system information is rewritten.|
| Make sure that the environment allows execution |
| before proceeding. |
| |
+----------------------------------------------------------------+
Do you want to continue with processing? [y/n] ==> y |
Finish the cluster setup command on the secondary node A.
The window indicating cluster setup command completion opens.
swstf8101 The cluster setup of the secondary node has been completed. # |
Dismount the shared disks on the secondary node A.
For a Storage Management Server transaction, dismount the shared disk for shared data and that for the repository on the secondary node A.
For a Storage Server transaction, dismount the shared disk for share data on the secondary node A.
Note
If the system is the 1:1 standby system, the Mutual standby system and the n:1 standby system, proceed to step 28.
If the system is a Cascade topology or Priority transfer, proceed to step 21.
Mount the shared disks on the secondary node B.
For a Storage Management Server transaction, mount the shared disk for shared data and that for the repository on the secondary node B.
For a Storage Server transaction, mount the shared disk for shared data on the secondary node B.
Note
When there are two or more secondary nodes B, Step 21 to Step 27 is processed by all the secondary nodes B.
Execute the cluster setup command on the secondary node B.
For a Storage Management Server transaction, on the secondary node B, execute the cluster setup command shown below after blocking other users from accessing the shared disk for shared data and that for the repository. When this command is executed, a repository is created in addition to the cluster being set up. For more information, see the chapter on database creation.
For a Storage Server transaction, on the secondary node B, execute the following cluster setup command after blocking other users from accessing the shared disk for shared data:
Example
# /opt/swstorage/bin/stgclset_lxprm -k Secondary -m /STGMGRDISK |
Refer to "8.2.4 stgclset_lxprm (Linux edition PRIMECLUSTER environment setup command)" for command details.
Note
For a Storage Management Server transaction to be performed, use the location that is specified when the Storage Management Server is installed.
Check the setup object.
Information about the logical node specified by the command is displayed. After confirming the displayed information, press the Enter key.
For a Storage Management Server transaction:
# /opt/swstorage/bin/stgclset_lxprm -k Secondary -m /STGMGRDISK
AdvancedCopy Manager settings are as follows.
Cluster system : PRIMECLUSTER
Node type : Secondary
IP Address : 10.10.10.10
Mount point : /STGMGRDISK
Node name : nodeMGR
Service : manager_service
Resource : Procedure
Function : Management Server
Do you want to continue with setting of AdvancedCopy Manager cluster? [default:y] |
For a Storage Server transaction:
# /opt/swstorage/bin/stgclset_lxprm -k Secondary -m /CTTEST3
AdvancedCopy Manager settings are as follows.
Cluster system : PRIMECLUSTER
Node type : Secondary
Mount point : /CTTEST3
Node name : nodeAGT
Service : agent_service
Resource : CmdLine
Function : Server
Do you want to continue with setting of AdvancedCopy Manager cluster? [default:y] |
To interrupt cluster environmental setting processing, input "n". To continue processing, input "y", or press the Enter key.
Check the addition of a secondary node.
The window for confirming the addition of a secondary node is displayed.
After confirmation of a cascade, "y" is inputted and the Enter key is pushed.
Secondary node is already setup in another node.
The number of secondary nodes : 1
Do you want to setup new secondary node? [default:n] y |
The number of secondary nodes already set up is outputted to "The number of secondary nodes."
Note
The default value is "n." "n" means cancellation of processing.
If the transaction is the Storage Management Server transaction, proceed to step 25.
If the transaction is the Storage Server transaction, proceed to step 26.
Start the creation of a common environment for AdvancedCopy Manager management server transactions.
The initial window for setting the common environment opens. Confirm the displayed information, enter "y", and press the Enter key.
+----------------------------------------------------------------+
| Creation of the AdvancedCopy Manager Storage management |
| server environment will start. |
| ============================================================== |
| |
| Once processing has started, system information is rewritten.|
| Make sure that the environment allows execution |
| before proceeding. |
| |
+----------------------------------------------------------------+
Do you want to continue with processing? [y/n] ==> y |
Finish the cluster setup command on the secondary node B.
The window indicating cluster setup command completion opens.
swstf8101 The cluster setup of the secondary node has been completed. # |
Dismount the shared disks on the secondary node B.
For a Storage Management Server transaction, dismount the shared disk for shared data and that for the repository on the secondary node B.
For a Storage Server transaction, dismount the shared disk for share data on the secondary node B.
Note
When any secondary nodes B remain (those that haven't performed Step 21 to Step 27), perform from Step 21 in the nodes. When operation from Step 21 to Step 27 is completed for all secondary nodes B, go to Step 28.
Create the userApplication and resources.
On both the primary node and the secondary node, set up "logical IP takeover of the NIC switching mode" of GLS. When using the existing GLS, this setup of GLS is unnecessary.
On either the primary node or the secondary node, use the RMS Wizard to create a userApplication and the following resources.
GDS resource
For a Storage Management Server transaction, register the class of the shared disk for shared data and the class of the shared disk for the repository.
For a Storage Server transaction, register the class of the shared disk for shared data.
Fsystem resource
For Storage Management Server transaction, register the mount point of the shared disk for shared data and the mount point of the shared disk with the directory for the repository.
For Storage Server transaction, register the mount point of the shared disk for shared data.
GLS resource
This resource is not necessary if a GLS resource has already been created by the applicable userApplication.
Procedure resource
Specify if procedure resources are used.
Register "SMGRPROC_Logical-Node-Name" into an Application class.
Command line resource
Specify if command line resources are used.
Set the following values in each of the command line resource parameters:
Start script
/opt/FJSVswstf/cluster/clproc/acm_logical-node-name start
Stop script
/opt/FJSVswstf/cluster/clproc/acm_logical-node-name stop
Note
For information on how to set GLS, refer to "PRIMECLUSTER Installation and Administration Guide" and either "PRIMECLUSTER Global Link Services Configuration and Administration Guide (Redundant Line Control Function)"or "PRIMECLUSTER Global Link Services Configuration and Administration Guide (Multipath Function)".
For information on how to create resources and userApplications with PRIMECLUSTER, see "Appendix B Creating Resources and userApplications with Linux-version PRIMECLUSTER".
The cluster setup command (8.2.4 stgclset_lxprm (Linux edition PRIMECLUSTER environment setup command)) has already made the preparatory settings (ie, creating a state transition procedure and storing resources in the resource database) that are defined to set PRIMECLUSTER procedure resources.
Do not specify anything in the command line resource check script.
Start the userApplication and the AdvancedCopy Manager.
Use the RMS Wizard to start the new userApplication or the userApplication stopped in step 4.
Back up the environment.
To guard against accidental deletion or corruption of data, back up the following environments.
Database
For a Storage Management Server transaction, refer to "Saving a database," in the "ETERNUS SF AdvancedCopy Manager Operations Guide (Linux)", and back up the created database area.
Data on the shared disk for shared data
Use the OS command such as cp to back up the following directories on the shared disk for shared data:
Mountpoint-of-shared-disk-for-AdvancedCopy-Manager-shared-data/etc
Mountpoint-of-shared-disk-for-AdvancedCopy-Manager-shared-data/var
Create an environment for a Storage Management Server transaction and a Storage Server transaction.
Use the Web GUI of AdvancedCopy Manager to create an environment for a Storage Management Server transaction and a Storage Server transaction.
In the case of a Storage Management Server transaction that acts as a Storage Server transaction, also create an environment for the Storage Server transaction.
Note
Refer to the "ETERNUS SF AdvancedCopy Manager Operator's Guide (Linux)", and create the environment for a Storage Management Server transaction and a Storage Server transaction.
