Upgrading a Server

If you are upgrading the Carbon Black EDR server, the procedure varies depending on whether you are upgrading a standalone server or a clustered server.

The database schema or VMware CB Threat Intel feed data must be migrated after the new server version is installed.

These steps require SSH or console access to the server and minions with root privileges.

To upgrade a standalone server:

1. On the server, stop the Carbon Black EDR services:

   sudo service cb-enterprise stop

2. (Optional) Clean the yum cache of metadata and packages:

   yum clean all

3. Update the Carbon Black EDR services:

   sudo yum upgrade cb-enterprise

4. Restart the Carbon Black EDR services:

   sudo service cb-enterprise start

To upgrade a clustered server:

1. On the primary server, navigate to the cb install directory (defaults to /usr/share/cb ) and stop the Carbon Black EDR services: sudo cbcluster stop

2. (Optional) Clean the yum cache of metadata and packages:

   yum clean all

3. Update the Carbon Black EDR services on each primary and minion server node:

   sudo yum update cb-enterprise

4. Run the cbupgrade utility (see the following section for more information.):

   /usr/share/cb/cbupgrade

5. On the primary server, restart the Carbon Black EDR services:

   sudo cbcluster start

Caution:

On pre-6.1 versions of Carbon Black EDR, you could change the home directory of the cb service account, which is /var/cb by default. This is the account under whose auspices server installations occur. This is no longer supported, and will cause upgraded servers to fail with an nginx error.

The home directory of the cb service account must be /var/cb. This is where upgrades place runtime configuration files for nginx, so if you changed the cb service home directory, these files will not be found. If you edited the home directory in /etc/password, restore it to /var/cb before upgrading.