To delete the cluster environment, use the following procedure:
Delete the node.
Use the Web GUI of the AdvancedCopy Manager to delete the node.
The function of MC/ServiceGuard is used to stop the transaction.
Stop the transaction (package) to be deleted.
Refer to the manual of MC/ServiceGuard for details of the method of stopping the transaction.
Note
If the system is a 1:1 standby system, a mutual standby system or an n:1 standby system, proceed to step 8.
If the system is a Cascade topology, proceed to step 3.
Mount the shared disk on the secondary node B.
The shared disk for share data checks that it is in a state of dismount on the primary node and all the secondary nodes.
Then, Mount the shared disk for shared data on the secondary node B.
Note
When there are two or more secondary nodes B, steps 3 to 7 are executed for all of these nodes.
Execute the cluster unsetup command on the secondary node.
On the secondary node, execute the following command after blocking other users from accessing the shared disk for shared data:
The example of an input:
# /opt/swstorage/bin/stgclunset_mcsg -n nodepr |
Refer to "8.3.5 stgclunset_mcsg (HP edition MC/ServiceGuard environment cancel command)" for command details.
Check the objects to be deleted.
Information about the logical node specified by the command is displayed. Confirm the displayed information, and press the Enter key.
AdvancedCopy Manager settings were 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 Number : 3 MODE : Normal Do you want to continue with un-setting of AdvancedCopy Manager cluster? [default:y] y |
To interrupt cluster environmental unsetup processing, input "n". To continue processing, input "y", or press the Enter key.
Note
The number of nodes which are not executing the cluster unsetup command is output to "Number". In a secondary node B, this value will be at least three.
The cluster unsetup command is executed on the secondary node B.
The window indicating cluster unsetup command completion opens.
swstf8143 The cluster deletion of the secondary node has been completed. Next, delete the cluster environment of another secondary node. # |
Note
In secondary node B, the completion message is swstf8143.
Dismount the shared disks on the secondary node B.
Dismount the shared disk for shared data on the secondary node B.
Note
If there are remaining secondary nodes B for which steps 3 to 7 have not been performed, perform these steps in each node. When steps 3 to 7 have been completed by all secondary nodes B, proceed to Step 8.
Mount the shared disk on the secondary node A.
Mount the shared disk for shared data on the secondary node A.
Execute the cluster unsetup command on the secondary node A.
On the secondary node A, execute the following command after preventing other users from accessing the shared disk for shared data:
Example
# /opt/swstorage/bin/stgclunset_mcsg -n nodepr |
Refer to "8.3.5 stgclunset_mcsg (HP edition MC/ServiceGuard environment cancel command)" for command details.
Check the objects to be deleted.
Information about the logical node specified by the command is displayed. Confirm the displayed information, and press the Enter key.
AdvancedCopy Manager settings were 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 Number : 2 MODE : Normal Do you want to continue with un-setting of AdvancedCopy Manager cluster? [default:y] y |
To interrupt cluster environmental unsetup processing, type "n. To continue processing, type "y" or press the Enter key.
Note
The number of nodes which are not executing the cluster unsetup command is output to "Number". In a secondary node A, this value is likely to be 2.
Finish the cluster unsetup command on the secondary node A.
A window opens, indicating the completion of the cluster unsetup command.
swstf8103 The cluster deletion of the secondary node has been completed. Next, delete the cluster environment of the primary node. # |
Dismount the shared disk on the secondary node A.
Dismount the shared disk for shared data on the secondary node A.
Mount the shared disk on the primary node.
Mount the shared disk for shared data on the primary node.
Execute the cluster unsetup command on the primary node.
On the primary node, execute the following command after blocking other users from accessing the shared disk for shared data:
The example of an input:
# /opt/swstorage/bin/stgclunset_mcsg -n nodepr |
Refer to "8.3.5 stgclunset_mcsg (HP edition MC/ServiceGuard environment cancel command)" for command details.
Check the objects to be deleted.
Information about the logical node specified by the command is displayed. Confirm the displayed information, and press the Enter key.
AdvancedCopy Manager settings were 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 Number : 1 MODE : Normal Do you want to continue with un-setting of AdvancedCopy Manager cluster? [default:y] y |
To interrupt cluster environmental unsetup processing, input "n". To continue processing, input "y", or press the Enter key.
Note
The number of nodes which are not executing the cluster unsetup command is output to "Number". In a primary node, this value is likely to be 1.
The cluster unsetup command is executed on the primary node.
The window indicating cluster unsetup command completion opens.
swstf8102 The cluster deletion of the primary node has been completed. # |
Dismount the shared disk on the primary node.
Dismount the shared disk for share data on the primary node.
Delete port numbers.
On the primary node and the secondary node, delete the following services defined in /etc/services during cluster setup. Use an OS command such as vi to delete the service from /etc/services.
Communication daemon for transactions: stgxfws_Logical-Node-Name
Delete transaction environment.
The start/stop commands of the Storage Server transaction are deleted from the CUSTOMER DEFINE FUNCTIONS section of the package control script of object transaction.
The following commands (the start option is included) are deleted from the section at the time of starting.
/opt/FJSVswstf/cluster/clproc/SmgrMCSG_Logical-Node-Name start |
The following commands (the stop option is included) are deleted from the section at the time of a stop.
/opt/FJSVswstf/cluster/clproc/SmgrMCSG_Logical-Node-Name stop |
When not using in the transaction the shared disk prepared for AdvancedCopy Manager, the information on a shared disk is also deleted. Moreover, the transaction (package) is deleted when the transaction will not be used in the future.
Refer to the manual of MC/ServiceGuard for details of the method of editing a control script, the method of reflection to other nodes, and the method of deleting a package.
Object transaction (package) is started by using the MC/ServiceGuard function.
This carries out this operation and is not required when a transaction is deleted in Procedure 19.
Refer to the manual of MC/ServiceGuard for information about the method of starting a transaction.
