To delete the cluster environment, use the following procedure:
Delete the node.
Use the Web GUI of the AdvancedCopy Manager to delete the node. For a Storage Management Server transaction, however, this operation is not necessary.
Stop the userApplication.
Use the RMS main window of PRIMECLUSTER to stop the transaction to be deleted.
Delete resources.
Use the RMS Wizard to delete the AdvancedCopy Manager resources registered for the target transaction. If the userApplication has been created using only AdvancedCopy Manager resources, delete the whole userApplication.
Point
For information on how to delete the userApplication and resources, see the "PRIMECLUSTER Installation and Administration Guide."
Note
If the system is a 1:1 standby system, a Mutual standby system or a n:1 standby system, proceed to step 10.
If the system is a Cascade topology or a Priority transfer, proceed to step 4.
Mount the shared disk on the secondary node B.
Mount the shared disk for shared data on the secondary node B.
For a Storage Management Server transaction, also mount the shared disk for repository in the secondary node B.
Note
When there are two or more secondary nodes B, Step 4 to Step 9 is processed by all the secondary nodes B.
Execute the cluster unsetup command on the secondary node B.
On the secondary node B, execute the following command after blocking other users from accessing the shared disk for shared data:
[Input example]
# /opt/swstorage/bin/stgclunset_lxprm -n nodeMGR |
Refer to "8.3.4 stgclunset_lxprm (Linux edition PRIMECLUSTER environment cancel command)" for command details.
Note
For a Storage Management Server transaction to be performed, use the location that was specified when the Storage Management Server was installed.
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.
# /opt/swstorage/bin/stgclunset_lxprm -n nodeMGR
AdvancedCopy Manager settings were as follows.
Cluster system : PRIMECLUSTER
Node type : Secondary
IP Address : 10.10.10.10 (In the case of Storage Server transaction, it is not displayed.)
Mount point : /STGMGRDISK
Node name : nodeMGR
Service : manager_service
Resource : Procedure
Function : Management Server (In the case of Storage Server transaction, it is displayed as Server.)
Number : 3
MODE : Normal
Do you want to continue with un-setting of AdvancedCopy Manager cluster? [default:y] |
To interrupt cluster environmental unsetup processing, input "n". To continue processing, input "y", or press the Enter key.
Note
The number of nodes that are not carrying out the cluster unsetup command is outputted to "NUMBER". In a secondary node B, it is likely to be three or more.
For a Storage Management Server transaction, delete the database.
A window for confirming database deletion opens. Confirm the displayed information, enter "y", and press the Enter key. The window is not displayed in the case of a Storage Server transaction.
+----------------------------------------------------------------+
| |
| All of database environments of AdvancedCopy Manager |
| will be deleted. |
| |
| [Notes] |
| Once processing has started, all stored data is discarded. |
| Make sure that the environment allows execution |
| before proceeding. |
| |
+----------------------------------------------------------------+
Do you want to continue with processing? [y/n] ==> y |
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, a completion message is swstf8143.
Dismount the shared disk on the secondary node B.
Dismount the shared disk for share data on the secondary node B.
For a Storage Management Server transaction, also dismount the shared disk for the repository on the secondary node B.
Note
If there are remaining secondary nodes B for which steps 4 to 9 have not been performed, perform from Step 4 for the nodes.
When operation from Step 4 to Step 9 is completed by all secondary nodes B, go to Step 10.
Mount the shared disk on the secondary node A.
Mount the shared disk for shared data on the secondary node A.
For a Storage Management Server transaction, also mount the shared disk for the repository in the secondary node A.
Execute the cluster unsetup command on the secondary node A.
On the secondary node A, execute the following command after blocking other users from accessing the shared disk for shared data:
[Input example]
# /opt/swstorage/bin/stgclunset_lxprm -n nodeMGR |
Refer to "8.3.4 stgclunset_lxprm (Linux edition PRIMECLUSTER environment cancel command)" for command details.
Note
For a Storage Management Server transaction to be performed, use the location that was specified when the Storage Management Server was installed.
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.
# /opt/swstorage/bin/stgclunset_lxprm -n nodeMGR
AdvancedCopy Manager settings were as follows.
Cluster system : PRIMECLUSTER
Node type : Secondary
IP Address : 10.10.10.10 (In the case of Storage Server transaction, it is not displayed.)
Mount point : /STGMGRDISK
Node name : nodeMGR
Service : manager_service
Resource : Procedure
Function : Management Server (In the case of Storage Server transaction, it is displayed as Server.)
Number : 2
MODE : Normal
Do you want to continue with un-setting of AdvancedCopy Manager cluster? [default:y] |
To interrupt cluster environmental unsetup processing, input "n" To continue processing, input "y", or press the Enter key.
Note
The number of nodes that are not carrying out cluster unsetup command is outputted to "NUMBER". In a secondary node, it is surely set to 2.
For a Storage Management Server transaction, delete the database.
A window for confirming database deletion opens. Confirm the displayed information, enter "y", and press the Enter key. The window is not displayed in the case of a Storage Server transaction.
+----------------------------------------------------------------+
| |
| All of database environments of AdvancedCopy Manager |
| will be deleted. |
| |
| [Notes] |
| Once processing has started, all stored data is discarded. |
| Make sure that the environment allows execution |
| before proceeding. |
| |
+----------------------------------------------------------------+
Do you want to continue with processing? [y/n] ==> y |
The cluster unsetup command is executed on the secondary node A.
The window indicating cluster unsetup command completion opens.
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 share data on the secondary node A.
For a Storage Management Server transaction, also dismount the shared disk for the repository on the secondary node A.
Mount the shared disk on the primary node.
Mount the shared disk for shared data on the primary node.
For a Storage Management Server transaction, also mount the shared disk for the repository 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:
[Input example]
# /opt/swstorage/bin/stgclunset_lxprm -n nodeMGR |
Refer to "8.3.4 stgclunset_lxprm (Linux edition PRIMECLUSTER environment cancel command)" for command details.
Note
For a Storage Management Server transaction to be performed, use the location that was specified when the Storage Management Server was installed.
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.
# /opt/swstorage/bin/stgclunset_lxprm -n nodeMGR
AdvancedCopy Manager settings were as follows.
Cluster system : PRIMECLUSTER
Node type : Primary
IP Address : 10.10.10.10 (In the case of Storage Server transaction, it is not displayed.)
Mount point : /STGMGRDISK
Node name : nodeMGR
Service : manager_service
Resource : Procedure
Function : Management Server (In the case of Storage Server transaction, it is displayed as Server.)
Number : 1
MODE : Normal
Do you want to continue with un-setting of AdvancedCopy Manager cluster? [default:y] |
To interrupt cluster environmental unsetup processing, input "n" To continue processing, input "y", or press the Enter key.
Note
The number of nodes that are not carrying out cluster unsetup command is outputted to "NUMBER". In a primary node, it will be set to 1.
For a Storage Management Server transaction, delete the database.
A window for confirming database deletion opens. Confirm the displayed information, enter "y", and press the Enter key. The window is not displayed in the case of a Storage Server transaction.
+----------------------------------------------------------------+
| |
| All of database environments of AdvancedCopy Manager |
| will be deleted. |
| |
| [Notes] |
| Once processing has started, all stored data is discarded. |
| Make sure that the environment allows execution |
| before proceeding. |
| |
+----------------------------------------------------------------+
Do you want to continue with processing? [y/n] ==> y |
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.
For a Storage Management Server transaction, also dismount the shared disk for the repository on the primary node.
Delete port numbers.
Delete the following services defined in /etc/services during cluster setup. Delete the services on the primary node and the secondary node. Use an OS command such as vi to delete the service from /etc/services.
Communication daemon for transactions: stgxfws_Logical-Node-Name
Start the userApplication.
Use the RMS main window of PRIMECLUSTER to start the transaction stopped in step 2. This operation is not necessary if the userApplication was deleted in step 3.
