Skip to content

Server to this release

Upgrading from older versions

The following instructions assume that you are upgrading from Server version 2021.1.0 or later. If you are running 2020.x or earlier please contact SAS Technical Support for instructions specific to your version.

Linux

  1. Stop all Agents and the Server
  2. Copy/move the pgsql folder from within esm-server to a location outside of the existing esm-server folder
  3. Rename the existing installation folder to something like esm-server-old
  4. Perform a fresh installation of the Server using these instructions ensuring that you install into the same location as the previous version
  5. After the installation completes, stop the server if it was started during the installation process
  6. The installation will have created a new pgsql folder, rename or remove this folder
  7. Move the pgsql folder from step 2 to the new esm-server folder
  8. Start the Server and Agent(s)

The Server will now start and automatically upgrade your database to the latest release. Once a validation of the new installation has been completed, the backup of the old installation taken in step 3 can be removed.

Windows

  1. Stop all Agents and the Server
  2. Copy/move the pgsql folder from within esm-server to a location outside of the existing esm-server folder
  3. Remove the existing installation by following these instructions
  4. Perform a fresh installation of the Server using these instructions
  5. After the installation completes, stop the server if it was started during the installation process
  6. The installation will have created a new pgsql folder, rename or remove this folder
  7. Move the pgsql folder from step 2 to the new esm-server folder
  8. Start the Server and Agent(s)

The Server will now start and automatically upgrade your database to the latest release.

Kubernetes

By default, the Server has an image update policy that will always pull the latest version of the application image available at the latest tag. Therefore, to get the latest version of the Server, the pod within the Deployment just needs to be restarted.

  1. Restart the Server Deployment 
    kubectl rollout restart deployment sas-enterprise-session-monitor-server -n default
Last update: July 25, 2023
Created: April 24, 2023