Release Notes 5.0.0 Jaglion V2

Copyright © SEP AG 1999-2024. 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.

SEP sesam 5.0.0.15 Jaglion V2 SP1

Updated: March 6, 2023

• SEP sesam version 5.0.0.15 Jaglion V2 SP1 is a feature, improvement, and bug fix release. Download 5.0.0.15 Jaglion V2 SP1 from SEP Download Center.

	Note
	The installation of 5.0.0.15 Jaglion V2 SP1 is highly recommended, as it contains many fixes and improvements. Currently the version does not require installation of a service pack. For the list of known issues and limitations see section Issues in Jaglion V2 5.0.0.15 SP1 release

This article contains important information about all Jaglion V2 releases, including service packs. It describes new features and new supported systems in Jaglion V2, installation, upgrades, and requirements, and includes a list of fixes included in the service packs.

• What's new
• Enhancements
• License
• New supported systems & integrations
• Installation and upgrades
• SEP sesam Server requirements

• Fixed with 5.0.0.15 SP1 release
• Fixed with 5.0.0.15 release
• Fixed with 5.0.0.12 SP1 release
• Fixed with 5.0.0.11 release
• Fixed with 5.0.0.9 SP3 release
• Issues in Jaglion V2 release
• End of maintenance and support
• Change reports

The new SEP sesam version 5.0.0 Jaglion V2 introduces SiS – SEP Immutable Storage, backup to Azure, powerful Si3 NG now with encryption, and some UI improvements.

What's new

Fighting ransomware with SEP sesam Immutable Storage – SiS

SEP Immutable Storage or SiS is a file storage feature resistant to ransomware attacks, based on Si3 NG on Linux. Even with full admin access to the SEP sesam backup server, attackers cannot delete, modify, or encrypt data stored on SiS. See more.

Backup to Azure

Backup your data directly to Azure Blob storage and restore the items you want directly from there with Si3 NG. See more.

Encrypting Si3 NG Deduplication Store

Si3 NG encryption protects your data from unauthorized access and helps ensure compliance. See more.

Powerful Deduplication Store for Different Storage Locations

Si3 NG boasts excellent performance and support for different storage locations. It requires a valid license. See more.

Enhancements

Backup

• Enforced FULL level backup if the backup was successful (on the client), but errors occurred during post-processing on the server side.
• The new RHV option -a use_virtioscsi allows disk attachment to data mover via bus type VIRTIO_SCSI, default is VIRTIO.

Restore

• RHV restore with overwrite now possible.
• Fixed failed Oracle restore on older systems in combination with newer SEP sesam Server version.

Restore Assistant (web)

• Additional task types are supported: NetIQ/Micro Focus eDirectory, Micro Focus iFolder, PostgreSQL and MySQL. You can perform a regular restore or write your backups to dump files (equivalent to the GUI option Write saveset into file). For more information, see Restore Assistant.
• Many usability improvements and new options: Restore ACLs only option added, restore task name can be changed, link to install guestfs tools added, improved messages when a backup cannot be mounted, preferred media pool can be selected as a mount option, and improved vSphere VMDK selection with clearer use cases.

Si3 NG

Note

The old generation Si3 deduplication store is deprecated. This means that the old generation Si3 is no longer being enhanced, but is still supported until further notice. SEP strongly recommends using the new Si3 NG data store instead, especially if the data is to be stored to S3 Cloud. If you are using an old generation Si3 deduplication store with S3, you will not be able to restore from S3 via the GUI. You can configure a new Si3 NG and an old Si3 in parallel on the same host and replicate from the old Si3 to the Si3 NG store. For details, see Configuring Si3 NG Deduplication Store.

Define № of Si3 NG stores

• Now you can configure the maximum number of Si3 NG/Si3 deduplication stores on RDS. Note that this settings is only visible in Advanced UI mode.
• Improved security for encrypted Si3 NG store. The encryption password is no longer written to the INI file.
• Corrected check of used space by SEP sesam for Si3 NG stores using S3 or Azure storage backend.
• See also information on license.

Certificate-based authentication

Now it is possible to also authenticate the users from external authentication sources (LDAP/AD) via a signed certificate (note that a database-based authentication must be enabled). For details, see Configuring Certificate-Based Authentication.

Automatic exclude for Windows Defender on Windows RDS

All data store-based paths (data store, Si3, Si3 NG) are automatically added to Windows Defender's exclusion criteria. This can help improve performance because these special folders are no longer scanned by Windows Defender.

Enhancements introduced with service packs

• Support for Open Enterprise Server 2022
• Mounting Nutanix VMs on Windows Sesam Server
• Regex exclude files and directories: V. 5.0.0.9 SP1 introduced separate exclusions for files and directories. Because the changed syntax for regexp excludes caused the old syntax to be ignored on Linux for directories, Service Pack 2 reset exclude processing to the previous state (to the default behavior before the change in exclude syntax processing).
• Full support for LTO-9 drives. See also Drives.

UI enhancements

While the look of the user interface has not changed significantly, we have made some subtle improvements to enhance the user experience. For example:

UI Modes

We have reduced the number of available UI modes (in the GUI) to two, so they are synchronized with the Web UI. You can select the appropriate UI mode: simple or advanced, under Configuration - > Defaults - > General. (The former advanced GUI mode is now replaced by simple mode, while the former expert mode is replaced by advanced.) See Selecting UI mode.

Enhanced Drive dialog

When creating a new drive in the New Drive dialog for the drive type "DISK _STORE" new settings are available. This allows you to split channels according to priority and ensure that higher priority jobs get preference. For details on priorities, see Setting Event Priorities.

Select restore interfaces

Restore interfaces

You can select the Restore mode (restore interfaces) that are available for restore and displayed in the context menu. It is recommended to use the web-based Restore Assistant instead of the Legacy restore (deprecated) option, which refers to the GUI restore wizard. See Selecting restore interface.

License

SEP sesam software requires a valid license. For more information, see Licensing.

• Version 5.0.0.9 introduces a check for the Si3 NG capacity so after an update from version Jaglion (5.0.0.[34]) to a new version the licensed deduplication storage may no longer be sufficient. This only affects customers who are already using Si3 NG deduplication store.
• This license check does not affect customers with SEP sesam Volume License that does not count the backup storage.
• License violation leads to 15 days remaining run time, during which the license issue must be fixed in either of two ways:
  1. The capacity of the used Si3 + Si3 NG stores must be fixed (SEP_DeDup_TB)
  2. Contact sales@sep.de and order a replacement license with the correct amount of backup storage TB. Then install it on SEP sesam Server (see Licensing FAQs).

New supported systems and integrations

Windows 11

SEP sesam Server 5.0.0.9 Jaglion V2 supports Windows 11 (without BSR Windows Disaster Recovery).

• BSR Windows Disaster Recovery for Windows 11 is expected to be fully supported ASAP.

Open Enterprise Server 2022

Introduced with Jaglion V2 SP3.

Expanded support for S3 compatible storage

SEP sesam supports S3 as a generic interface based on the new deduplication store Si3 NG. For details on newly supported S3 targets, see SEP sesam Support Matrix – Object Storage.

Debian and Ubuntu supported with HPE StoreOnce Catalyst

For a full list of supported OS for SEP sesam SEP sesam integration with HPE StoreOnce Catalyst, see SEP sesam Support Matrix – HPE StoreOnce Catalyst.

For new supported systems with previous Jaglion version, see Jaglion Release Notes. For a complete list of supported OS and databases, see SEP sesam Support Matrix.

Discontinued systems

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

Installation and upgrades

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

SEP sesam Jaglion V2 5.0.0.15 was released on 8 February 2023. A direct upgrade from versions 4.4.3.X to version Jaglion V2 5.0.0.15 is supported.
The latest released Jaglion V2 versions are:

• SEP sesam 5.0.0.15 Linux – released: 8 February 2023.
• SEP sesam 5.0.0.15 Windows – released: 8 February 2023.

Linux specific

In order to meet all required dependencies for the SEP sesam Client packages on SLES 15 SP1 or SP2, it may be required to activate the following package modules prior to SEP sesam installation:

Module-Basesystem
Module-Server-Applications
Module-Legacy

These modules are part of the installation DVD; in case no online subscription is available, they can be added via:

zypper ar dvd:/Module-Server-Applications DVD-Server 
zypper ar dvd:/Module-Basesystem DVD-BASE
zypper ar dvd:/Module-Legacy DVD-Legacy 

For details, see Installation on Linux. For a list of supported Linux versions, see the SEP sesam Support Matrix.

Windows specific

Installation

• When installing SEP sesam Server on Windows, you can now choose to install a PostgreSQL database that is included with the SEP sesam installer (or use the SQLite that does not require a server to be set up and is used with SEP sesam by default). For details, see Installation on Microsoft Windows.
• Upgrading from SQLite to PostgreSQL is currently not supported, except with the help of SEP support.
• SEP sesam recommends the use of PostgreSQL for complex enterprise environments with many tasks, high performance expectations (due to PostgreSQL's ability to support multiple concurrent writers and read/write at fast speeds), and security and authentication requirements.

For a list of supported Windows versions, see the SEP sesam Support Matrix.

Upgrade

SEP sesam Server and Client components should be upgraded to the latest version during the upgrade process. This ensures that SEP sesam Clients are fully protected. Customers with a valid license are eligible for a free upgrade of SEP sesam to any new release for the duration of the license. See also Updating SEP sesam and Remote Installation of Windows Clients.

Post update task

Version 5.0.0.9 uses the enhanced LIS file format, which increases performance at least 10 times. After updating to version 5.0.0.9, a new full vSphere backup should be performed to allow mounting and attaching VMDKs.

SEP sesam Server requirements

Java

The SEP sesam GUI is based on Java and requires a Java Runtime Environment (JRE).

• SEP sesam 5.0.0.9 Jaglion V2 Service Packs require Java 11.
• SEP sesam 5.0.0.9 Jaglion V2 supports Java 11 and Java 8. If you are still using Java 8, we strongly recommend that you migrate your server to Java 11 as this is the last version of SEP sesam that supports Java 8.
  • Java 8 support has already been discontinued with SEP sesam version 5.0.0.9 SP1, which requires Java 11.
• SEP sesam 5.0.0.9 Jaglion V2, including Service Packs, support Java 17 only on demand. See SEP sesam installation fails if only Java 17 is installed for details.

The required Java version depends on the SEP sesam version.

Previous release

• Release notes for SEP sesam 5.0.0 Jaglion

Fixes: SEP sesam Server 5.0.0.15 Jaglion V2 SP1

	Note
	The installation of 5.0.0.15 Jaglion V2 SP1 is highly recommended, as it contains many fixes and improvements.

Fixed with 5.0.0.15 Jaglion V2 SP1:

Command event cannot start a shell script, e.g. sbc_oracle_rman.sh Parsing of commands was corrected and command events work as expected. Improved Tape Init Tape initialization works faster and with removal of meta files of savesets with older file names containing counter >0. Multistream backup with EOM fails with message Failed to write Tape Trailer. Tape is already closed. (Linux only) Handling of Tape Trailer write is improved. The full list of fixes can be found in the Change report Jaglion V2 Service Packs.

Fixes: SEP sesam Server 5.0.0.15 Jaglion V2

Fixed with 5.0.0.15 Jaglion V2:

Hyper-V RCT Support Virtual machine backups with resilient change tracking (RCT) is now supported with COPY/FULL/DIFF/INCR Backup and VM mount for Single File Restore (SFR). New feature - Termination of SEP sesam command events Wildcards '$PID' and '$CMD' can be used in specific abort commands. Backup with many sources should not fail if one of the sources does not exist Use option -o ignore_missing_source to allow SBC processing in such case. Note that backup will complete with the warning state. The full list of fixes can be found in the Change report Jaglion V2 Service Packs.

Fixes: SEP sesam Server 5.0.0.12 Jaglion V2 SP1

Fixed with 5.0.0.12 Jaglion V2 SP1:

sm_data_store removed all files from DataStore if a file named .data was found on DataStore During problems with DB2 backup, a saveset with an empty name was created. The DataStore cleanup task (sm_data_store check_db -o remove all) in such cases removed all files from that DataStore. Selective Path restore - not all required items are restored. Problem: Journal file (LIS) with different encoded lines (ISO8859 and UTF-8). Since update to 5.0.0.9 on Linux tape encryption could not be turned on during backup Solution: Due to a variable overflow the salt key was not set correctly. Web-UI Restore Assistant VMware Restore to original VM not possible vSphere SFR with different pools and selection of a new Hyper-V restore target. Some other fixes in SP1 Selective restore from SAYTEC sayFUSE devices failed with SMS user is not allowed to save on this directory Canceling vSphere backups sometimes does not end subtask backup Analysis of backup log with warnings leads to a failed backup status: SBC logging without final state message. Queued job sm_sbc_com_ext is not removed when SAP Hana backup runs into timeout. Windows: sm_sshd executes 3 icacls processes during each processs start. Windows: sbc crashes on path backups with large exclude lists. Restore of UNC folder runs into an error because the parent folder cannot be overwritten. Since Jaglion V2 the configured clients in command events have been ignored. Now they are used again, as default when creating a new command event or in case of an immediate start. All MS SQL data bases are backed up, if source db name starts with all (e.g. db name is allris) HCL Domino incremental backup 'The number of objects saved from SBC (...) and the (0) LIS file does not match' Backup of source with special characters does not work (since version 5.0) The full list of fixes can be found in the Change report Jaglion V2 Service Packs.

Fixes: SEP sesam Server 5.0.0.11 Jaglion V2

	Note
	Version 5.0.0.11 contains all improvements and bug fixes of 5.0.0.9 SP3. If you already updated to 5.0.0.9 with SP3, it is not necessary to update to 5.0.0.11.

Fixed with 5.0.0.11 Jaglion V2:

Manually added exclude patterns have been deleted during update on backup clients. Version 5.0.0.11 (or higher) retains manually added exclude patterns on backup Clients. Note that 5.0.0.11 contains all fixes from previous Jaglion V2 versions. It is not required to use lower versions and service packs and it even may remove exclude patterns. So update from Beefalo V2 (e.g. 4.4.3.84 or .86) should be done with at least 5.0.0.11 Jaglion V2.

Fixes: SEP sesam Server 5.0.0.9 Jaglion V2 SP3

	Note
	Service packs are cumulative and contain all released bug fixes for Jaglion V2.

Fixed with 5.0.0.9 Jaglion V2 SP3:

This SP3 fixes the problem with the purge process that was reintroduced in version 5.0.0.9 and could lead to the accidental removal of an otherwise valid backup. SP3 also contains minor fixes, among others: Windows: sm_qm hangs if Sesam Queue Manager (sm_qm_main) is terminated. Linux SBC skips the first directory if the backup source directory contains a .nosbc file. After applying Service Pack 1 to version 5.0.0.9, on Linux exclude list processing via the exclude file is ignored. The data store file system check (FSCK) does not take care of ongoing migrations. Backing up to a media pool that has no more free tapes does not work, even if using media from another pool is allowed. The full list of fixes can be found in the Change report Jaglion V2 Service Packs.

Fixes: SEP sesam Server 5.0.0.9 Jaglion V2 SP2

Fixed with 5.0.0.9 Jaglion V2 SP2:

SEP sesam v. 5.0.0.9 SP1 – The old syntax for regexp excludes no longer works for directories in SP1 (Linux only) SP1 introduced a changed syntax for regexp excludes to separate excludes for files and directories. If exclude ends with a trailing slash "/$" (e.g. .tmp/$), it is recognized as directory exclude regex. If there is no trailing slash "/" at the end (e.g. .tmp), it is recognized as file exclude regex. Now to exclude a folder, the syntax is: \./folder/folder_to_exclude/$ The problem is that the old syntax usually does not end with ".../$", so that the processing of the exclude list for the directories via the exclude file on Linux is ignored. Resolution: Fixed. Download SP2 and install. Service Pack 2 reverts exclude processing to its previous state, that is, to the default behavior before the exclude syntax processing was changed (-o excl=regexp; any regex pattern added to the directory AND file filter). Migration does not compare checksum anymore since Jaglion. sm_reformat_lis can't copy SharePoint Server LIS file.

Fixes: SEP sesam Server 5.0.0.9 Jaglion V2 SP1

Fixed with 5.0.0.9 Jaglion V2 SP1:

SEP sesam v. 5.0.0.9 – Concurrent backups of Nutanix VMs lead to backup of wrong VM snapshot disks Multiple backups result in backing up incorrect Nutanix VM snapshot disks because the same UUID was used to create the VM snapshot. Unique client identifier to request for Nutanix UUID is missing. SEP sesam v. 5.0.0.9 – External job remains in queue when submit timeout expires External job remains in queue when submit timeout expires due to incorrect check for backup operation. SEP sesam v. 5.0.0.3-5.0.0.9 – Problems with Si3 NG on S3 ⇒ Several issues with Si3 NG on S3 have been fixed, upgrade to SP1 is highly recommended. SEP sesam v. 5.0.0.9 – OVF file is not detected as missing during vSphere backup When performing a vSphere backup, the .ovf and other configuration files needed for the restore are missing even though the backup is successful. The restore cannot be performed without the .ovf file. SEP sesam v. 5.0.0.9 – The GUI shows an incorrect maintenance expiration message instead of the more important license expiration message The license check sends a maintenance expired notification instead of license expiration. This can cause the license to expire without being notified and consequently not allowing backup jobs to be executed. SEP sesam v. 5.0.0.9 – The shown content for the generation SFR of vSphere might be incomplete Generation single file restore (SFR) of vSphere displays the contents of the FULL backup when the base backup has been done via image. Thus, only the FULL backup displays the correct content, but when you run FULL and INC, only the content of FULL is displayed. SEP sesam v. 5.0.0.4-5.0.0.9 – If two shared drives are used for backup, another backup on the already free drive does not start The backup on the already free shared drive will not be started once the first backup started on this shared drive is finished. The second drive remains in the pending state, even if the backup on the first drive is completed. SEP sesam v. 5.0.0.4-5.0.0.9 – Jobs can get stuck in the queue even though the drive resources are free Jobs get stuck in the pending queue and are not processed or are processed very late even though the drive resources are available. This problem is caused by the queue manager due to an incorrect priority check. SEP sesam v. 5.0.0.9 – The sesam bootstrap DB export does not contain information about the migrated sesam backup If a SEP sesam backup is performed and then migrated, the bootstrap DB export lacks the information that the backup was migrated. This only allows a disaster recovery from the original backup, but not from the migrated backup. SEP sesam v. 5.0.0.9 – The incorrect operation of Cancel Current Running Activities stops all running sm_break_task processes The Cancel Current Running Activities function updates the status of all tasks that are still running with a slight delay and causes all concurrent sm_break_task processes to be stopped. Since sm_break_task processes are stopped upon the regular check of the status of the result entry, this results in the running processes not being stopped. Consequently, such jobs can no longer be detected via DB:results.state and can only be stopped manually. SEP sesam v. 5.0.0.9 – Backup of ACLs on a CIFS share fails with ERROR_PRIVILEGE_NOT_HELD (1314) Backups of ACLs over a CIFS share with local and domain admin fail due to access restrictions. The following error occurs:ERROR_PRIVILEGE_NOT_HELD (1314) A required privilege is not held by the client. SEP sesam v. 4.4.3-5.0.0.9 – Backup of virtual machines in subdirectories fails If the virtual machines on the data store are located in a subfolder, the VM backup fails because SEP sesam cannot export the .ovf file (the .ovf file is not found in the specified directory). SEP sesam v. 5.0.0.9 – UTF-8 conversion could not be executed, wcstombs returned an error Wide character could not be converted (84) Microsoft Windows Unicode with 4 bytes could not be converted on Linux RDS. SEP sesam v. 5.0.0.9 – Saveset is not removed from a data store when immediate delete is selected in the GUI After performing a backup to a data store, if you attempt to delete a saveset in the GUI data store properties -> tab Savesets -> select a saveset and right click Delete without selecting the option Delay deletion to next purge, the saveset is deleted from DB, but not from the filesystem. Note that deleting the backup works correctly. SEP sesam v. 5.0.0.9 – Deactivated VM tasks are not excluded from the license count After deactivating VM tasks that exceed the number of allowed tasks defined by the license, a license violation still occurs. SEP sesam v. 5.0.0.9 – The status of a data store is incorrectly displayed as OK when RDS is unreachable The status of a data store shows the error message CURL failed with error code: Timeout was reached because the server is unreachable. However, the status check of the datastore is displayed as OK. SEP sesam v. 5.0.0.9 – After a restore of the child task that ended with a warning, the parent restore task is still active After a restore of the child task that ended with a warning, sm_break fails to terminate the parent restore task. This happens because the process ended, but the state was still active. SEP sesam v. 4.4.3.86-5.0.0.9 – DB:results.stop_time written in wrong format Incorrect format for DB:results.stop_time . E.g., the date and time 2022-06-06 11:22:44 is incorrectly converted to 20220606112244129, where it should be displayed as month-day-year hour-minute-second with a hyphen as a separator. SEP sesam v. 5.0.0.9 – When three backup filters are applied in GUI -> Monitoring -> Last Backup State, an exception occurs When three filters are applied in GUI Monitoring -> Last Backup State, an exception with 'syntax error at or near "AND"' occurs SEP sesam v. 5.0.0.9 – Filters Migration or Replication in GUI -> Monitoring -> Last Backup State do not work Since migrations and replications are no longer represented in the DB:results table, the Migration and Replication filters have no effect. BUGFIX Fixing the double free problem in sm_qm_main that can trigger sm_qm_main crash.

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.0.0.x Jaglion V2 known issues:

Severity: MAJOR SEP sesam v. 5.0.0.11 - On HPE Catalyst or Si3 NG stores all files get deleted from a datastore with command sm_data_store check_db -o remove_all The command sm_data_store check_db -o remove_all is used to remove all inconsistencies in the sesam database and the data files of a datastore. If a file named '.data' is found on the HPE Catalyst or Si3 NG datastore, all files from the datastore will get deleted with this command. Workaround: List the information about the saveset inconsistencies in the sesam database and the data files of the datastore using sm_data_store check_db. If a file named '.data' is found, do not run the sm_data_store check_db -o remove_all. Resolution: Fixed with 5.0.0.12 SP1. SEP sesam v. 5.0.0.9 – In rare cases, the backup is incorrectly marked as successful In some rare cases, the backup is incorrectly marked as successful when backing up to Si3 deduplication store fails with error java.io.IOException: The device is not ready. In SEP sesam specific error parsing is implemented to detect false failed backups. If an error occurs in the system during backup that does not impact the restorability of the backup, SEP sesam recognizes such errors and marks these backups as successful. The error java.io.IOException: The device is not ready can occur in case the backup target is an Si3 v1 deduplication store and FTP transport is used for backup connection. Error parsing skips that message as if it is not affecting the backup. Workaround: You can use HTTP instead od FTP transport for backup connection. Resolution: In SEP sesam error parsing was changed to be more unique and catch such exceptions, so that failed backups are not marked as successful. Fixed with 5.0.0.12 SP1. SEP sesam v. 5.0.0.9 – Manually added exclude patterns get deleted during update Manually added exclude patterns have been deleted during update on backup clients. The Sesam server update preserved exclude patterns on the server only. Resolution: If you have sm.ini [SBC_EXCLUDE] patterns set manually, avoid update with SEP sesam version lower than 5.0.0.11 on backup Clients. Perform update with version equal or higher 5.0.0.11 to retain manually added exclude patterns. See Creating exclude list. SEP sesam v. 5.0.0.9 – Possible data loss due to a faulty purge function Due to the missing database entry by the purge process ('Delete everything older than the oldest Sesam day'), an FSCK error may occur as sm_pur_status could accidentally remove backup information for migrated savesets. Although the migrated version of the backup still exists, it is no longer listed in the database. Consequently, the administrator may decide to use the function Clean up Data Store to fix the error, which results in the deletion of the migrated saveset and loss of data. Resolution: Fixed with version 5.0.0.9 SP3 or higher. SEP sesam v. 5.0.0.2-5.0.0.9 – Linux backup silently skips a directory if .nosbc file is part of backup source (Linux only) When backing up a backup source that contains one or more .nosbc files, a directory is silently skipped, but the backup is marked as successful. For example, if there is a backup source /data that contains /data/ds1/.nosbc, /data/ds1/pages/ and /data/ds1/trash/, then the pages/ or trash/ directories are not backed up. If a backup source does not contain a .nosbc file, all files are backed up successfully. Workaround: Since sbc incorrectly excludes a directory from backup if a file .nosbc is part of the backup source, use the -o noexcl switch in the backup options (backup task properties, tab Options -> Backup options) when backing up a backup source with a .nosbc file. Resolution: Fixed with version 5.0.0.11 SEP sesam v. 5.0.0.3-5.0.0.9 – Hyper-V restore of Hyper-V RCT backup fails with error When restoring a Hyper-V VM from a Hyper-V VM RTC backup under a new VM name, the restore fails with an error: Failed to read metadata file. Resolution: Fixed with version 5.0.0.11 Severity: NORMAL SEP sesam v. 5.0.0.15 - On Linux vSphere restore fails with SBC core dump when RHEL 8.6 is used as the data mover Fix: Install VDDK version 7.0.3 on the data mover. SEP sesam v. 5.0.0.15 - Command event cannot start a shell script The command event does not work correctly if the command is a shell script, for example sbc_oracle_rman.sh, executed under a specific user, or if the command ends with -d {number} (last 2 arguments). External commands fail with No such file or directory when not executed as user root on Linux. Workaround: You can change command arguments, e.g. instead of "sm_loader unload -l 1 -d 2" use "sm_loader unload -d 2 -l 1 -v 1" or "sm_loader unload -d 2 -l 1". Resolution: SEP is working on this issue and will provide a fix as soon as possible. If you have encountered this problem, SEP support can provide a hotfix. SEP sesam v. 5.0.0.9 SP1 – The old syntax for regexp excludes no longer works for directories in SP1 (Linux only) SP1 introduced a changed syntax for regexp excludes to separate excludes for files and directories. If exclude ends with a trailing slash "/$" (e.g. .tmp/$), it is recognized as directory exclude regex. If there is no trailing slash "/" at the end (e.g. .tmp), it is recognized as file exclude regex. Now to exclude a folder, the syntax is: \./folder/folder_to_exclude/$ The problem is that the old syntax usually does not end with ".../$", so that the processing of the exclude list for the directories via the exclude file on Linux is ignored. Workaround: Change the syntax in the existing tasks to distinguish between excluding files and directories. For details, see Exclude with Regular Expressions. Resolution: Fixed with SP2 for Jaglion V2. Download SP2 and install. Srvice Pack 2 reverts exclude processing to its previous state, that is, to the default behavior before the exclude syntax processing was changed (-o excl=regexp; any regex pattern added to the directory AND file filter). If you have already changed the syntax to match a new behavior, add the following switch to the backup options in the GUI to distinguish between files and folders using ending "/$": -o excl=regexp_split SEP sesam v. 5.0.0.9, incl. Service Packs – SEP sesam installation fails if only Java 17 is installed SEP sesam ≥ 5.0.0.9 Jaglion V2 installation fails if Java 17 is the only Java version installed. Installation succeeds if both Java versions 11 and 17 are installed, as SEP sesam ≥ 5.0.0.9 Jaglion V2 requires Java 11. Java 17 is only supported on demand if the following workaround is applied. Workaround: You can enable the use of Java 17 from the command line with sm_setup set_java_path -f <java_17_installation_path>. Resolution: Java 17 is planned to be supported with the next major release. SEP sesam v. 5.0.0.3-5.0.0.9 – New Hyper-V RCT backups do not support single file restore (via VFS mount) As of 5.0.0 Jaglion, SEP sesam uses Resilient Change Tracking (RCT) by default for Hyper-V backups on Windows Server ≥ 2016 (Hyper-V VM ≥ 6.2). Single file restore (VFS mount) is currently only supported for VM Hyper-V backups without RCT option (old approach with VSS snapshots creating .avhdx files instead of the new Resilient Change Tracking). The new RCT backups have a 'RCT' attribute and the mount option is not shown. For older backups without the 'RCT' attribute, the mount option is available. Workaround: When restoring a Hyper-V RCT backup, perform a regular VM restore of the virtual machine as described in Restoring a Hyper-V virtual machine. Resolution: SEP development is working on a single file restore via mount for Hyper-V RTC backups and will implement it as soon as possible. SEP sesam v. 5.0.0.3-5.0.0.9 – Hyper-V restore fails, if the data store path from the original VM does not exist on the target server Hyper-V restore fails with error Warning: Cannot create item [D:\]: [87] WIN32 API error: 87 - The parameter is incorrect., if the data store path from the original VM does not exist on the target server, regardless of whether the default Hyper-V folder for VMs is used or an existing data store path is set. The original path is always used. Resolution: SEP is working on this issue and will provide a fix as soon as possible. Severity: MINOR SEP sesam v. 5.0.0.x – Clean installation of SEP sesam may fail on RHEL version 8.5 or higher For new installations of SEP sesam on OS versions RHEL 8.5 and 9 using YUM or DNF, the installation may fail because Java is not configured completely during the installation. This is due to the changes in Java RPM installation script. When upgrading an existing version of SEP sesam, this is not an issue. Workaround: We recommend to first install Java version 11 or higher before you start the SEP sesam installation. SEP sesam v. 5.0.0.x – Proxmox VE backup does not work with the client name as plain IP address If the node added to the SEP sesam environment is not set up correctly and an IP address is used as the client name instead of the client's hostname matching the hostname returned by the Proxmox server, the backup fails. Resolution: This problem can only be solved by correctly configuring the Proxmox clients in the SEP sesam environment. For more details on configuring the client name correctly, see Proxmox VE Backup: Adding the Proxmox server (and nodes) to the SEP sesam environment. SEP sesam v. 5.0.0.x – Kopano backup containing non-ASCII characters fails to create index, but backup is marked as successful A Kopano backup containing non-ASCII characters results in the error UnicodeEncodeError: 'ascii' codec can't encode character... Consequently, the mail subject index cannot be created, but the backup is marked as successful. Resolution: The index problem can only be fixed by creating the correct locale: #vi /etc/locale.gen and then enable de_DE.UTF-8 UTF-8 #locale-gen SEP sesam v. 4.4.3.86–5.0.0.x – Initial Seeding functionality temporarily removed As using the Initial Seed option to set up a new Si3 deduplication store for replication resulted in an apparently successful setup, but no data was replicated, the Initial Seeding functionality is no longer available in version 5.0.0.x. It is not yet known whether it will be available again in the future.

End of maintenance and support

Obsolete SEP sesam Server versions

The following versions of SEP sesam are no longer supported:

• SEP sesam 4.4.3 Grolar -> October 2021
• SEP sesam 4.4.3 Tigon V2 -> December 2020
• SEP sesam 4.4.3 Tigon -> September 2020

Discontinued SEP sesam Server OS

The following table lists the last available version of SEP sesam Server or RDS components for specified operating systems. 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.

SEP sesam Release Versions

Operating system	Last available version	Release	Notes
Debian 10 »Buster«	5.1.0.25 Apollon V2	5.1.0 Apollon V2
SLES 12	5.1.0.25 Apollon V2	5.1.0 Apollon V2
Windows Server 2012	5.1.0.7 Apollon	5.1.0 Apollon
RHEL 7	5.1.0.7 Apollon	5.1.0 Apollon
Debian 9 »Stretch«	5.0.0.15 Jaglion V2	5.0.0 Jaglion V2
SLES 11 SP2, SP3, SP4	4.4.3.x Beefalo V2, see notes	4.4.3 Beefalo V2	SEP announced that it would no longer support SLES 11 SP2, SP3, SP4 with SEP sesam Beefalo, but has re-established support for Beefalo V2, where all SEP sesam Beefalo V2 packages (Server, Client, etc.) can be used. However, Beefalo V2 is the last available SEP sesam release for SLES 11 SP2, SP3, SP4 .
Windows Server 2008 R2	4.4.3.x Beefalo V2, see notes	4.4.3 Beefalo V2	SEP announced that it would no longer support SEP sesam Server on Windows Server 2008 R2 with SEP sesam Beefalo, but has re-established this support already in Beefalo. This actually means that the last available SEP sesam Server release for Windows Server 2008 R2 is Beefalo V2.
Ubuntu 16.04	4.4.3.84 Beefalo V2	4.4.3 Beefalo V2
RHEL 6	4.4.3.64 Grolar	4.4.3 Grolar
Debian 8 »Jessie«	4.4.3.64 Grolar	4.4.3 Grolar
Debian 7 »Wheezy«	4.4.3.64 Grolar	4.4.3 Grolar	Version 4.4.3.64 only available for sesam-cli on amd64
Windows Server 2008	4.4.3.64 Grolar	4.4.3 Grolar
Windows 7	4.4.3.64 Grolar	4.4.3 Grolar
Ubuntu 14.04	4.4.3.48 Tigon V2	4.4.3 Tigon V2
All 32-bit operating systems	4.2.2.40	4.2.2	For some operating systems SEP sesam client is still available in 32-bit.
SLES 10	4.2.2.40	4.2.2
RHEL 5	4.2.2.40	4.2.2
Debian 6 »Squeeze«	4.2.2.40	4.2.2	sesam-cli also available in version 4.4.1.22
Windows Server 2003	4.2.2.40	4.2.2
Debian 5 »Lenny«	4.2.1.34	4.2.1
SLES 11 ≤ SP1	4.2.1.34	4.2.1	Initial SLES 11 Release and Servicepack 1

Change reports

• Change report 5.0.0.9 Jaglion V2
• Change report Jaglion V2 Service Packs

See also

SEP sesam Release Versions