Release Notes 5.2.0 Artemis

From SEPsesam
(Redirected from Release Notes)


SEP sesam version 5.2.0.6 Artemis: a new major release
April 17, 2025
Installation is highly recommended as it includes various performance, stability, and other key customer fixes. For details, see Change report 5.2.0 Artemis.
Download for Linux: SEP sesam 5.2.0 Linux Download for Windows: SEP sesam 5.2.0 Windows
See Installation on Linux See Installation on Windows
Note

You always have to update the SEP sesam Server first before updating the RDS and client components. For more information on the SEP sesam software updates, see Updating SEP sesam.

What's new in 5.2.0.6 Artemis

Fixes
Fixed with 5.2.0.6 Artemis:
SEP sesam v. 5.2.0.5 - (#34655) Update to SEP sesam 5.2.0.5 fails due to 'NULL' string in DB:results.eol field
In SEP sesam version 5.2.0 Artemis, the data type of the DB:results.eol database field was changed to TIMESTAMP. If this field contains the string 'NULL' (as text, not as database NULL value), the update to version 5.2.0.5 fails because the string cannot be automatically converted to a valid timestamp.
Solution: Fixed with 5.2.0.6 Artemis.
SEP sesam v. 5.2.0.5 - (#34653) After upgrade on Windows, 'beta' flag is set
After updating SEP sesam from version 5.1.0.X to 5.2.0.5 on Windows, the 'beta' flag may be incorrectly set in the configuration. Note that this issue affects Windows systems only, Linux systems are not affected.
Workaround: To clear the flag, first set the SEP sesam profile, then run the following command:
sm_db "update defaults set value='0' where key='beta'"
Solution: Fixed with 5.2.0.6 Artemis.

See also: Change report

What's new in 5.2.0 Artemis

Important considerations

Note
The minimum required version for updating to 5.2.0 Artemis is 5.1.0.14 Apollon V2. Make sure your SEP sesam installation is updated to 5.1.0.14 or higher before proceeding with the update to 5.2.0 Artemis. Direct update from lower versions is not supported. See also SEP sesam Release Versions.
PostgreSQL version 15 or higher for SEP sesam database
The SEP sesam Server requires PostgreSQL version 15 or higher as its database system. On Windows, PostgreSQL is automatically upgraded to version 16.6 (previously 13.9) during the upgrade to version 5.2.0 Artemis. Note that the configuration file postgresql.conf may be overwritten during the PostgreSQL upgrade.
Important: During the upgrade, a backup copy of the db_pg folder is created (e.g., db_pg_20241209121756). This backup contains the original postgresql.conf file, ensuring that no configuration settings are lost. If required, settings from this backup can be restored after the upgrade.
It is recommended to use the PostgreSQL command ALTER SYSTEM instead of modifying the postgresql.conf file directly (see PostgreSQL documentation). Configuration changes made with ALTER SYSTEM are stored in the postgresql.auto.conf file, which is not affected during a PostgreSQL upgrade.
SEP sesam data mover for VMware vSphere
In SEP sesam version 5.2.0 Artemis, the SEP sesam Server and vSphere data movers must be running the same version. After updating the SEP sesam Server to 5.2.0 Artemis, make sure to update all vSphere data movers to the same version.
License requirements for SEP Immutable Storage – SiS
The license for SEP Immutable Storage (SiS) is not included in the SEP sesam Classic and VM Essential licenses. SiS can be used with a Unit, MSP Unit and SEP sesam Volume licenses. If you are using an SiS store, review your licensing model before upgrading to version 5.2.0 Artemis to ensure compliance. If needed, contact SEP support for assistance.
After upgrading to version 5.2.0 Artemis, using an SiS store without the appropriate license may result in a license violation.
VM Essential Edition license
The issue where the VM Essential Edition license was incorrectly covering 50 virtual machines per hypervisor has been resolved. The license now correctly covers up to 50 virtual machines in total across all hypervisors. For more details, see Licensing.
User management
The user roles "operator," "restore," and "backup" are no longer supported in the GUI, and login attempts with these roles will be rejected. Users assigned to these roles can either switch to the Web UI or have their roles updated in the GUI.
Cloud-based Si3 deduplication store with Object Lock
In the beta release of SEP sesam version 5.2.0 Artemis, S3 Object Lock presents certain issues and is currently not supported for cloud-based Si3 deduplication stores. This functionality is under development and a fix will be provided.

Discontinued systems and features

Discontinued OS versions

SEP sesam Server component is no longer available for the following operating systems and versions:

  • SLES 12
  • Debian 10 (Buster)
Discontinued Java versions

Java 11/OpenJDK 11 is no longer supported. The minimum required version for the SEP sesam GUI component is now Java 17/OpenJDK 17, however, it is highly recommended to use Java 21/OpenJDK 21.

Note
Before updating, make sure to check the [JAVA] section of the sm.ini file and remove any references to Java 11.
Discontinued vSphere versions

The Windows installation of the SEP sesam Client component no longer includes the sbc linked to OpenSSL 1.0.2, which was located in the subfolder bin\sesam\sbc_ssl102. As a result, support for vSphere versions ≤ 6.5 and VDDK 7.0 or earlier has been discontinued.

vSphere versions 8.0, 7.0, and 6.7 are supported with VDDK 8.0 Update 2 using OpenSSL 3.0 (see: virtual-disk-development-kit-80-update-2-release-notes).

Discontinued Si3 V1 data store

The Si3 V1 data store is discontinued and is no longer available.

If you are still using an Si3 V1 data store, it is required to migrate to Si3 V2 to ensure continued support and compatibility with future updates. For detailed instructions see Configuring Si3 Deduplication Store, or contact SEP support for assistance.

Discontinued IMG backup type on VMware

On VMware, the IMG backup type for vSphere environments is no longer available. It is replaced by the CBT (Changed Block Tracking) backup type and all existing IMG backup tasks for vSphere will be automatically updated to use the CBT backup type.

Warning
After updating to version 5.2.0 Artemis, the first run of any previous IMG backups will execute at the FULL backup level instead of DIFF or INCR.
Discontinued restore procedure in the GUI

In the GUI, the restore procedure (Restore wizard) is no longer available. The web-based Restore Assistant provides full restore functionality for both standard and specialized restore types and supports a wide range of data sources. Together with the Web UI for monitoring and managing your SEP sesam environment, these web interfaces are gradually replacing the standard desktop GUI.

Deprecated CTRL client access mode

The CTRL access mode between SEP sesam Server and Client is treated as deprecated and will no longer be available in the next release. Therefore, in this release the access mode for clients with CTRL access mode will be replaced by SMSSH mode as far as possible.

It is recommended to change the use of the CTRL access mode to SMSSH before updating the clients to version 5.2.0 Artemis.

New features in 5.2.0 Artemis

Improved support for Proxmox VE backup and restore

For virtual machines in Proxmox VE, SEP sesam provides advanced integration when used with storage systems that support snapshot capabilities, such as LVM with thin provisioning, ZFS or Ceph RBD. Depending on which storage system is used, different backup methods are available - LVM, ZFS, and Ceph RBD. If storage types are mixed or no suitable method is available, VZDUMP captures the entire VM. Before performing backup, SEP sesam checks the disk configuration for a VM and if necessary changes the selected backup method.

Azure VM Extension

SEP sesam now supports backup and restore of Azure Virtual Machines (VMs). This feature enables integration with Azure VM environment, providing capabilities to back up entire VMs, including the operating system, system state, and all attached disks, without downtime. With Azure snapshot technology, SEP sesam ensures application-consistent backups with flexible storage options and efficient recovery capabilities.

Crossover Backup Server Replication

SEP sesam Crossover Backup Server Replication (CBSR) enables a SEP sesam Server to connect in read-only mode to an Si3 datastore on another SEP sesam Server. This allows the second server to replicate and import backups from the primary server to a separate storage location, enhancing data protection.

Cloud-based SEP sesam Server Disaster Recovery

SEP sesam now offers improved SEP sesam Server Disaster Recovery process by saving full export of the bootstrap database to an Si3 deduplication store, allowing you to back up your SEP sesam Server to cloud storage, such as S3 or Azure. This eliminates the need to manage sesam database files from email attachments and removes file size limitations. With complete SEP sesam Server information securely stored and accessible, the disaster recovery procedure becomes faster, simpler, and more reliable.

New Web UI workflows and actions

SEP sesam introduces enhanced workflows and improved object handling in the Web UI, supporting a wide range of daily tasks and gradually replacing the GUI for everyday operations. The detailed view of nearly all SEP sesam objects has been improved and now includes frequently used actions and configuration options.

Two new assistants are available:

  • Storage Configuration Assistant that provides guided setup for various datastore types including RDS setup, for example, Path, Si3, and HPE StoreOnce.
  • Backup Configuration Assistant that guides you through the entire backup configuration process, including client setup, task creation, and scheduling. The assistant automatically detects the supported backup types for the selected client.

Additionally, Immediate Start action is available from object details or the context menu, allowing you to directly start any SEP sesam task.

New option for advanced event scheduling

New option no-start-active-full is available to prevent queuing of incremental or differential backups while a full backup is running. This option helps avoid multiple redundant backups, which can clutter the database and complicate the backup chain, making restore operations more difficult.

Setting network bandwidth limit for SEP sesam tasks

You can now limit the network bandwidth used by SEP sesam operations to prevent them from consuming all available network resources. By setting read and write bandwidth limits (in MB/s), you can optimize resource usage and ensure other network activities remain unaffected. Bandwidth limits can be configured using the -o bwlimit=<value> option in the task configuration to define a limit for a specific task, or by setting environment variables BWLIMIT, BWLIMIT_READ, and BWLIMIT_WRITE to control read and write limits globally.

Improvements in 5.2.0 Artemis

Automatic failover for devices, RDS, and media (Beta)

SEP sesam introduces automatic failover mechanisms for storage. For example, if a datastore media pool is full, it can switch to a tape media pool. Currently, supported failover options include using SPARE pools for tape devices and load balancing for 'Path' datastores.

Improved network and data security
  • TLS 1.1 is disabled by default to enhance data protection.
  • FTP protocol is disabled by default to improve security of network traffic. However, if this protocol is still required, it can be enabled. See Disabling unsecure transport modes for details.
  • STPD-HTTPS blocks outdated and insecure protocols and ciphers, including TLS 1.0/1.1, SSL 3.0, ARCFOUR-128/40, 3DES-CBC, DES-CBC, and 3DES-PGP-CFB.
  • Latest version of OpenSSL 3.4.0 (previously 3.2) is integrated for improved encryption and security.
Authentication and authorization
  • Multi-Factor Authentication (MFA): Two-Factor Authentication (2FA) options now include email, certificates, or one-time passwords (OTP). Administrators can enforce a MFA type for all users (global settings key gui.auth.mfa.force_type).
  • Password Management: Improvements include options for setting a custom date for password expiration, locking user accounts after multiple failed login attempts (global settings key gui.auth.pw.max_failure_count), and configurable password complexity requirements, such as minimum length, character types, and the inclusion of spaces.
Backup
  • vSphere VM with configured vTPM can be successfully backed up in online mode.
Web UI
  • Extensive usability testing led to numerous improvements across the SEP sesam Web UI, focusing on improving clarity, functionality, and user experience.
  • Improved security features with support for Two-Factor Authentication (MFA) using email, certificate, or one-time password (OTP), users can now change their own password.
  • Added checks for EULA acceptance at startup or after login, users must accept EULA before continuing.
  • Improved alerts and notifications for license expiration and maintenance status.
  • Enhanced license management, including license upload as ZIP file and improved expiration handling.
  • Enhanced session timeout handling, including warning pop-ups, active mount checks, and improved redirection.
  • New Customer Experience (SCE) tab in user settings enables activating/deactivating participation in the program.
  • New dashboard pie charts for last migration and restore state.
  • New weather icon indicators for last backup state showing trends in stability.
  • Active mounts are shown in dashboard Server Status widget.
  • Dashboard enhancements include saveset copy counts for migrations and capacity usage bars for media pools.
  • Improved Gantt charts with options for group and task type filtering.
  • New option to resume canceled backups using the last successful FULL backup.
  • Improved task group assignment, improved workflows for object activation, deactivation, and deletion.
  • Added checks of access and update state for client.
  • Enhanced job timelines, showing finished jobs for 3 minutes after completion.
  • Improved multi-selection filters across views, with partial text search and "select all" options.
  • Enhanced tape/media management features include added date format toggle, drive state in properties, and drive online/offline actions, detailed display includes new columns for write protection, media state, and highlight of current drive.
  • Backup task enhancements include display of backup subtype (e.g., vSphere CBT, Hyper-V RTC/VSS), and display of SBC transfer start time in tables and timelines
  • Support for setting a data mover added to task and task group event configuration.
  • Prevented start/restart of jobs for deactivated clients or tasks.
Restore Assistant
  • Many improvements and fixes to enhance usability and efficiency.
  • Enhanced management of active mounts with improved cleanup processes, mount operations enable viewing and downloading logs for active or successful mounts.
  • Proxmox: Added new features, including mount functionality, additional source information, and options for overwrite or no-overwrite during restores.
CLI
  • Improved performance of the CLI, including faster startup and command execution.
  • The parameter -Z (lifetime) accepts input as a specific date in the format yyyy-mm-dd hh:mm:ss, or as a time period in the format hh:mm.
  • Start restore task: New parameter -w to enable relocation during restore operations.
  • Add/modify interface: New parameter -t to set the i_type of an interface.
  • Start media pool event: For consistency across CLI objects, parameter -B replaced parameter -y (start time) (-y remains supported for backward compatibility).
  • Migrate: New parameters -K (blocking date), -X (execution flag), -x (start time), -k (end-of-life date), removed parameter -T (source interface).
  • Start replication event: New parameters -x (start time), -d (source drive).
  • Start restore event: New parameter -B (start time).
  • Start task: New parameter -B (start time).
  • Add task: New parameter -S (full source).
  • Task group: New parameter -h to specify the data mover.
  • Client: new parameter rename
  • Saveset: The drive number is required to remove a saveset: -d (drive number).
  • For weekly schedules, the duration of the sub-recurrence (-r) is limited to a maximum of 23:59 hours.
  • User management: New options -R 1 to reset the OTP secret for a user (the user must re-scan the QR code with their authenticator app), -g 1 and -r 1 to generate or remove a Sesam API key for a user.

New supported systems and integrations

  • Windows Server 2025
  • BSR Pro version 20.1.336 (also for Windows 11/Windows Server 2025)
  • Azure VM

Known issues and limitations

Note
Antivirus programs may disrupt network communication and cause SEP sesam processes, such as backup and replication, to fail. One program that is known to cause SEP sesam processes to terminate is Sophos Firewall with IPS (Intrusion Prevention System) enabled. Make sure that there are no antivirus, firewall, IDS or IPS programs preventing interaction with SEP sesam.
5.2.0 Artemis known issues:

Severity: MAJOR

SEP sesam v. 5.2.0.6 - (#34661) In Restore Assistant, target storage selection is unavailable for some virtual backup types
In the Restore Assistant, the target storage selection list is empty for virtual backup types other than VMware vSphere and Proxmox VE. As a result, a storage location cannot be selected during task configuration.
Solution: SEP is working on this issue and plans to provide a solution.

Severity: NORMAL

SEP sesam v. 5.2.0.x - (#32971) Selective Windows path restore fails with "Next item or ESET is expected" for SPARSE files
Selective restore of individual files or folders on Windows may fail with the error message Next item or ESET is expected when restoring from backups that include SPARSE files. This is caused by an incorrect data length value written in the LISv2 format, leading to restore failure.
Solution: SEP is working on this issue and plans to provide a solution with the next release.
SEP sesam v. 5.2.0.x - (#31967) In the Web UI, the EULA cannot be accepted
After upgrading to SEP sesam version 5.2.0 Artemis, you must first accept the End User License Agreement (EULA). The EULA cannot be accepted through the Web UI. You must launch the GUI to accept the EULA, before you can proceed using the Web UI.
Solution: SEP is working on this issue and plans to provide a solution.
SEP sesam v. 5.2.0.6 - (#34649) Backup fails if backup source path contains a comma
If the specified source location path for a backup includes a comma (e.g., G:\with,comma), SEP sesam incorrectly parses it as two separate paths: G:\with and comma. As a result, the backup fails due to an unknown source path.
Solution: SEP is working on this issue and plans to provide a solution.
SEP sesam v. 5.2.0.x - (#34663) On OES Linux, FTP protocol is not used with -S <hostname>:11001 setting
On OES Linux systems, when a network interface is configured using a hostname and port number (e.g., -S server:11001), the sbc_smdr module incorrectly uses the HTTP protocol instead of FTP for data transfer. For more information, see also Disabling Unsecure Transport Modes.
Solution: SEP is working on this issue and plans to provide a solution.


Discontinued systems

In SEP sesam Artemis, the following OS versions are no longer supported:

  • SLES 12
  • Debian 10 (Buster)

The following systems are no longer supported:

  • Java 11/OpenJDK 11
  • vSphere 6.5
  • VDDK 7.0.3

You can continue using the last available version of SEP sesam on these operating systems, but SEP AG no longer provides updates or fixes for the specified versions.

For SEP sesam Client versions, backward compatibility is maintained and the last available versions for a platform are continuously supported. On older platforms you can use older versions of SEP sesam Client component, but it is recommended to combine such clients with the latest versions of SEP sesam Server and RDS components.

For details on discontinued systems, see Unsupported OS. For a complete list of supported SEP sesam Clients, see SEP sesam Support Matrix.

End of maintenance and support

Obsolete SEP sesam Server versions

The following versions of SEP sesam are no longer supported:

For the list of all SEP sesam versions see SEP sesam Release Versions.

Change reports

Change report 5.2.0 Artemis


Copyright © SEP GmbH (formerly 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 GmbH. When compiling and designing user documentation SEP GmbH uses great diligence and attempts to deliver accurate and correct information. However, SEP GmbH cannot issue a guarantee for the contents of this manual.
Retrieved from "https://wiki.sep.de/wiki/index.php?title=Release_Notes_5.2.0_Artemis&oldid=392694"