ETERNUS SF Storage Cruiser V16.9.1 / AdvancedCopy Manager V16.9.1 Cluster Environment Setup Guide

13.1.4 Uninstallation of ETERNUS SF Manager

Uninstall the ETERNUS SF Manager.
The procedure is as follows:

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. With Failover Cluster Manager, move transactions to which ETERNUS SF Manager belongs to the primary node.

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

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

   1. With Failover Cluster Manager, move transactions to which ETERNUS SF Manager belongs to the secondary node.

   2. Refer to "Uninstallation of ETERNUS SF Manager" in the 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 Remove 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 Remove to delete the IP address resources. The Remove Client Access Point is displayed. Click Yes.

   • Scripts

     Right-click the scripts that were used by ETERNUS SF Manager and select Remove to delete the script resources. The Remove Generic Script is displayed. Click Yes.

   • Services

     Right-click the following services and select Remove to delete the service resources. The Remove Generic Service is displayed Click Yes.

     • ETERNUS SF Manager Postgres Service

     • ETERNUS SF Storage Cruiser Optimization Option

     • AdvancedCopy Manager COM Service for logicalNodeName (when "AdvancedCopy COM Service_logicalNodeName" is remained)

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

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

   In the Failover Cluster Manager tree, right-click Roles > ESF-manager and then select Remove. The Remove Other is 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 folder that copied files under ETERNUS_SF\AST

   • 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 your cluster software manuals for information on how to start the cluster transaction.