Uninstalling TOS

If high availability is enabled, disable it.
On the primary data node:
```
[<ADMIN> ~]$ sudo tos cluster ha disable [--force]
```
sudo tos cluster ha disable
--force should be used only if the cluster status is not healthy - see sudo tos status.

On completion:
- Replication of data to the additional data nodes will cease.
- Data nodes other than the primary data node will contribute very little to the running of the cluster and we recommend removing them using sudo tos cluster node remove.
- Verify that HA is no longer active by running sudo tos status on the primary data node.

If your cluster contains nodes other than the primary data node, remove them:

Identify the node you want to remove and its status by running sudo tos cluster node list on the primary data node.

If the node is in a healthy state:

On the primary data node, run:

[<ADMIN> ~]$ sudo tos cluster node remove <node>

sudo tos cluster node remove <node>

Parameters

Parameter	Description	Required/Optional
`<node>`	Hostname address of the node to remove.	Required

On completion, a new command string is displayed, which you will need to run on the node you want to remove within 30 minutes. If the allocated time expires, you will need to repeat the current step.

Log in to the CLI of the node to be removed.
On the node to be removed, run the command string displayed on completion of the command above. On completion, all TOS-related directories and data will be deleted from the node, therefore make sure you run it on the correct node. Running the command on the wrong node will destroy the cluster.

All TOS-related directories will be deleted from the node.

If the node you want to remove is not in a healthy state:

On the primary data node, run:

[<ADMIN> ~]$ sudo tos cluster node remove <node> --force

sudo tos cluster node remove <node> --force

Parameters

Parameter	Description	Required/Optional
`<node>`	Hostname address of the node to remove.	Required

TOS directories will not be deleted from the node

If the machine is still serviceable, you can delete the TOS directories manually:
```
[<ADMIN> ~]$ sudo rm -rf /opt/tufin/data/*
```
sudo rm -rf /opt/tufin/data/*
```
[<ADMIN> ~]$ sudo rm -rf /opt/tufin/logs/*
```
sudo rm -rf /opt/tufin/logs/*
```
[<ADMIN> ~]$ sudo rm -rf /opt/tufin/migration/*
```
sudo rm -rf /opt/tufin/migration/*
```
[<ADMIN> ~]$ sudo rm -rf /opt/tufin/dumps/*
```
sudo rm -rf /opt/tufin/dumps/*

Verify that the node has been removed by again running sudo tos cluster node list.

Uninstall TOS Aurora from your system. This removes the software components but not your data.
```
[<ADMIN> ~]$ sudo tos uninstall
```
sudo tos uninstall

After the uninstall command has completed, a number of directories will remain on your primary data node. Run the commands below to remove all directories except backups and other data that you may need in the future:

[<ADMIN> ~]$ sudo rm -rf /opt/tufin/data/*
[<ADMIN> ~]$ sudo rm -rf /opt/tufin/logs/*
[<ADMIN> ~]$ sudo rm -rf /opt/tufin/migration/tmp
[<ADMIN> ~]$ sudo rm -rf /opt/tufin/migration/log
[<ADMIN> ~]$ sudo rm -rf /opt/tufin/migration/tos2-upgrade
[<ADMIN> ~]$ sudo rm -rf /opt/tos/.install
[<ADMIN> ~]$ sudo rm -rf /opt/tos/.update
[<ADMIN> ~]$ sudo rm -rf /tmp/tufin

sudo rm -rf /opt/tufin/data/* \
sudo rm -rf /opt/tufin/logs/* \
sudo rm -rf /opt/tufin/migration/tmp \
sudo rm -rf /opt/tufin/migration/log \
sudo rm -rf /opt/tufin/migration/tos2-upgrade \
sudo rm -rf /opt/tos/.install \
sudo rm -rf /opt/tos/.update \
sudo rm -rf /tmp/tufin

In addition, if the SC module was enabled:

[<ADMIN> ~]$ sudo rm -rf /opt/tufin/migration/sc-server

sudo rm -rf /opt/tufin/migration/sc-server

An alternative to deleting the sub-directories from /opt/tufin and /opt/tos is to delete /opt/tufin and /opt/tos entirely, however this will remove also data that you may need in the future, including backups and installation files:

[<ADMIN> ~]$ sudo rm -rf /opt/tufin/
[<ADMIN> ~]$ sudo rm -rf /opt/tos/

sudo rm -rf /opt/tufin/ \
sudo rm -rf /opt/tos/