SolarWinds Backup Help

Preparatory steps for versions prior to 16.2

We recommend using a recent version of the Storage Node Installer for best results. If you want to continue with an older version (prior to 16.2), some preparatory steps are necessary:

  1. Stop the storage node service.
  2. Make sure to stop all the processes associated with the storage node service.
  3. Make a backup copy of the current Storage Node Installer installation directory.

In version 16.2 and later of the Storage Node Installer, all necessary processes are stopped automatically. This guarantees that there will not be any conflicts during reconfiguration, so no preparatory steps are needed.

Step 1: Stop the storage node service

Start a terminal emulator and stop the storage node service.

Linux instructions

  • For the CloudStorageController: # /etc/init.d/CloudStorageController stop
  • For the ProcessController (in legacy versions): # /etc/init.d/ProcessController stop

FreeBSD instructions

  • For the CloudStorageController: # /etc/rc.d/CloudStorageController stop
  • For the ProcessController (in legacy versions): # /etc/rc.d/ProcessController stop

Windows instructions

  • For the CloudStorageController: net stop CloudStorageController
  • For the ProcessController (in legacy versions): net stop ProcessController

Checking the storage node service name

The name of the storage node service is "CloudStorageController". In versions released in 2013 or earlier, the name of the process is "ProcessController". If in doubt, you can check which of the names applies to the current storage node installation:

  • For the CloudStorageController: # ps x | grep CloudStorageController | grep -v grep
  • For the ProcessController: # ps aux | grep ProcessController | grep -v grep

If the service is running, you will get a response similar to the following:

15942 ?        Ssl    0:00 /opt/mxb/bin/CloudStorageController serve

Step 2: Stop related processes

Make sure to stop all the processes associated with the storage node service. Here is the full list of the processes:

  • nginx
  • RemoteConnectionGateway
  • WebRemoteConnectionGateway
  • StorageNodeAgent
  • ReportingService
  • CloudStorageController or ProcessController (in legacy versions)

Instructions for Linux and FreeBSD

On Linux and FreeBSD, use the grep command followed by the name of a process. For example, you can check the status of the RemoteConnectionGateway process in the following way:

# ps aux | grep RemoteConnectionGateway

If the service is stopped, no output will be returned.

Windows instructions

On Windows, you can access the processes through the Task Manager (the Processes tab).