To set up a Storage Server transaction, use the procedure below.
Restart the system.
Restart the primary node and secondary node. If the system is restarted as an extension of the installation process of AdvancedCopy Manager, proceed to step 2.
The transaction environment is checked or created by using the MC/ServiceGuard function.
Please refer to the manual of MC/ServiceGuard for information about the checking method of a package, as well as the creation method.
The Transactions (package) which adds Storage Server Transactions is checked. In the case of new Transactions, it checks that a package is created, a package is started and a package can move between nodes.
Check the preparations.
Check each item in "3.3 Confirmation of items" for the package to be set up.
Stop the transaction by using the MC/ServiceGuard function.
Stop the target transaction (stop a package).
Please refer to the manual of MC/ServiceGuard for information about the method of stopping the transaction.
Mount the shared disk on the primary node.
The shared disk for share data checks that it is in a state of dismount on the primary node and the secondary node.
Then, Mount the shared disk for shared data on the primary node.
Register port numbers.
Register the port number for the transaction communication daemon in /etc/services.
Use the 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.
On the primary node, execute the following cluster setup command after blocking other users from accessing the shared disk for shared data:
The example of an input:
# /opt/swstorage/bin/stgclset_mcsg -k Primary -m /stgmount -n nodepr -s serv1 -v vg01 -i 10.10.10.10 -u 10.10.10.0 |
Refer to "8.2.5 stgclset_mcsg (HP edition MC/ServiceGuard environment setup command)" for command details.
Check the setup object.
Information on the logical node specified by the command is displayed. After the displayed content is confirmed press the Enter key.
AdvancedCopy Manager settings are as follows. Cluster system : MC/ServiceGuard Node type : Primary IP Address : 10.10.10.10 SUBNET : 10.10.10.0 Mount point : /stgmount Device Name : /dev/vg01/lvol1 Volume Group : vg01 Node name : nodepr Service : serv1 Function : Server Do you want to continue with setting of AdvancedCopy Manager cluster? [default:y] y |
It asks whether to continue the setting processing.
To interrupt cluster environmental setting processing, input "n". To continuing processing, input "y", or press the Enter key.
Completed the setup command on the primary node.
The completion screen of the cluster setup command is displayed.
swstf8100 The cluster setup of the primary node has been completed. Next, create the cluster environment of the secondary node. # |
Dismount the shared disk on the primary node.
Dismount the shared disk for share data on the primary node.
Mount the shared disk on the secondary node A.
Mount the shared disk for shared data on the secondary node A.
Execute the cluster setup command on the secondary node A.
On the secondary node A, execute the following cluster setup command after blocking other users from accessing the shared disk for shared data:
The example of an input:
# /opt/swstorage/bin/stgclset_mcsg -k Secondary -m /stgmount |
Refer to "8.2.5 stgclset_mcsg (HP edition MC/ServiceGuard environment setup command)" for command details.
Check the setup object.
Information on the logical node specified by the command is displayed. After the displayed content is confirmed press the Enter key.
AdvancedCopy Manager settings are as follows. Cluster system : MC/ServiceGuard Node type : Secondary IP Address : 10.10.10.10 SUBNET : 10.10.10.0 Mount point : /stgmount Device Name : /dev/vg01/lvol1 Volume Group : vg01 Node name : nodepr Service : serv1 Function : Server Do you want to continue with setting of AdvancedCopy Manager cluster? [default:y] y |
It asks whether continue setting processing.
To interrupt cluster environmental setting processing, input "n". To continue processing, input "y", or press the Enter key.
Completed the setup command on the secondary node A.
The completion screen of the cluster setup command is displayed.
swstf8101 The cluster setup of the secondary node has been completed. # |
Dismount the shared disk on the secondary node A.
Dismount the shared disk for AdvancedCopy Manager share data on the secondary node A.
Note
If the system is a 1:1 standby system, a mutual standby system or an n:1 standby system, proceed to step 22.
If the system is Cascade topology, proceed to step 16.
Mount the shared disk on the secondary node B where the cluster setup command will be executed.
Mount the shared disk shared data on the secondary node B.
Note
When there are two or more secondary nodes B, Step 16 to Step 21 is processed for all the secondary nodes B.
Execute the cluster setup command on the secondary node B.
Execute the cluster setup command on the secondary node B on which the shared disk for AdvancedCopy Manager was mounted in step 16.
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_mcsg -k Secondary -m /stgmount |
Refer to "8.2.5 stgclset_mcsg (HP edition MC/ServiceGuard 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.
AdvancedCopy Manager settings are as follows. Cluster system : MC/ServiceGuard Node type : Secondary IP Address : 10.10.10.10 SUBNET : 10.10.10.0 Mount point : /stgmount Device Name : /dev/vg01/lvol1 Volume Group : vg01 Node name : nodepr Service : serv1 Function : Server Do you want to continue with setting of AdvancedCopy Manager cluster? [default:y] y |
A message displays, asking whether to continue the setup processing. To interrupt cluster environmental setting processing, type "n", to continue processing, type "y" or press the Enter key.
Check the addition of a secondary node.
The confirmation window for adding a secondary node is displayed. After confirming the cascade, type "y" and press the Enter key.
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 output to "The number of secondary nodes."
Note
The default value is "n", which indicates cancellation of processing.
Finish the cluster setup command on the secondary node B.
A window displays, indicating that the cluster setup command is complete.
swstf8101 The cluster setup of the secondary node has been completed. # |
Dismount the shared disks on the secondary node B.
Dismount the shared disk for share data on the secondary node B.
Note
If there are remaining secondary nodes B for which steps 16 to 21 have not been performed, perform these steps in each node. When steps 16 to 21 have been completed by all secondary nodes B, proceed to Step 22.
Edit and register package information.
When business is newly created in Procedure 2, the sample control script created by the cluster environmental setting command is copied to the control script of a package.
When resources other than AdvancedCopy Manager are set as the package control script (AdvancedCopy Manager was added to the existing business), with reference to the sample control script created by the cluster environmental setting command, the information on AdvancedCopy Manager is set as the existing control script.
The information on AdvancedCopy Manager in a sample control script can be searched with "AdvancedCopy Manager."
MC/ServiceGuard A.11.13 sample control script: /var/opt/swstorage/cluster/samp_Logical-Node-Name.sh.
Serviceguard A.11.17 sample control script:
/var/opt/swstorage/cluster/samp1117_Logical-Node-Name.sh.
The default timeout value for a daemon to stop in AdvancedCopy Manager is 300 seconds. When the timeout value is set up by the package configuration file, it should be checked that the timeout value is enough.
After replacing/editing a package control script, verification of a package composition file, registration, and checking are carried out.
Refer to the manual on MC/ServiceGuard for the method of verification of a package configuration file, registration, and checking.
Start the transaction by using the MC/ServiceGuard function.
Start the transaction that was stopped in step 4. (the package should be switched to on-line.)
Please refer to the manual of MC/ServiceGuard for information about the method of starting the transaction.
Back up the environment.
As a safeguard against accidental loss of data, back up the following environments.
Data on the shared disk for shared data
Use an 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 Server transaction.
Use the Web GUI of AdvancedCopy Manager to create an environment for a Storage Server transaction.
Note
Create an environment for a Storage Server transaction with reference to the "ETERNUS SF AdvancedCopy Manager Operator's Guide" that is applicable to the Storage Management Server OS.
If the Storage Management Server runs in Solaris
"ETERNUS SF AdvancedCopy Manager Operator's Guide (Solaris)"
If the Storage Management Server runs in Windows
"ETERNUS SF AdvancedCopy Manager Operator's Guide (Windows)"
If the Storage Management Server runs in Linux
"ETERNUS SF AdvancedCopy Manager Operator's Guide (Linux)"
