ETERNUS SF Storage Cruiser V15.3/ AdvancedCopy Manager V15.3 Cluster Environment Setup Guide

13.1.4 Uninstallation of ETERNUS SF Manager

Uninstall the ETERNUS SF Manager.

This explanation for uninstalling the ETERNUS SF Manager uses "ESF-manager" as the name of the cluster service to be deleted.

1. Uninstall the ETERNUS SF Manager from the primary node.

   1. Use the Failover Cluster Manager to take ownership of the transactions to which ETERNUS SF Manager belongs on the primary node.

   2. Refer to "Uninstallation of ETERNUS SF Manager" in the ETERNUS SF Installation and Setup Guide to uninstall the ETERNUS SF Manager.

2. Uninstall the ETERNUS SF Manager from the secondary node.

   1. Use the Failover Cluster Manager to take ownership of the transactions to which ETERNUS SF Manager belongs on the secondary node.

   2. Refer to "Uninstallation of ETERNUS SF Manager" in the ETERNUS SF Installation and Setup Guide to uninstall the ETERNUS SF Manager.

3. Delete the service resources from the primary and secondary nodes.

   Use the Failover Cluster Manager screen to delete below resources from the transactions to which ETERNUS SF Manager belongs. If you are going to use them in any other services, the shared disks and IP addresses do not have to be deleted.

   • Shared disks

     Right-click the resources for the shared disks that were used by ETERNUS SF Manager and select Delete from ESF-manager to delete the shared disk resources.

   • IP addresses

     Right-click the resources for the IP addresses that were used by ETERNUS SF Manager and select Delete to delete the IP address resources. The Confirm Operation will be displayed. Click Yes.

   • Scripts

     Right-click the scripts that were used by ETERNUS SF Manager and select Delete to delete the script resources. The Confirm Operation will be displayed. Click Yes.

   • Services

     Right-click the following services and select Delete to delete the service resources. The Confirm Operation will be displayed Click Yes.

     • ETERNUS SF Storage Cruiser Manager

     • ETERNUS SF Manager Postgres Service

     • AdvancedCopy Manager COM Service for logical node name (If "AdvancedCopy COM Service_logicalNodeName" is remained.)

     • AdvancedCopy Manager GUI Service (If "AdvancedCopy GUI Service" is remained.)

4. Delete the cluster resources from the primary and secondary nodes.

   If only ETERNUS SF Manager belonged to the transaction, delete the cluster service (transaction).

   In the Failover Cluster Manager tree, right-click Services and Applications > ESF-manager and then select Delete. The Confirm Operation will be displayed. Click Yes.

5. Delete unnecessary resources.

   Delete the directories and the files that remain in the following locations.

   • Under ETERNUS SF Manager install directory on the primary node

   • Under ETERNUS SF Manager install directory on the secondary node

   • Under the shared disk folder that copied dynamic disk

   • Under the shared disk folder that copied files under ETERNUS_SF\ESC

   • Under the shared disk for AdvancedCopy Manager repository and the shared disk for AdvancedCopy Manager shared data.

   • Storage destination of generic script for AdvancedCopy Manager CCM, Apache, and Tomcat

6. Use the Failover Cluster Manager to resume the suspended transactions.

   Refer to the Windows Server Failover Clustering manuals for information on how to start the cluster group.