Install > SA Core uninstallation

SA Core uninstallation

This section describes how to uninstall a Single Core, remove a core from a Multimaster Mesh, and how to uninstall all cores of a Multimaster Mesh.

Uninstall basics

There are several reasons that you might choose to uninstall an SA Core:

  • Removing test installations
  • Removing demonstration installations
  • Merging or modifying a facility’s Multimaster Mesh Cores
  • Decommissioning or moving a facility

Make backups of your Model Repository, Software Repository, and your database of cryptographic material unless you are certain that you no longer need that data, because a complete core uninstallation also removes the Model Repository and the cryptographic material database and permanently deletes all the data. You can preserve the SA data in the Model Repository database by doing a database backup before uninstalling. See the Oracle documentation.

Note: Before you uninstall an SA Core, you should back up the Oracle database running on the server where that core’s Model Repository is installed. See Oracle database backup methods.
Note: The core’s cryptographic material must be available during the uninstallation so that SA Core Components can be fully removed from the environment. If the cryptographic material is not available, the uninstallation will fail.

Procedures for uninstalling Cores

You can perform any of the following uninstallation procedures according to your requirements:

Uninstall a single Core

A single core can have all components installed on one host or may have some core components installed (distributed) on other hosts. To uninstall a single SA Core, perform the following tasks:

  1. Before uninstalling a single core, you must deactivate all servers that host components for that Core using the SA Client.
  2. On the server hosting the core’s Infrastructure Component bundle, log in as root.
  3. Change to the root directory:

    cd /

  4. Run the uninstall_opsware.sh script with the -r (specify response file) argument. You need to use the response file created when you installed the SA Core you are uninstalling:

    <distro>/opsware_installer/uninstall_ opsware.sh -r <response-file>

    where <distro> is the full path to the Product Software (primary) media. You must specify the full path the response file.

  5. A menu similar to the following appears:

    Welcome to the Opsware Installer.
    Please select the components to uninstall.
    1 ( ) Software Repository - Content (install once per mesh)
    2 ( ) OS Provisioning
    3 ( ) Slice
    4 ( ) Core Infrastructure Components
    5 ( ) Model Repository, First Core
    6 ( ) Oracle RDBMS for SA

    Select one or more or all components to uninstall:

    Press a to select all components. If you must uninstall components one-at-a-time, for example due to a custom installation where core components have been distributed among multiple core component hosts, the components must be uninstalled in the order they appear on the menu above. For example, you would first log on to the SA Provisioning component host, run uninstall_ opsware.sh -r <response-file> and uninstall that component, then log into the Slice Component bundle host and run the uninstall script to remove that component, and so on down the list.

    You will be asked if you want to preserve the database of Cryptographic Material. If you enter y, the directory containing the database will not be removed during the uninstall.

    You will also see this prompt:

    Are you absolutely sure you want to remove users' OGFS home and audit directories? (home and audit directories will only be removed if they are stored on the Software Repository server) (y/n)?

    Select y if you want to remove the OGFS home and audit directories. If you press n, the directories will not be removed. Note that, if you have placed the OGFS home and audit directories on a server other than the server hosting the Software Repository, the uninstall will not remove those directories even if you press y.

  6. After you have uninstalled all core components, you should remove the /var/opt/opsware/install_opsware directory.
If you specified during the uninstall that you want to preserve the database of cryptographic material, you should not delete the /var/opt/opsware/crypto directory. This directory contains the database of your cryptographic material.

Uninstalling a Secondary Core in a Multimaster Mesh

Note: Do not uninstall the First Core (primary core) unless you plan to uninstall the entire Multimaster Mesh and all its cores. Uninstalling all Cores in a Multimaster Mesh. This section describes only uninstalling Secondary Cores from a Multimaster Mesh.

To uninstall a single Secondary Core in a Multimaster Mesh:

  1. Log in to any SA Client available for that Mesh.
    1. If the Secondary Core to be uninstalled has a Data Access Engine that is currently serving as the Primary Data Access Engine for the core, you must first assign a Data Access Engine in another Core to serve as the Primary Data Access Engine.

      See the Reassigning the Data Access Engine to a Secondary Role section in the SA 10.50 Administration Guide.

    1. Verify that all transactions have propagated to the other facilities in the Multimaster Mesh.

      For more information about verifying transaction traffic, see Verifying multimaster transaction traffic.

  2. Decommission the facility for the core you will uninstall.
    1. See Decommissioning a facility.
    2. On the Infrastructure Component bundle host in the core you are decommisioning, run the following command:

      /opt/opsware/bin/python2
      <distro>/opsware_installer/tools/reload_vaults.pyc --certfile
      /var/opt/opsware/crypto/gateway/spin.srv

      where <distro> is the full path to the Product Software (primary) media. Successful output will be similar to this:

      Core ID Peers IDs Known To This Core
      ------- --------------------------------
      <      nnn> <nnn>
  3. Stop and start the Model Repository Multimaster Component in all cores, except for the core that you will be uninstalling, by entering the following command as root on Infrastructure Component bundle host(s):

    /etc/init.d/opsware-sas stop vaultdaemon
    /etc/init.d/opsware-sas start vaultdaemon

  1. Stop the Command Center (OCC) component (part of the Slice Component bundle). Log in as root to a Slice Component bundle host and enter the following command:

    /etc/init.d/opsware-sas stop occ.server

  2. Stop all Data Access Engines (part of the Infrastructure Component bundle).

    Log in as root to the Infrastructure Component bundle host and enter the following command:

    /etc/init.d/opsware-sas stop spin

Note: If the Command Center and the Data Access Engine are installed on different servers, you must also run the stop spin command on all Slice Component bundle hosts.
  1. Stop the Model Repository Multimaster Component.

    Log in as root to the Infrastructure Component bundle host and enter the following command:

    /etc/init.d/opsware-sas stop vaultdaemon

  2. On the Infrastructure Component bundle host, stop and start the Data Access Engine that serves as the Primary Data Access Engine by entering the following commands as root:

    /etc/init.d/opsware-sas stop spin

    /etc/init.d/opsware-sas start spin

  1. On Infrastructure Component bundle host for the core to be uninstalled, log in as root.
  2. Change to the root directory:

    cd /

  3. Run the uninstall_opsware.sh script:

    <distro</opsware_installer/uninstall_ opsware.sh -r <response-file>

    where <distro> is the full path to the mounted media.

  4. At the components prompt, select one or more or all components to uninstall:

    Welcome to the Opsware Installer.
    Please select the components to uninstall.
    1 ( ) OS Provisioning
    2 ( ) Slice
    3 ( ) Infrastructure
    2 ( ) Model Repository
    1 ( ) Oracle RDBMS for SA

    Select a for all. If you want to uninstall components separately, they must be uninstalled in the order they appear on the menu above. To do so, enter the number of the component to uninstall. For example, you would first log on to the SA Provisioning component host, run uninstall_ opsware.sh -r <response-file> and uninstall that component, then log into the Slice Component bundle host and run the uninstall script to remove that component, and so on down the list.

  5. You will be asked if you want to preserve the database of Cryptographic Material. If you respond y, the directory containing the database will not be removed during the uninstall.

    You will also see this prompt:

    Are you absolutely sure you want to remove users' OGFS home and audit directories? (home and audit directories will only be removed if they are stored on the Software Repository server) (y/n)?

    Enter y if you want to remove the OGFS home and audit directories. If you enter n, the directories will not be removed. If you chose to place the OGFS home and audit directories on a server other than the server hosting the Software Repository, the uninstall will not remove those directories even if you enter y.

Requirements: If you installed the core using Custom Mode, it is important that you uninstall the components in the reverse order that they were installed.
  1. After the uninstall has completed, remove the /var/opt/opsware/install_opsware directory.
Requirements: If you specified during the uninstall that you want to preserve the database of cryptographic material, you should not delete the /var/opt/opsware/crypto directory. This directory contains the database of cryptographic material.

Uninstalling all Cores in a Multimaster Mesh

To uninstall all cores in a Multimaster Mesh:

  1. Stop the Command Engine (OCC) by logging on as root to a Slice Component bundle host and enter the following command:

    /etc/init.d/opsware-sas stop occ.server

  2. Stop the Data Access Engine (spin).

    Log in as root to the Infrastructure Component bundle host and enter the following command:

    /etc/init.d/opsware-sas stop spin

    If the Command Engine and the Data Access Engine are installed on different servers, you must also run the stop spin command on the Slice Component bundle host(s).

  3. Stop the Model Repository Multimaster Component in all cores by logging in to all Infrastructure Component bundle hosts and running the following command as root:

    /etc/init.d/opsware-sas stop vaultdaemon

  4. In each core, uninstall all SA components on the hosts on which they are installed. On the servers hosting the components to be uninstalled, log in as root.
  5. Change to the root directory:

    cd /

  6. Run the uninstall_opsware.sh script:

    <distro>/opsware_installer/uninstall_ opsware.sh -r <response-file>

    where <distro> is the full path to the mounted media.

  7. At the components prompt, select one or more or all components to uninstall:

    Welcome to the Opsware Installer.
    Please select the components to uninstall.
    1 ( ) OS Provisioning
    2 ( ) Slice
    3 ( ) Infrastructure
    2 ( ) Model Repository
    1 ( ) Oracle RDBMS for SA

    Select a for all. If you want to uninstall components separately, they must be uninstalled in the order they appear on the menu above. To do so, enter the number of the component to uninstall. For example, you would first log on to the SA Provisioning component host, run uninstall_opsware.sh -r <response-file> and uninstall that component, then log into the Slice Component bundle host and run the uninstall script to remove that component, and so on down the list.

    You will be asked if you want to preserve the database of Cryptographic Material. If you respond y, the directory containing the database will not be removed during the uninstall.

    You will also see this prompt:

    Are you absolutely sure you want to remove users' OGFS home and audit directories? (home and audit directories will only be removed if they are stored on the Software Repository server) (y/n)?

    Enter y if you want to remove the Global File System (OGFS) home and audit directories. If you enter n, these directories will not be removed. If you placed the OGFS home and audit directories on a server other than the server hosting the Software Repository when you installed the core, the uninstall script will not remove those directories even if you enter y.

Requirements: If you installed the core using Custom Mode, it is important that you uninstall the components in the reverse order that they were installed.
  1. After the uninstall has completed, remove the /var/opt/opsware/install_opsware directory.
Caution: If you specified during the uninstall that you want to preserve the database of cryptographic material, you should not delete the /var/opt/opsware/crypto directory. This directory contains the database of cryptographic material.

Decommissioning a facility

Caution: Performing this procedure does not shut down or uninstall SA in a facility. Decommission facilities with care, because this task cannot be undone.

When you decommission a facility, the facility is still listed in the SA Client; however, it is grayed out. After a short name is used, even if it is decommissioned, that name cannot be reused.

  1. To decommission a facility with the SA Client, perform the following steps.
  2. From the SA Client navigation pane, select the Devices tab, then select All Managed Servers. This displays all your managed servers.
  3. Locate and select the server that is running the core for the facility you want to decommission. You must first deactivate the SA Agent on this server.
  4. Select the Actions menu or right-click and select Deactivate Agent. This deactivates the SA Agent on that server.
  5. Select the Administration tab, then select Facilities. This displays all your facilities.
  6. Select the facility that you want to decommission.
  7. Select the Actions menu or right-click and select Decommission.
  8. Confirm your selection. This decommissions the facility.
Note: After you have deactivated a facility, you must delete the deactivated core host. This prevents system diagnostic errors.

Removing a decommissioned facility

When you decommission a facility, the facility is still listed in the SA Client; however, it is grayed out. You can remove a facility by performing the following steps:

  1. From the SA Client navigation pane, select the Devices tab, then select All Managed Servers. This displays all your managed servers.
  2. Remove all the servers which are managed by the facility you want to delete.
  3. All customers attached to the facility must be removed before the Facility can be removed.
  4. Stop all services on the core servers that are part of the facility which will be deleted.

    /etc/init.d/opsware-sas stop

  5. Select the Administration tab, then select Facilities. This displays all your facilities.
  6. Select the facility you want to remove.
  7. Select the Actions menu or right-click and select Delete.
  8. Confirm your selection. This deletes the facility.
  9. Restart Model Repository Multimaster component on the primary core infrastructure server

    /etc/init.d/opsware-sas restart vaultdaemon

  10. On the primary core infrastructure server, remove the entry corresponding to the facility you just removed from the following file:

    /etc/opt/opsware/opswgw-mgw-<primary_facility_name>/opswgw.custom

    The line will look similar to:

    opswgw.ForwardTCP=<port>:<removed_facility_name>-mm:<secondary_core_db>:<db_port>

    For example: opswgw.ForwardTCP=20002:SLAVE-mm:192.168.100.3:1521

Send Help Center feedback