Use the following procedure to delete the cluster environment:
Delete the node
Delete the node using the AdvancedCopy Manager Web GUI. This step is not required for Storage Management Server transactions.
If also used as a Storage Server, perform the steps below before deleting the cluster environment.
Refer to "Commands" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide for Tape Backup Option" for command details.
The deletion procedure depends on the type of device being deleted. The deletion procedures for each device type are explained below.
Deleting a transaction volume
Use the following procedures to delete a transaction volume. Ensure that that these procedures are performed before the targeted transaction volume is removed.
Delete the tape backup management class.
Execute acmtpmgmtclassdel (Ttape backup management class deletion command).
Refer to "acmtpmgmtclassdel (Tape backup management class deletion command)" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide for Tape Backup Option" for details.
Execute acmhistdel (history information deletion command) to delete all the backup history of the transaction volume that is targeted for deletion.
A command execution example is shown below.
# /opt/FJSVswstc/bin/acmhistdel -z /dev/dsk/c1t1d0s6 /dev/dsk/c1t1d0s6 acmhistdel completed # |
Execute acmbkpoldel (Disk backup policy delete command) and acmtpbkpoldel (Tape backup policy delete command) to delete the backup policies of the transaction volume that is targeted for deletion.
An example of executing these commands is shown below.
# /opt/FJSVswstc/bin/acmbkpoldel /dev/dsk/c1t1d0s6 /dev/dsk/c1t1d0s6 acmbkpoldel completed # # /opt/FJSVswstc/bin/acmtpbkpoldel /dev/dsk/c1t1d0s6 /dev/dsk/c1t1d0s6 acmtpbkpoldel completed # |
Execute acmdevinfoset (Device Configuration command) to delete the device information of the transaction volume that is targeted for deletion.
A command execution example is shown below.
# /opt/FJSVswstc/bin/acmdevinfoset -o /dev/dsk/c1t1d0s6 acmdevinfoset completed # |
Deleting a backup volume
Take the steps below to delete a backup volume. Note that it is essential to perform these steps before removing the targeted backup volume.
Delete the tape backup management class.
Execute acmtpmgmtclassdel (Tape backup management class delete command).
Refer to "acmtpmgmtclassdel (Tape backup management class deletion command)" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide for Tape Backup Option" for details.
Set the not-in-use status for the backup volume that is targeted for deletion.
The not-in-use status for a volume means that the relevant volume does not exist in the backup history. If the volume is in the backup history, delete the backup history. If the same backup history also exists on tape, the history on tape does not need to be deleted. Refer to acmhistdel (History information delete command) for details. If the volume already has the not-in-use status, proceed to the next step.
A command execution example is shown below.
# /opt/FJSVswstc/bin/acmhistdel -m DISK -g 1 /dev/dsk/c1t1d0s6 /dev/dsk/c1t1d0s6 acmhistdel completed # |
Execute acmdevinfoset (Device Configuration command) to delete the device information of the backup volume that is targeted for deletion.
A command execution example is shown below.
# /opt/FJSVswstc/bin/acmdevinfoset -o /dev/dsk/c1t2d1s6 acmdevinfoset completed # |
Note
When a backup volume is deleted, a backup policy that is already set may no longer be met (for example, the number of backup volumes may be less than the required number of saved generations). In this case, subsequent backup operations may not be possible. Therefore, it is essential to check the backup policies that have already been set before deleting a backup volume.
If, as described above, there will be insufficient backup volumes, add a replacement backup volume before deleting the targeted backup volume.
Stop transactions
Stop the transactions that are to be deleted using the PRIMECLUSTER RMS main window
Delete resources
Use the PRIMECLUSTER "userApplication Configuration Wizard" to delete the AdvancedCopy Manager resources and TSM resources registered for the transactions to be deleted. If the userApplication has been created using only AdvancedCopy Manager resources, delete the entire userApplication
Note
Refer to the PRIMECLUSTER Installation and Administration Guide for information on how to delete userApplications and resources
Mount the shared disk on the secondary node
Mount the shared disk for AdvancedCopy Manager shared data on the secondary node.
If the same server is used for both a Storage Management Server transaction and a Tape Server transaction, mount the shared disk for the repository as well.
Cancel the TSM cluster settings.
On the secondary node, execute the PRIMECLUSTER environment deletion procedure by referring to "Deleting the TSM server cluster environment" under "Canceling Applications" in the "TSM PRIMECLUSTER Application Guide".
Use the procedure below to delete the PRIMECLUSTER environment:
# cd shared disk mount point for TSM/tsm/cluster # ./tsmclunset_safe -k Sec -m shared disk mount point for TSM |
Note
Do not delete environment for the primary node.
Execute the cluster unsetup command for the Tape Server transaction on the secondary node
# /opt/swstorage/bin/tboclunset_lxprm -n logical node name |
Check the deletion target
Information will be displayed about the logical node specified with the command. Check the information that is displayed, and then press the Enter key
# /opt/swstorage/bin/tboclunset_lxprm -n nodeMGR
AdvancedCopy Manager Tape Server settings were as follows.
Cluster system : PRIMECLUSTER
Node type : Secondary
Mount point : /STGMGRDISK
Node name : nodeMGR
Function : Tape Server
Do you want to continue with un-setting of AdvancedCopy Manager Tape Server cluster? [default:y] |
Enter "n" to cancel the cluster environment deletion, or type "y" or press the Enter key to continue with the deletion
The cluster unsetup command on the secondary node will complete
The completion screen for the cluster unsetup command will be displayed
swstm 2003 The Tape Server cluster deletion of the secondary node has been completed. Next, delete the cluster environment of the primary node. # |
Note
When the unsetup command completes, a message will display suggesting that the cluster environment be canceled on the primary node. However, you should go on to execute the cluster unsetup command for the Storage Management Server transaction or the Storage Server transaction on the secondary node.
On the secondary node, execute the cluster unsetup command for the Storage Management Server transaction or the Storage Server transaction
Perform steps 11 to 14 of the procedure in "5.1.2 Deletion Procedure" under "Deleting Storage Management Server Transactions and Storage Server Transactions"
Dismount the shared disk on the secondary node
Dismount the shared disk for shared data on the secondary node.
For Storage Management Servers, dismount the shared disk for the repository on the secondary node as well
Mount the shared disk on the primary node
Mount the shared disk for shared data on the primary node.
For Storage Management Servers, mount the shared disk for the repository on the primary node as well
Cancel the TSM cluster settings
Execute the PRIMECLUSTER environment deletion procedure on the primary node by referring to the "ETERNUS SF TSM PRIMECLUSTER Application Guide".
To delete the PRIMECLUSTER environment, mount the ETERNUS SF AdvancedCopy Manager Tape Server Option CD and execute the following command from the CD:
# cd CD-ROM mount point/tape-mgr/solaris/pkg/tsm/CLUS # ./tsmclunset_safe -k Pri -m shared disk mount point for TSM |
Additionally, delete any shared resources or procedures that were used with TSM by referring to the "ETERNUS SF TSM PRIMECLUSTER Application Guide".
Delete procedures on both the primary node and the secondary node
Execute the cluster unsetup command for the Tape Server transaction on the primary node
# /opt/swstorage/bin/tboclunset_lxprm -n logical node name |
Check the deletion target
Information about the logical node specified with the command will be displayed. Check the information that is displayed, and then press the Enter key
# /opt/swstorage/bin/tboclunset_lxprm -n nodeMGR
AdvancedCopy Manager Tape Server settings were as follows.
Cluster system : PRIMECLUSTER
Node type : Primary
Mount point : /STGMGRDISK
Node name : nodeMGR
Function : Tape Server
Do you want to continue with un-setting of AdvancedCopy Manager Tape Server cluster? [default:y] |
Enter "n" to cancel the cluster environment deletion, or type "y" or press the Enter key to continue with the deletion.
The cluster unsetup command on the primary node will complete
The completion screen for the cluster unsetup command will be displayed
swstm 2002 The Tape Server cluster deletion of the primary node has been completed. # |
Execute the cluster unsetup command for the Storage Management Server transaction or the Storage Server transaction on the primary node.
Perform steps 17 to 20 in the procedure in "5.1.2 Deletion Procedure" under "Deleting Storage Management Server Transactions and Storage Server Transactions".
Dismount the shared disk on the primary node
Dismount the shared disk for shared data on the primary node.
For Storage Management Servers, dismount the shared disk for the repository on the primary node as well
Delete port numbers
Delete the following service, which was set in the /etc/services file when the cluster was set up.
Delete this service on both the primary node and the secondary node using a text editor such as vi, which is provided by the operating system
Communications daemon for transactions:stgxfws_logical node name
Restart transactions
Use the PRIMECLUSTER RMS main window to restart the transactions that were stopped in step 2.
This step is not required if the userApplication was deleted in step 3.
