5 2 0:Updating SEP sesam

Overview

During the maintenance period, SEP sesam provides updates, bug fixes, patches, service packs, and the latest versions to users with a valid license. New versions of SEP sesam deliver fixes, improvements, and new functionality to optimize the performance and capabilities of your backup environment. Service packs include all released bug fixes for the corresponding SEP sesam version, ensuring stability and reliability.

To keep you informed about updates and issues affecting your SEP sesam environment, notifications are available via RSS feeds. These alerts provide information about releases of bug fixes, service packs, critical issues, and announcements of new versions. You can access these notifications in the Notification Center.

SEP sesam enables you to configure an update strategy that best fits your environment, minimizing disruptions to backup operations. Different options for installing and updating SEP sesam help you to update your system efficiently, with minimal impact on your backup schedules and system performance.

To check for new versions, SEP sesam Server reads the inventory file from the official repository at SEP Download Center and compares the list of available versions with the installed ones. Additionally, SEP sesam enables you to set up and use a custom repository, which is useful in secure network environments with limited internet connectivity or when you need to control which versions are available for installation.

Configuring update strategy

By configuring your update strategy, you can ensure that SEP sesam updates are applied in a controlled and efficient manner, minimizing disruptions to your backup environment. Update strategy involves setting the update mode, which defines how updates are handled. Additionally, you can exclude individual clients from receiving updates.

Configuring the update strategy for your SEP sesam clients allows you to control how and when updates are checked, downloaded, and installed. SEP sesam provides several options, ranging from automated update process to full manual control.

Selecting update mode

You can set your update mode in GUI menu bar -> Configuration -> Defaults -> tab Install/Update. Each mode defines how SEP sesam handles updates for all clients in your environment. The available update modes are:

• Turn off (hide from all users):

This mode completely disables the install and update feature in the GUI. No user, including administrators, will see any options related to installation or updates until the mode is changed. This is useful if updates should not be performed at all.

• Do not check or install automatically (default option):

By default, SEP sesam does not check, download, or install updates. In this mode, updates are handled manually, ensuring you have full control over when and how updates are applied.

• Check automatically, but install manually:

In this mode, SEP sesam automatically checks for available updates by accessing the index.txt file in the SEP Download Center, which contains the list of all available packages. However, updates are not downloaded or installed automatically. When you want to update the clients, you must manually trigger this action.

• Check, download, and install automatically:

SEP sesam automatically checks for updates. When a new version is available from the SEP Download Center, SEP sesam automatically downloads and installs the available software packages, based on the SEP sesam NEWDAY schedule. This mode doesn’t require any manual intervention, but it could interfere with ongoing backup jobs or other activities in a busy environment.

Screenshots

Excluding clients from updates

You may need to prevent specific clients from being updated, even if your update mode is set to Do not check or install automatically.

To exclude a client from updates, in the GUI go to the Main Selection -> Components -> Clients, double-click the client you want to modify to open its properties and select Do not update this client check box. Note that this setting applies in general for all possible updates, including service packs and other software packages.

This option is useful when updating multiple clients simultaneously. SEP sesam enables you to update a group of clients based on their location or operating system (Windows or Linux). By excluding a client, you ensure it is skipped during the group update, eliminating the need to create a client list manually.

Screenshots

Update process

Keeping your SEP sesam environment up to date ensures that all components, SEP sesam Server, RDS, GUI Server, and clients, run the latest version. Updates deliver new features, service packs and fixes, improving performance and reliability.

SEP sesam uses its update functionality to compare installed component versions with the latest versions available in the SEP repository. This process relies on the index.txt file, which lists all available packages in the repository. By default, SEP sesam retrieves the index.txt file from the official SEP Download Center.

In secure environments or networks with limited internet connectivity, you can use a custom repository. This allows sourcing updates from a local folder, network share, or custom URL. The custom repository must include a manually prepared index.txt file listing the available packages.

When updating SEP sesam, the SEP sesam Server has to be updated first, followed by RDS, clients and other components. Make sure to follow this sequence to maintain compatibility across all components.

SEP sesam provides flexibility in managing updates. Updates can be checked, downloaded, and installed automatically, or the process can be performed manually. Update packages are provided as executable installation files for Windows or as packages for Linux systems. For Linux, service packs (SP) are distributed as shell scripts, which must be made executable before installation.

Viewing and tracking update status

You can track the installed software and update status of your SEP sesam components in the Web UI in the Clients view. In the Software tab, you can view the detailed information on installed and available versions of the clients, and you can filter the list to focus on specific areas of interest. The Software Update tab provides a detailed view of the update events for clients.

In the GUI, you can view the detailed update status of a client by right-clicking the client and selecting Check Update State. You can also track updates across multiple clients by expanding a location to display a group of clients.

For the SEP sesam Server, you can check the installed software version and update status in the Web UI by selecting the server name in the navigation menu at the top. This opens a dialog box displaying detailed information about the server, including client software and update status, organized into tabs for easy navigation.

Screenshots

File:About SEP sesam WebUI.jpg

Alternatively, in the GUI, navigate to the menu bar and select Help -> About SEP sesam. This provides comprehensive details about all installed packages and their versions for the SEP sesam Server.

Screenshots

Update methods

SEP sesam provides several methods for installing updates, enabling you to choose the one that best fits your system requirements and administrative preferences. The following methods are available:

• Update using the GUI

With this method, SEP sesam automatically checks for available updates. If a newer version of the SEP sesam client package or a service pack is available, the client is updated directly through the graphical user interface (GUI). This approach is straightforward and ideal for managing updates interactively.

• Update using the CLI

The command-line interface (CLI) offers a powerful way to check for and install updates, service packs, and patches on all SEP sesam components, including the SEP sesam Server. This method also supports additional options for scripting and automation, making it suitable for advanced users and administrators managing updates across multiple systems.

• Direct installation on the computer

This method involves downloading the SEP sesam software package to the target computer and running the installation directly. Windows updates involve running an executable file, while Linux updates may require making the software package file executable before installation. This method is useful when a direct or manual approach is preferred, or when network connectivity limits the use of automated methods.

Each method provides a different approach to updating, enabling you to choose the one that best fits your system requirements and administrative preferences.

Updating SEP sesam Server

Updating the SEP sesam Server involves downloading the appropriate update package from SEP Download Center and installing it directly on the server system. Before proceeding with the update, it is recommended to back up your SEP sesam environment and review the release notes for details about the update. Always update the SEP sesam Server first, followed by other components, such as RDS, GUI and clients.

	Note
	If you are using a remote GUI client, it must also be updated when the SEP sesam Server is updated. Both systems must run the same GUI version to function properly.

In the SEP Download Center, you can find software packages organized by component, operating system (OS) or platform, and hardware architecture. The naming convention for SEP sesam software packages provides detailed information about the package, including its version, distribution compatibility, and architecture. Packages are named according to the following conventions:

SEP sesam version:

<component>-<version>.<OS>.<architecture>.<extension>

Examples:

• On Windows: sesam-srv-5.1.0.24-windows.x64.exe
• On Linux: sesam_srv-5.1.0-24.sles15.x86_64.rpm

Service pack:

<component>-<timestamp>_<identifier>_<version>.<OS>.<architecture>.<extension>

Examples:

• On Windows: sesam_sp_srv-202404171004_7f6a952_5.1.0.14_windows_x64.exe
• On Linux: sesam_sp_srv-202404171004_7f6a952_5.1.0-14.sles15.x86_64.sh

For Windows systems, SEP sesam provides executable installation packages that can be run directly to install the software. For Linux systems, executable RPM or DEB packages are provided for component versions, which can be installed using the appropriate package manager (for example, yum or apt). Service packs on Linux are provided in shell script files that must first be made executable using the chmod +x command, for example:

root@system: ~ # chmod +x sesam_sp_srv-202404171004_7f6a952_5.1.0-14.sles15.x86_64.sh 

	Note
	All commands must be executed either as root user or as an administrative user using the sudo command.

SEP sesam Server cannot be updated using the GUI, a new version must always be downloaded and installed manually. However, the GUI provides two update options specifically for the SEP sesam Server: Install Service Pack and Install UI Server Service Pack. These options allow you to apply service packs for the server and the GUI client.

	Note
	SEP sesam service pack installation does not check if SEP sesam operations are running. Applying a patch will stop all active operations, for example backup or migration.

Updating RDS

The SEP sesam Remote Device Server (RDS) component is updated in a similar manner to the SEP sesam Server component and involves downloading the appropriate package from the SEP Download Center and installing it directly on the system.

During the installation or update of the RDS, the hostname of the SEP sesam Server must be provided. Make sure to use the server hostname and not its IP address.

When installing RDS, you also have the option to include the GUI and client components. The client package on the RDS system can be updated or installed using the GUI.

Updating SiS Server

The Si3 deduplication store requires a dedicated SiS Linux server with the SEP sesam RDS package installed. For security purposes, the SEP sesam Server does not have remote access to the SiS Server, which means updates cannot be performed directly from the SEP sesam Server. Instead, the update process must be executed locally on the SiS Server.

To update the SiS Server, first download the appropriate RDS package for your system from SEP Download Center and install it directly on the SiS Server. Ensure the installation is performed with administrative privileges. Optionally, download the latest si3.jar file from the SEP sesam Server and update it on the SiS Server.

To update the Si3 deduplication store on the SiS Server, locally run the following command:

#> sm_create_sds.sh -U -u 1 

If required, you can modify the immutability period of the SiS storage during the update process. Run the following command:

#> sm_create_sds.sh -U -E <immutability period in days> -u 1

For example:

#> sm_create_sds.sh -U -E 21 -u 1

For more information, see also SEP Immutable Storage – SiS.

Updating GUI client

The SEP sesam GUI client and SEP sesam Server must run the same version to function correctly.

When the GUI client is started, it connects to the SEP sesam Server and checks the software versions of both systems. If the versions do not match, the GUI client will display a notification indicating that an update is required. You can then start the update process, and the required software is downloaded directly from the SEP sesam Server.

Alternatively, you can download the appropriate installation package from SEP Download Center and install the GUI component. The GUI component is included in the installation packages for SEP sesam Server, RDS, and Client, and can be installed independently as a standalone component, or in combination with other SEP sesam components.

Updating clients

For updating clients, SEP sesam provides several different options. Using either the GUI or CLI, you can update individual clients or perform updates simultaneously on multiple clients. Additionally, SEP sesam allows you to exclude specific clients from updates to prevent updates on particular systems that may require special handling.

You can customize the update strategy for your SEP sesam clients to control how and when updates are checked, downloaded, and installed. SEP sesam provides options that range from automatic updates to full manual control.

The update process includes client software packages as well as any applicable service packs, ensuring that your SEP sesam environment remains up-to-date with the latest improvements and fixes.

For detailed information and instructions, see Updating Clients.

Using custom repository for SEP sesam packages

By default, SEP sesam checks and retrieves updates from its official repository in SEP Download Center. The default repository is managed by SEP and contains the latest SEP sesam packages, service packs, and updates. However, you can configure a custom repository stored locally, on a network drive, or accessed at a specific URL. A custom repository allows you to manage specific versions and control updates across your environment, and offers network security by hosting the repository in a secured location behind a firewall, or disabling access from SEP sesam Server to the internet.

You can set up a custom repository in one of the following locations:

• Local directory

Store the repository on your local system, for example, file:///C:\temp\sesam_download on Windows, or file:////tmp/sesam_download on Linux.

• Network share

Store the repository on a network-accessible location, for example, file:\\<win_share>\users\admin\sesam\ on Windows, or file://<linux_share>/users/admin/sesam/ on Linux.

• Custom URL

Use a URL pointing to a remote repository with the required packages, for example, http://beta.sep.de/.

To set up and configure the custom repository, you have to prepare the repository and then specify its location in SEP sesam. To recognize the repository and its contents, SEP sesam requires the index.txt file, which contains a list of all available package files within the specified directory and allows SEP sesam to identify and access these files for updates.

Prepare the repository

To prepare the custom SEP sesam repository, first download the required SEP sesam packages to the directory you plan to use as your custom repository. Do not create subdirectories and ensure that all necessary package versions are located in the relative root directory. The index file will only reflect the contents of this directory, not its subdirectories.

Next, generate or update the index.txt file. The index.txt file must be updated each time new package versions are added to the repository to reflect the updated contents. Note that when you activate the custom repository for the first time, SEP sesam automatically creates the index.txt file.

	Tip
	If you download all available packages from the SEP Download Center, you can also download the latest index.txt for use in your custom repository.

If the index.txt file already exists at the repository, you can delete the existing file and SEP sesam will regenerate it automatically when accessing the repository.

Alternatively, you can recreate the file manually to ensure the list is updated with relative paths for all available packages in the repository. In the CLI navigate to the directory of your repository, and run the following command:

• on Windows:

dir /B > index.txt  

• on Linux:

find . -name "*sesam*" -printf "%P %k %TY-%Tm-%Td %TH:%TM:%TM \n" > index.txt  

Activate the repository

To activate the custom SEP sesam repository and configure SEP sesam to use it, perform the following steps:

1. In the GUI menu bar navigate to Configuration -> Defaults -> tab Install/Update.
2. Enable option Use custom SEP sesam package source.
3. Enter the path to the repository and then click OK.

	Note
	When specifying paths, make sure to use the correct path syntax. For local repositories, use file:/// on Windows, or file://// on Linux. For network shares, use file:\\ on Windows, or file:// on Linux.

Screenshots

See also

About Installation and Update — Updating Clients — Remote Installation of Windows Clients — Notification Center — SEP sesam Web UI Dashboard — SEP sesam CLI

Copyright © SEP AG 1999-2025. All rights reserved.

Any form of reproduction of the contents or parts of this manual is allowed only with the express written permission from SEP AG. When compiling and designing user documentation SEP AG uses great diligence and attempts to deliver accurate and correct information. However, SEP AG cannot issue a guarantee for the contents of this manual.