Release Notes 5.0.0 Jaglion: Difference between revisions

From SEPsesam
(Fixed typos)
(39 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{Draft}}
{{Draft}}
{{Copyright SEP AG en}}
{{Copyright SEP AG en}}
{{note|SEP AG is pleased to announce that the upcoming version of SEP sesam, v. 5.0.0.1 ''Jaglion'', is currently in the [[SEP_sesam_Release_Versions|beta 1 release phase]]. This document describes known issues for ''beta 1 release'' as well as the most important new features and additional information for the upcoming official release.
*Note that SEP sesam provides SEP sesam ''5.0.0.1 Jaglion beta 1'' as a test program on an "as is" basis and without warranty. Beta version may contain errors and bugs and may cause problems that could lead to system failures and data loss.
*If you are interested in testing the beta version, please register as a beta tester by email to [mailto:beta@sep.de beta@sep.de]. Make sure that you fully '''understand and agree to the terms and conditions''', described in [[Hints for beta testing]], before you start using SEP sesam beta software. }}
<!--{{note|SEP AG is pleased to announce the beta release of SEP sesam 4.4.3 ''Beefalo V2''. If you are interested in testing the beta version, please register as a beta tester by email to [mailto:beta@sep.de beta@sep.de]. Before installing the beta version, make sure that you '''''understand the beta release version status and conditions''''', available at [[Hints for beta testing]].}}-->


== {{anchor|new}}What's new in SEP sesam 5.0.0 ''Jaglion''==
== {{anchor|new}}What's new in SEP sesam 5.0.0 ''Jaglion''==
Line 19: Line 25:
New SEP sesam release 5.0.0 ''Jaglion'' introduces a more powerful and intuitive Web UI, handy new GUI functions, and more consistent and stable internal APIs.   
New SEP sesam release 5.0.0 ''Jaglion'' introduces a more powerful and intuitive Web UI, handy new GUI functions, and more consistent and stable internal APIs.   


===Features at glance===
===Features at a glance===
===== Improvements and bug fixes =====
This release contains a number of improvements and important fixes in various areas and resolves the issue with  [[Release_Notes_5.0.0_Jaglion#fixes|slow tape restore performance]].
 
===== Extended SEP sesam REST API V2 =====
The SEP sesam REST API V2 has been extended to support a wide variety of use cases. A large number of new endpoints have been added. For details, see [https://wiki.sepsoftware.com/wiki/index.php/File:SEP_sesam-REST-API-V2-Jaglion.pdf SEP sesam REST API V2 Jaglion].


===== Enhanced Web UI =====
===== Enhanced Web UI =====
The more advanced and intuitive [[Release_Notes_5.0.0_Jaglion#Web_UI|''Web UI'']] offers the following in addition to monitoring SEP sesam operations: Start backups immediately, restart failed jobs, lock backups, review alerts, set UI mode, and view job and data store details.
The more advanced and intuitive [[Release_Notes_5.0.0_Jaglion#Web_UI|''Web UI'']] offers the following in addition to monitoring SEP sesam operations: Start backups immediately, restart failed jobs, lock backups, review alerts, set UI mode, and view job and data store details.


===== Backup & Restore =====
===== Backup & restore =====
*Now also supported: [[Release_Notes_5.0.0_Jaglion#Nutanix|''Nutanix Acropolis Hypervisor'']] (AHV) backup and restore. Nutanix AHV module is supported on SEP sesam Linux Server and on SEP sesam Windows Server, using a Linux Client as a data mover.  
*Now also supported: [[Release_Notes_5.0.0_Jaglion#Nutanix|''Nutanix Acropolis Hypervisor'']] (AHV) backup and restore. The Nutanix AHV module is supported on SEP sesam Linux Server and on SEP sesam Windows Server, using a Linux Client as a data mover.  
*To simplify backing up multiple VMs, you can [[Release_Notes_5.0.0_Jaglion#automating_backups|''automate the process'']] by automatically generating tasks for VMs that are connected to the same host; in addition, you can also automatically create clients for VMs to which the generated tasks and ACLs can be assigned.  
*To simplify backing up multiple VMs, you can [[Release_Notes_5.0.0_Jaglion#automating_backups|''automate the process'']] by automatically generating tasks for VMs that are connected to the same host; in addition, you can also automatically create clients for VMs to which the generated tasks and ACLs can be assigned.  
*The new [[Release_Notes_5.0.0_Jaglion#OLVM|''Oracle-VM task type'']] is available to perform agentless snapshot-based backups of all OLVM virtual machines.
*The new [[Release_Notes_5.0.0_Jaglion#OLVM|''Oracle-VM task type'']] is available to perform agentless snapshot-based backups of all OLVM virtual machines.
*For direct HPE backups in the cloud, the new data store type ''HPE Cloud Volume'' is available.
*''Si3 deduplication store'' has been improved; the new ''Si3 NG deduplication store'' enables significantly higher deduplication performance.
*For Microsoft Windows Server 2016 or later, the Resilient Change Tracking feature (RCT) is supported to back up Hyper-V virtual machines. Similar to CBT for VMware and Citrix, incremental backup technology RCT for Hyper-V identifies block-level changes and backs up only data that has changed since the last incremental backup.
*''VFS (Sesam virtual file system) performance'' improvements enable 100x faster access to vSphere VMs booted directly from SEP sesam data store.
*When browsing a VMware vSphere server for backup sources, VMs are displayed in the vCenter tree along with the host and clusters. The client browser for VMware now displays a description of the configured backup tasks and details of the VM-related metadata that can be copied.
*For direct HPE backups and especially replications to the cloud, the new data store type [[Release_Notes_5.0.0_Jaglion#Cloud_Volume|''HPE Cloud Volumes'']] is available.
*For Microsoft Windows Server 2016 or later, the [[Release_Notes_5.0.0_Jaglion#RCT|''Resilient Change Tracking (RCT)'']] is supported to back up Hyper-V virtual machines.
*Since ''Jaglion'', the [[Release_Notes_5.0.0_Jaglion#tech_improvements|''locked state'']] is automatically applied to all backups in the chain of the selected backup.
*Since ''Jaglion'', the [[Release_Notes_5.0.0_Jaglion#tech_improvements|''locked state'']] is automatically applied to all backups in the chain of the selected backup.
*When backing up [[Release_Notes_5.0.0_Jaglion#Citrix|''Citrix Hypervisor VMs'']], it is possible to exclude individual virtual disk (VHD) from the backup.
*When backing up [[Release_Notes_5.0.0_Jaglion#Citrix|''Citrix Hypervisor VMs'']], it is possible to exclude individual virtual disk (VHD) from the backup.
*The web restore assistant now supports restore of additional task types (Nutanix AHV, Micro Focus GroupWise, etc.) and additional restore options are available when restoring data online.
**[[Release_Notes_5.0.0_Jaglion#Exchange_restore|''Web Exchange restore'']]: It is possible to perform a single Exchange mailbox database restore with SEP sesam Exchange Recovery Pro via the web interface Restore Assistant (with appropriate rights).
**Now also [[Release_Notes_5.0.0_Jaglion#web_restore|''web single file restore for virtual machines'']] is supported.
**When restoring MS SQL Server databases online, new recovery state options (leave the database ready for use by rolling back uncommitted transactions, etc.) and additional execution options (overwrite existing items with newer/older items from backup and skip ACL settings during restore) are available.


===== Authentication & Authorization =====
===== Web Restore Assistant =====
*The [[Release_Notes_5.0.0_Jaglion#restore_assistant|''web Restore Assistant'']] now supports restoring new task types (Nutanix AHV, Micro Focus GroupWise, etc.) and provides additional restore options.
*Also supported is web [[Release_Notes_5.0.0_Jaglion#web_restore|''single file restore for virtual machines'']].
**[[Release_Notes_5.0.0_Jaglion#Exchange_restore|''Web Exchange restore'']]: It is possible to perform a single Exchange mailbox database restore with SEP sesam Exchange Recovery Pro via the web Restore Assistant (with appropriate rights).
*[[Release_Notes_5.0.0_Jaglion#VMware_sandbox_rst|''VMware sandbox restore via the Restore Assistant '']] offers improved functionality and usability of the recovery options, i.e. the use of run and execution commands of the VMware guest tools.
*[[Release_Notes_5.0.0_Jaglion#MS_SQL|''Restore of MS SQL Server databases using web Restore Assistant'']] is supported with specific recovery state and execution options.
 
===== Authentication & authorization =====
SEP sesam v. 5.0.0 [[Release_Notes_5.0.0_Jaglion#authentication|''authentication concept'']] has changed. Now only a user with ''Superuser'' privileges can configure authentication and attach permissions (ACLs) to created users. The [[Release_Notes_5.0.0_Jaglion#certificate|''internal users can be authenticated via a signed certificate'']] instead of a user password.  
SEP sesam v. 5.0.0 [[Release_Notes_5.0.0_Jaglion#authentication|''authentication concept'']] has changed. Now only a user with ''Superuser'' privileges can configure authentication and attach permissions (ACLs) to created users. The [[Release_Notes_5.0.0_Jaglion#certificate|''internal users can be authenticated via a signed certificate'']] instead of a user password.  


===== Media Management =====
===== Media management =====


[[5_0_0:Tape_Management#expire|Expiring a tape]] provides a new option to delete all metadata, which erases all tape media metadata and initializes the tape (if the tape is loaded in a drive), removing access to all existing data on the tape.
[[5_0_0:Tape_Management#expire|Expiring a tape]] provides a new option to delete all metadata, which erases all tape media metadata and initializes the tape (if the tape is loaded in a drive), removing access to all existing data on the tape.
Line 46: Line 63:
=== {{anchor|new_systems}}New supported systems ===  
=== {{anchor|new_systems}}New supported systems ===  
SEP sesam Server [[SEP_sesam_Release_Versions|5.0.0 ''Jaglion'']] now also supports the following:
SEP sesam Server [[SEP_sesam_Release_Versions|5.0.0 ''Jaglion'']] now also supports the following:
*xx
*Nutanix AHV
*HCL Domino 12
*Debian 11 (''bullseye'')
*RHV 4.4
*SLES15 Service Pack 3 (SP3) for SEP sesam Server (in previous version, SP3 was only supported for RDS, GUI and Client)
 
'''Improvements''': Cryptographic protocols OpenSSL 1.1.1/TLS2


For a complete list of supported OS and databases, see [[4_4_3_Beefalo:SEP_sesam_OS_and_Database_Support_Matrix|SEP sesam Support Matrix]].
For a complete list of supported OS and databases, see [[5_0_0:SEP_sesam_OS_and_Database_Support_Matrix|SEP sesam Support Matrix]].


=== {{anchor|unsupported_systems}}Discontinued systems ===
=== {{anchor|unsupported_systems}}Discontinued systems ===
Line 54: Line 77:
*Ubuntu 16.04
*Ubuntu 16.04
*SLES11
*SLES11
*Windows Server 2008 R2
}}
}}


For details on discontinued systems, see [[Unsupported OS]]. For a complete list of supported SEP sesam Clients, see [[4_4_3_Beefalo:SEP_sesam_OS_and_Database_Support_Matrix|SEP sesam Support Matrix]].
For details on discontinued systems, see [[Unsupported OS]]. For a complete list of supported SEP sesam Clients, see [[5_0_0:SEP_sesam_OS_and_Database_Support_Matrix|SEP sesam Support Matrix]].


==={{anchor|requirements}}SEP sesam Server requirements===
==={{anchor|requirements}}SEP sesam Server requirements===
;Java xx: No changes since the last (''Beefalo V2'') release. For details see [[Java Compatibility Matrix]], same requirements as for ''Beefalo''.
'''Java xx'''  
 
SEP sesam GUI is based on Java and requires a Java Runtime Environment (JRE). The required [[Special:MyLanguage/Java_Compatibility_Matrix|Java version depends on the SEP sesam version]].
 
{{Note|Java 17 is not supported by SEP sesam. For a list of supported Java versions, see the [[Special:MyLanguage/Java_Compatibility_Matrix|Java Compatibility Matrix]].}}


==={{anchor|installation}}Installation and upgrades===
==={{anchor|installation}}Installation and upgrades===


SEP sesam 5.0.0 ''Jaglion'' was initially released on xx<sup>th</sup> of xx, 2021. Direct '''upgrade''' for versions '''4.4.3.X''' to version '''5.0.0 Jaglion''''' is supported.
SEP sesam ''Jaglion 5.0.0.1 beta'' was released (and available for testing) on 8<sup>th</sup> of November, 2021. Direct '''upgrade''' for versions '''4.4.3.X''' to version Jaglion '''5.0.0.1 beta''''' is supported.


Latest released versions are:
Latest released versions are:
* SEP sesam 5.0.0 [https://download.sep.de/linux/ Linux] [[File:tux.gif]] – released: x of <month>, <year>.
* SEP sesam 5.0.0.1 beta [http://beta.sep.de/linux/ Linux] [[File:tux.gif]] – released: 8<sup>th</sup> of November, 2021.
* SEP sesam 5.0.0 [https://download.sep.de/windows/ Windows] [[File:win7.gif]] – released: x of <month>, <year>.
* SEP sesam 5.0.0.1 beta [http://beta.sep.de/windows/ Windows] [[File:win7.gif]] – released: 8<sup>th</sup> of November, 2021.
<!--
* SEP sesam 4.4.3.79 [https://download.sep.de/linux/ Linux] [[File:tux.gif]] – released: 11<sup>th</sup> of May, 2020.
* SEP sesam 4.4.3.79 [https://download.sep.de/windows/ Windows] [[File:win7.gif]] – released: 11<sup>th</sup> of May, 2020.
-->


;[[File:tux.gif]]  Linux specific:
;[[File:tux.gif]]  Linux specific:
Line 87: Line 111:
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 [[Special:MyLanguage/Updating_SEP_sesam|Updating SEP sesam]] and [[Special:MyLanguage/4_4_3_Beefalo:Remote_Installation_of_Windows_Clients|Remote Installation of Windows Clients]].
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 [[Special:MyLanguage/Updating_SEP_sesam|Updating SEP sesam]] and [[Special:MyLanguage/4_4_3_Beefalo:Remote_Installation_of_Windows_Clients|Remote Installation of Windows Clients]].


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 [[Special:MyLanguage/Automatic Updates|Automatic Updates]] and [[Special:MyLanguage/Automatic_Installation_On_Windows| Automatic Installation on Windows]].
====Post update task====
Version 5.0.0.x uses the enhanced LIS file format, which increases performance at least 10 times. After updating to version 5.0.0.x, a new full [[Special:MyLanguage/4_4_3_Tigon:VMware_Backup|vSphere backup]] should be performed to allow mounting and attaching VMDKs.  


<!--* ''VMware® Virtual Disk Development Kit (VDDK) version 6.5'' for Windows.
====Previous release====
* ''Callback File System® (CBFS®) version 6.1.181'' from EldoS Corporation, used to create virtual file systems and disks for save sets which are stored on SEP sesam local [[Special:MyLanguage/SEP_sesam_Glossary#data_store|data store]] or [[Special:MyLanguage/SEP_sesam_Glossary#Si3_store|Si3 deduplication store]]. {{note|A CBFS driver is needed for the virtual file system layer ([[Special:MyLanguage/SEP_sesam_Glossary#XPRFS|Cross Platform Recovery File System – XPRFS]]). The installation/update of this driver requires a reboot of your newly installed or updated Windows SEP sesam Server unless this driver is already installed with a previous SEP sesam 4.4.3 installation.}}-->
<!--*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 [[Special:MyLanguage/Updating_SEP_sesam|Updating SEP sesam]] and [[Special:MyLanguage/4_4_3_Beefalo:Remote_Installation_of_Windows_Clients|Remote Installation of Windows Clients]].-->
<!--{{note|As of previous release, SEP sesam executables are single signed with SHA256. Because of the buffer limitation of the ''GetCertHash()'' function on Windows Server 2008 SP2, the SEP sesam executables which are now signed with a SHA256 certificate cannot run on Windows Server 2008. To install/upgrade SEP sesam on the respective Windows Server version, you have to install a special Windows update first. For details and update download, see any of the following links:
 
*[https://support.microsoft.com/en-us/help/2763674/you-cannot-run-an-application-that-is-signed-with-a-sha-256-certificat You cannot run an application that is signed with a SHA-256 certificate on a computer that is running Windows Vista SP2 or Windows Server 2008 SP2]
*[https://support.microsoft.com/de-de/help/2763674/you-cannot-run-an-application-that-is-signed-with-a-sha-256-certificat Eine Anwendung, die mit SHA-256-Zertifikat signiert ist, kann nicht auf einem Computer ausgeführt werden, der Windows Vista SP2 oder Windows Server 2008 SP2 ausführt].}}-->
 
'''Previous release'''
* [[Release_Notes_4.4.3_Beefalo_V2|Release notes for SEP sesam 4.4.3 ''Beefalo V2'']]
* [[Release_Notes_4.4.3_Beefalo_V2|Release notes for SEP sesam 4.4.3 ''Beefalo V2'']]


Line 104: Line 121:
{{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.}}
{{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.}}
{{Box Hint Y|5.0.0 ''Jaglion'' known issues|
{{Box Hint Y|5.0.0 ''Jaglion'' known issues|
===Severity: CRITICAL===
<!--===Severity: CRITICAL===
;[[File:Warning sign.png|20px]]Possible data loss due to non-executed updates of the entries in the SEP sesam database at extremely high system load.
:*There may be problems updating entries in the SEP sesam database if the system load is so high that the maximum number of connections is reached (PostgreSQL) or the busy timeout (SQLite) is no longer sufficient. This can result in the backup status being incorrectly set as successful and external applications (e.g. SAP Hana) seeing backups as successful even though they did not complete successfully. In such a case, data loss may occur during a restore.
:::'''Workaround:''' SEP is working on this issue and will provide a fix as soon as possible.
 
;[[File:Warning sign.png|20px]]SEP sesam v. 4.4.3.84 – (''Linux'') Backup to VTL library* completed successfully even though there were media write errors reported and backup could not be completed  
;[[File:Warning sign.png|20px]]SEP sesam v. 4.4.3.84 – (''Linux'') Backup to VTL library* completed successfully even though there were media write errors reported and backup could not be completed  
:*(''Applies only to Linux'') When backing up to VTL, the VTL library cannot continue writing to the underlying block device due to insufficient space and tracks error. [[Special:MyLanguage/SEP_sesam_Glossary#SMS|SMS]] ignores the error and continues writing the data to VTL without sufficient space. The Backup log shows ''"backup completed successfully"'' although it actually failed and no data was written to backup media. <br />(*''This behavior is seen with the QUADStor VTL only.'')
:*(''Applies only to Linux'') When backing up to VTL, the VTL library cannot continue writing to the underlying block device due to insufficient space and tracks error. [[Special:MyLanguage/SEP_sesam_Glossary#SMS|SMS]] ignores the error and continues writing the data to VTL without sufficient space. The Backup log shows ''"backup completed successfully"'' although it actually failed and no data was written to backup media. <br />(*''This behavior is seen with the QUADStor VTL only.'')
:::'''Workaround:''' Download the hotfix from [http://download.sep.de/servicepacks/4.4.3/4.4.3.84/hotfix/linux/ SEP Download Center] to your Linux server or RDS and install it by executing the following commands as ''root'' in a terminal session. '''Attention:''' This operation will stop all running backups.
:::'''Workaround:''' -->
#>sm_main stop node
#>cd /opt/sesam
#>tar xvzf <hotfix file>
#>sm_main start node
-----
-----
===Severity: SECURITY===
===Severity: SECURITY===
;SEP sesam v. 5.0.0 – (Windows) STPD automatically disables the HTTPS port on Windows  
;SEP sesam v. 5.0.0 – (Windows) STPD automatically disables the HTTPS port on Windows  
:*(Applies only to Windows) The Sesam Transfer Protocol Server (STPD) automatically disables the HTTPS port if CPU instructions are missing due to unsupported AVX. Consequently, the SSL key and certificate cannot be created.
:*(Applies only to Windows) The Sesam Transfer Protocol Server (STPD) automatically disables the HTTPS port if CPU instructions are missing due to unsupported AVX. Consequently, the SSL key and certificate cannot be created.
:::'''Workaround :''' Make sure that you use CPUs with supported AVX versions (AVX, AVX2 or AVX-512). They are listed in the article [https://en.wikipedia.org/wiki/Advanced_Vector_Extensions Advanced Vector Extensions].
:::'''Workaround :''' Make sure that you use CPUs with supported AVX versions (AVX, AVX2 or AVX-512) as well as FMA3 (Fused Multiply-Add 3-operand Form) or FMA4 (Fused Multiply-Add 4-operand Form). For the list of supported AVX versions, see [https://en.wikipedia.org/wiki/Advanced_Vector_Extensions Advanced Vector Extensions].
-----
-----
===Severity: SEVERE===
===Severity: MAJOR===
;SEP sesam v. 4.4.3.86 - VM backup may fail if a backup source path is too long
;SEP sesam v. 5.0.0.1 ''beta'' – Single file restore (SFR) of VMs fails with warning
:*If a source path of a VM backup is too long, the backup may fail with the following error:<br />''Exit code from sbc_com_interface: [1] - warning<br />Error: VM Exception: [Command [sbc_com_interface, -b, openjob...fails].''<br />Note that this only occurs in rare cases when a large number of VMKDs are attached to VM. If no such error is displayed, the VM backup is successful.
:* VM SFR fails with the following warning: '''Warning: Saveset not created' because 'tmp/mnt' directory is excluded.''  
:::'''Resolution:''' Already fixed, contact [https://www.sep.de/download-support/support/ support] for help.
;SEP sesam v. 4.4.3.86 – Mount of RHV, Citrix XEN, KVM or OpenNebula backup fails on Windows Host
:* Mounting the virtual disks of RHV, Citrix XEN, KVM or OpenNebula backup fails on Windows host with an error: ''ImportError: sh 1.12.14 is currently only supported on Linux''.
:::'''Workaround:''' SEP is working on this issue and will provide a fix as soon as possible.
:::'''Workaround:''' SEP is working on this issue and will provide a fix as soon as possible.
;SEP sesam v. 4.4.3.86 – Core dump of ''sm_stpd'' during closejob operation via FTP on SLES12 PPC
;SEP sesam v. 5.0.0.1 ''beta'' – STPD shutdown may hang
:*  Core dump occurs during closejob operation over FTP on SLES12 PPC due to string variable being too short.
:*  The Sesam Transfer Protocol Server (STPD) occasionally hangs during service shutdown due to incorrect signal function.
:::'''Workaround:''' Use the network protocols http:// or https://;  ensure that the interface is correctly added to the client properties (see [[Special:MyLanguage/Configuring_Clients#procedure|Configuring Clients: Procedure]]).
:::'''Resolution:''' Fixed with version [http://download.sep.de/ 5.0.0.x].
:::'''Resolution:''' Already fixed, contact support for help.  
-----
-----
===Severity: MINOR===
===Severity: MINOR===
;SEP sesam v. 4.4.3.86 – Exchange incremental backup fails sporadically with error
;SEP sesam v. 4.4.3.86–5.0.0.1 ''beta'' ''Initial Seeding'' functionality temporarily removed
:* When trying to perform an Exchange INCR backup, it may fail with an error: <nowiki>''STATUS=WARNING MSG=global name 'self' is not defined''</nowiki>.
:*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.1.  
:::'''Workaround:''' SEP is working on this issue and will provide a fix as soon as possible.
;SEP sesam 5.0.0.1 ''beta'' – Backing up a VMware .vmx file may fail due to a line that is too long
;SEP sesam v. 4.4.3.86 – While configuring Si3 deduplication store, ''sm_config_drives'' aborts on Windows Server 2016/2019
:*Backing up VMware virtual machine configuration (.vmx) file may result in a ''Segmentation fault (core dumped)'' error if a line is too long. (The long line comes from the ''appInfo'' feature of the VMware tools.) Consequently, the backup of the VMware configuration fails.
:*(''Windows only'') An Si3 deduplication store is created and configured, then another data store is created; ''sm_config_drives'' starts again and terminates.  
:::'''Resolution:''' Fixed with version [http://download.sep.de/ 5.0.0.x].
:::'''Workaround:''' SEP is working on this issue and will provide a fix as soon as possible.
;SEP sesam 5.0.0.1 ''beta'' – Unable to browse backup source for Oracle VM
;SEP sesam v. 4.4.3.86 – Seeding Si3 deduplication store fails with error
:*It is not possible to browse Oracle Linux Virtualization Manager (OLVM) client to specify the source and select the object(s) to be backed up.
:*Using the ''Initial Seed'' option to set up a new Si3 deduplication store for replication results in a seemingly successful setup, but no data is replicated and the ''sm_dedup_server.log'' shows a Java exception.  
:::'''Resolution:''' Fixed with version [http://download.sep.de/ 5.0.0.x].
:::'''Workaround:''' SEP is working on this issue and will provide a fix as soon as possible.
;SEP sesam 5.0.0.1 ''beta'' – Unable to perform Hyper-V single file restore from RDS due to a failed mount
;SEP sesam v. 4.4.3.86 – After database import via GUI, SEP sesam processes ''rmi'' and ''sds'' are offline
:*When performing Hyper-V single file restore from an RDS, SEP sesam fails to mount Hyper-V VM VHD on Windows RDS due to the wrong path to .map file.
:*When ''sm_db_update'' is finished, SEP sesam is restarted, but all running processes are stopped and fail to get restarted.
:::'''Resolution:''' Fixed with version [http://download.sep.de/ 5.0.0.x].
:::'''Workaround:''' Execute the following commands after db import:
;SEP sesam 5.0.0.1 ''beta'' No Exchange Recovery Pro shortcut (RPEX) created when mounting the saveset
sm_main start rmi
:*When performing Exchange single item recovery, the saveset is mounted successfully, but no RPEX shortcut is created on the Windows server.
sm_main start sds
:::'''Resolution:''' Fixed with version [http://download.sep.de/ 5.0.0.x].
;SEP sesam v. 4.4.3.74 Cancelling a Citrix XEN backup task does not abort the backup execution:
;SEP sesam 5.0.0.1 ''beta'' – Restoring vSphere COPY backups with ''single saveset'' option does not work
:*Aborting a Citrix Xen backup task does not prevent the backup job from running as SEP sesam does not pass a cancel request to the running ''sbc_proxy'' and ''sbc'' process. Therefore the backup process will be running without interruption. Be aware that killing the ''sbc_proxy'' or ''sbc'' process manually will keep the snapshots; in this case, snapshots must be released manually.
:*When restoring VMware COPY backups with selected GUI option ''When run with backup level 'COPY', write all data into single saveset'', the restore fails.
:::'''Workaround:''' Only if you have aborted Citrix XEN backups manually by killing the ''sbc_proxy'' or ''sbc'' process, don't forget to release these snapshots as they are not managed by SEP sesam automatically. SEP is working on this issue and will provide a fix as soon as possible.
:::'''Resolution:''' Fixed with version [http://download.sep.de/ 5.0.0.x].
-----
-----
====''Minor GUI issues''====
<!--====''Minor GUI issues''====
We are experiencing some minor GUI issues that do not affect SEP sesam's performance and functionality. SEP is working on these issues and will provide a fix as soon as possible.
We are experiencing some minor GUI issues that do not affect SEP sesam's performance and functionality. SEP is working on these issues and will provide a fix as soon as possible.  
;SEP sesam v. 4.4.3.86 – When a loader is reconfigured with a new drive, the drive is not shown
:*When a new loader is created and an already configured drive is moved to the new loader, clicking the ''Apply'' button fails to show the drive for the newly created loader.
:::'''Workaround:''' Close the ''Loaders'' view and then open it to refresh the displayed loader configuration.
;SEP sesam v. 4.4.3.86 – ''Send'' button in migration task properties does not work
:*When using the ''Send'' button for the ''Main log'' in the properties of the migration task, sending does not work.  
;SEP sesam v. 4.4.3.86 – Starting disaster recovery from the toolbar fails
;SEP sesam v. 4.4.3.86 – Starting disaster recovery from the toolbar fails
:*When attempting to start disaster recovery from the toolbar, an error message is displayed and the operation fails. (This button is only displayed if a Defaults ''disaster_recovery'' entry is set with a value of 1.)
:*When attempting to start disaster recovery from the toolbar, an error message is displayed and the operation fails. (This button is only displayed if a Defaults ''disaster_recovery'' entry is set with a value of 1.)
;SEP sesam v. 4.4.3.86 – Filtering may not work correctly in some views
-->
:*When using ''Main Selection'' -> ''Scheduling'' -> ''Events as List'' -> ''Filter'' to filter the results for the backup, the results list is empty.
:*When using ''Main Selection'' -> ''Tasks'' -> ''As List'' -> ''Filter'' to filter tasks by their status, selecting ''Execution off'' will only display tasks where both client and task are disabled.
;SEP sesam v. 4.4.3.86 – Copying a backup task fails to copy assigned schedules
:*When copying a backup task, all properties except assigned schedules are copied to the newly created task.
}}
}}
== {{anchor|fixes}}Important fixes ==
{{Box Hint|Fixed with [https://download.sep.de/ SEP sesam Server 5.0.0 ''Jaglion'']|
{{Box Hint|Fixed with [https://download.sep.de/ SEP sesam Server 5.0.0 ''Jaglion'']|
;SEP sesam v. 4.4.3.75 – Tape restore performance is slower than backup performance
:* When restoring from tape the performance is 2-3 times slower than the performance of the backup.
:::'''Resolution:''' Fixed; fill the second buffer while processing the first buffer, EOF handling adapted.
;SEP sesam v. ≥ 4.4.3 – Si3S does not work in case of changed STPD port on the Client  
;SEP sesam v. ≥ 4.4.3 – Si3S does not work in case of changed STPD port on the Client  
:*[[Special:MyLanguage/SEP_sesam_Glossary#Si3S|SEP Si3 source-side deduplication]] (Si3S) backup of a client to a SEP Si3 deduplication store not work, if the STPD service TCP port on the client side (in <tt>sm.ini</tt> and/or <tt>stpd.ini</tt>) is changed from the default port.
:*[[Special:MyLanguage/SEP_sesam_Glossary#Si3S|SEP Si3 source-side deduplication]] (Si3S) backup of a client to a SEP Si3 deduplication store not work, if the STPD service TCP port on the client side (in <tt>sm.ini</tt> and/or <tt>stpd.ini</tt>) is changed from the default port.
Line 177: Line 178:


==={{anchor|Nutanix}}Nutanix AHV===
==={{anchor|Nutanix}}Nutanix AHV===
With ''Jaglion'', SEP sesam provides efficient data protection for Nutanix AHV virtual machines (VMs). The Nutanix AHV module is supported only on SEP sesam Linux Server. You can easily back up and restore Nutanix AHV VMs, as described in [[Special:MyLanguage/5_0_0:Nutanix_AHV_Backup|Nutanix AHV Backup]] and [[Special:MyLanguage/5_0_0:Nutanix_AHV_Restore|Nutanix AHV Restore]].
With ''Jaglion'', SEP sesam provides efficient data protection for Nutanix AHV virtual machines (VMs). The Nutanix AHV module is supported on SEP sesam Linux Server and on SEP sesam Windows Server, using a Linux Client as a data mover. You can easily back up and restore Nutanix AHV VMs, as described in [[Special:MyLanguage/5_0_0:Nutanix_AHV_Backup|Nutanix AHV Backup]] and [[Special:MyLanguage/5_0_0:Nutanix_AHV_Restore|Nutanix AHV Restore]].


==={{anchor|authentication}}Authentication and authorization===
==={{anchor|authentication}}Authentication and authorization===
Line 188: Line 189:


To simplify backing up multiple VMs, you can automate the process by automatically generating tasks for VMs that are connected to the same host; you can also automatically create clients for VMs that can be assigned the generated tasks and ACLs. It is recommended to use these features when a new hypervisor is added and many new VMs need to be backed up. For details, see [[Special:MyLanguage/5_0_0:Automating_Backup_Process|Automating Backup Process]].  
To simplify backing up multiple VMs, you can automate the process by automatically generating tasks for VMs that are connected to the same host; you can also automatically create clients for VMs that can be assigned the generated tasks and ACLs. It is recommended to use these features when a new hypervisor is added and many new VMs need to be backed up. For details, see [[Special:MyLanguage/5_0_0:Automating_Backup_Process|Automating Backup Process]].  
==={{anchor|Cloud_Volume}}HPE Cloud Volumes storage===
In addition to HPE StoreOnce Catalyst stores and HPE Cloud Bank storage, you can now use ''HPE Cloud Volumes'' as backup storage. The HPE Cloud Volumes solution provides efficient direct backup, replication, and restore. Although you can use HPE Cloud Volume store for direct backups, it is recommended that you use it more as a secondary target repository for replication. For details, see [[Special:MyLanguage/5_0_0:HPE_Cloud_Volumes_Backup|HPE Cloud Volumes Backup]].
==={{anchor|RCT}}Resilient Change Tracking for Hyper-V===
For Microsoft Windows Server 2016 or later, the Resilient Change Tracking feature (RCT) is supported to back up Hyper-V virtual machines. Similar to CBT for VMware and Citrix, incremental backup technology RCT for Hyper-V detects block-level changes and backs up only the data that has changed since the last incremental backup. This allows you to back up VMs faster while saving storage space. See [[Special:MyLanguage/4_4_3_Grolar:Hyper-V_Backup#RCT|RCT for Hyper-V]].


==={{anchor|OLVM}}Oracle-VM task type===
==={{anchor|OLVM}}Oracle-VM task type===
The new ''Oracle-VM'' task type is available to perform agentless snapshot-based backups of all OLVM virtual machines, regardless of their workload or operating system. See [[5_0_0:OLVM_Backup|OLVM Backup]].
The new ''Oracle-VM'' task type is available to perform agentless snapshot-based backups of all OLVM virtual machines, regardless of their workload or operating system. See [[5_0_0:OLVM_Backup|OLVM Backup]].


==={{anchor|web_restore}}Web single file restore for VMs===
==={{anchor|restore_assistant}}New and improved with web Restore Assistant===
In the web interface Restore assistant, you can now restore single files of ''VMware'', ''Hyper-V'', ''RHV/OLVM'', ''Citrix Hypervisor'', ''KVM/QEMU'', and ''OpenNebula'' virtual machines (VMs) online, if you have been granted the appropriate permissions. Single file restore for ''Proxmox VE'' and ''Nutanix AHV'' VM is currently not supported. For details, see [[Special:MyLanguage/5_0_0:Web_Single_File_Restore_for_Virtual_Machines|Web Single File Restore for Virtual Machines]].
 
The web ''Restore Assistant'' supports new task types and offers new features and an intuitive user experience that makes restoring data online quick and easy. For details, see [[Special:MyLanguage/5_0_0:Restore_Assistant|Restore Assistant]].
 
===={{anchor|web_restore}}Web single file restore (SFR) for VMs====
In the web interface ''Restore assistant'', you can now restore individual files from ''VMware'', ''Hyper-V'', ''RHV/OLVM'', ''Citrix Hypervisor'', ''KVM/QEMU'', ''OpenNebula'' and ''Nutanix AHV'' virtual machines online, if you have been granted the appropriate permissions. SFR for ''Proxmox VE'' VM is currently not supported. For details, see [[Special:MyLanguage/5_0_0:Web_Single_File_Restore_for_Virtual_Machines|Web Single File Restore for Virtual Machines]].
 
===={{anchor|Exchange_restore}}Web Exchange restore====
Now it is possible to restore a single Exchange mailbox database using ''SEP sesam Exchange Recovery Pro'' via the web interface ''Restore Assistant''. Exchange Recovery Pro is only supported on Windows systems and must be installed on the system serving as SEP sesam Server or SEP sesam RDS. See [[5_0_0:Web_Exchange_Restore|Web Exchange Restore]].


==={{anchor|Exchange_restore}}Web Exchange restore===
===={{anchor|VMware_sandbox_rst}}Web VMware sandbox restore====  
Now it is possible to restore a single Exchange mailbox database using SEP sesam Exchange Recovery Pro via the web interface Restore Assistant if you have been granted the appropriate permissions. Exchange Recovery Pro is only supported on Windows systems and must be installed on the system serving as SEP sesam Server or SEP sesam RDS. See [[5_0_0:Web_Exchange_Restore|Web Exchange Restore]].
Enhanced VMware sandbox restore via the web Restore Assistant can be performed in advanced restore mode. It provides improved functionality and usability of the recovery options, i.e. the use of run and execution commands of the VMware guest tools. See [[5_0_0:VMware_Sandbox_Restore|VMware Sandbox Restore]].


==={{anchor|Citrix}}Citrix VHD exclude===
===={{anchor|MS_SQL}}Web MS SQL restore====
When backing up Citrix Hypervisor VMs, you can exclude individual virtual disk (VHD) from ''Full''/''Diff''/''Incr'' backup in the SEP sesam GUI to avoid storage occupancy. For details, see [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Backup|Citrix XenServer Backup]].
Online restore of MS SQL Server databases is supported with specific recovery state options (leave the database ready for use by rolling back uncommitted transactions, etc.) and additional execution options (overwrite existing items with newer/older items from backup and skip ACL settings during restore). See [[5_0_0:Web_MS_SQL_Restore|Web MS SQL Restore]].


==={{anchor|Web_UI}}Web UI enhancements===  
==={{anchor|Web_UI}}Web UI enhancements===  
SEP sesam Web UI now provides a more detailed overview of jobs and tasks, improved monitoring of the SEP sesam environment, and the possibility of performing different operations, e.g., running or locking the backups, restarting failed jobs, etc. For details, see [[Special:MyLanguage/5_0_0:SEP_sesam_Web_UI|SEP sesam Web UI]]
SEP sesam Web UI now provides a more detailed overview of jobs and tasks, improved monitoring of the SEP sesam environment, and the possibility of performing different operations, e.g., running or locking the backups, restarting failed jobs, etc. For details, see [[Special:MyLanguage/5_0_0:SEP_sesam_Web_UI|SEP sesam Web UI]].


==={{anchor|GUI_enhancements}}GUI enhancements===  
==={{anchor|GUI_enhancements}}GUI enhancements===  
Line 212: Line 228:


*In previous SEP sesam versions, the backup ''locked'' state (savesets of the backup cannot be deleted) is applied to the selected backup only, so you have to lock all backups of a backup chain manually. As of ''Jaglion'', the ''locked'' state is automatically applied to all backups in the backup chain. See [[Special:MyLanguage/4_4_3_Beefalo:Backups_by_State|Backups by State]].
*In previous SEP sesam versions, the backup ''locked'' state (savesets of the backup cannot be deleted) is applied to the selected backup only, so you have to lock all backups of a backup chain manually. As of ''Jaglion'', the ''locked'' state is automatically applied to all backups in the backup chain. See [[Special:MyLanguage/4_4_3_Beefalo:Backups_by_State|Backups by State]].
*{{anchor|Citrix}}When backing up Citrix Hypervisor VMs, you can exclude individual virtual disk (VHD) from ''Full''/''Diff''/''Incr'' backup in the SEP sesam GUI to avoid storage occupancy. For details, see [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Backup|Citrix XenServer Backup]].
*[[5_0_0:Tape_Management#expire|Expiring a tape]] provides a new option to delete all metadata, which erases all tape media metadata and initializes the tape (if the tape is loaded in a drive), removing access to all existing data on the tape.


== {{anchor|end}}End of maintenance and support ==
== {{anchor|end}}End of maintenance and support ==

Revision as of 09:56, 7 December 2021

Draft.png WORK IN PROGRESS
This article is in the initial stage and may be updated, replaced or deleted at any time. It is inappropriate to use this document as reference material as it is a work in progress and should be treated as such.

Template:Copyright SEP AG en

Information sign.png Note
SEP AG is pleased to announce that the upcoming version of SEP sesam, v. 5.0.0.1 Jaglion, is currently in the beta 1 release phase. This document describes known issues for beta 1 release as well as the most important new features and additional information for the upcoming official release.
  • Note that SEP sesam provides SEP sesam 5.0.0.1 Jaglion beta 1 as a test program on an "as is" basis and without warranty. Beta version may contain errors and bugs and may cause problems that could lead to system failures and data loss.
  • If you are interested in testing the beta version, please register as a beta tester by email to beta@sep.de. Make sure that you fully understand and agree to the terms and conditions, described in Hints for beta testing, before you start using SEP sesam beta software.

What's new in SEP sesam 5.0.0 Jaglion

New SEP sesam release 5.0.0 Jaglion introduces a more powerful and intuitive Web UI, handy new GUI functions, and more consistent and stable internal APIs.

Features at a glance

Improvements and bug fixes

This release contains a number of improvements and important fixes in various areas and resolves the issue with slow tape restore performance.

Extended SEP sesam REST API V2

The SEP sesam REST API V2 has been extended to support a wide variety of use cases. A large number of new endpoints have been added. For details, see SEP sesam REST API V2 Jaglion.

Enhanced Web UI

The more advanced and intuitive Web UI offers the following in addition to monitoring SEP sesam operations: Start backups immediately, restart failed jobs, lock backups, review alerts, set UI mode, and view job and data store details.

Backup & restore
  • Now also supported: Nutanix Acropolis Hypervisor (AHV) backup and restore. The Nutanix AHV module is supported on SEP sesam Linux Server and on SEP sesam Windows Server, using a Linux Client as a data mover.
  • To simplify backing up multiple VMs, you can automate the process by automatically generating tasks for VMs that are connected to the same host; in addition, you can also automatically create clients for VMs to which the generated tasks and ACLs can be assigned.
  • The new Oracle-VM task type is available to perform agentless snapshot-based backups of all OLVM virtual machines.
  • Si3 deduplication store has been improved; the new Si3 NG deduplication store enables significantly higher deduplication performance.
  • VFS (Sesam virtual file system) performance improvements enable 100x faster access to vSphere VMs booted directly from SEP sesam data store.
  • When browsing a VMware vSphere server for backup sources, VMs are displayed in the vCenter tree along with the host and clusters. The client browser for VMware now displays a description of the configured backup tasks and details of the VM-related metadata that can be copied.
  • For direct HPE backups and especially replications to the cloud, the new data store type HPE Cloud Volumes is available.
  • For Microsoft Windows Server 2016 or later, the Resilient Change Tracking (RCT) is supported to back up Hyper-V virtual machines.
  • Since Jaglion, the locked state is automatically applied to all backups in the chain of the selected backup.
  • When backing up Citrix Hypervisor VMs, it is possible to exclude individual virtual disk (VHD) from the backup.
Web Restore Assistant
Authentication & authorization

SEP sesam v. 5.0.0 authentication concept has changed. Now only a user with Superuser privileges can configure authentication and attach permissions (ACLs) to created users. The internal users can be authenticated via a signed certificate instead of a user password.

Media management

Expiring a tape provides a new option to delete all metadata, which erases all tape media metadata and initializes the tape (if the tape is loaded in a drive), removing access to all existing data on the tape.

New supported systems

SEP sesam Server 5.0.0 Jaglion now also supports the following:

  • Nutanix AHV
  • HCL Domino 12
  • Debian 11 (bullseye)
  • RHV 4.4
  • SLES15 Service Pack 3 (SP3) for SEP sesam Server (in previous version, SP3 was only supported for RDS, GUI and Client)

Improvements: Cryptographic protocols OpenSSL 1.1.1/TLS2

For a complete list of supported OS and databases, see SEP sesam Support Matrix.

Discontinued systems

Information sign.png Note
In SEP sesam Jaglion, SEP announced that it would no longer support:
  • Ubuntu 16.04
  • SLES11
  • Windows Server 2008 R2

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

SEP sesam Server requirements

Java xx

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

Information sign.png Note
Java 17 is not supported by SEP sesam. For a list of supported Java versions, see the Java Compatibility Matrix.

Installation and upgrades

SEP sesam Jaglion 5.0.0.1 beta was released (and available for testing) on 8th of November, 2021. Direct upgrade for versions 4.4.3.X to version Jaglion 5.0.0.1 beta is supported.

Latest released versions are:

  • SEP sesam 5.0.0.1 beta Linux Tux.gif – released: 8th of November, 2021.
  • SEP sesam 5.0.0.1 beta Windows Win7.gif – released: 8th of November, 2021.
Tux.gif 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 
Win7.gif Windows specific

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.x uses the enhanced LIS file format, which increases performance at least 10 times. After updating to version 5.0.0.x, a new full vSphere backup should be performed to allow mounting and attaching VMDKs.

Previous release

Known issues and limitations

Information sign.png 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 Jaglion known issues:

Severity: SECURITY

SEP sesam v. 5.0.0 – (Windows) STPD automatically disables the HTTPS port on Windows
  • (Applies only to Windows) The Sesam Transfer Protocol Server (STPD) automatically disables the HTTPS port if CPU instructions are missing due to unsupported AVX. Consequently, the SSL key and certificate cannot be created.
Workaround : Make sure that you use CPUs with supported AVX versions (AVX, AVX2 or AVX-512) as well as FMA3 (Fused Multiply-Add 3-operand Form) or FMA4 (Fused Multiply-Add 4-operand Form). For the list of supported AVX versions, see Advanced Vector Extensions.

Severity: MAJOR

SEP sesam v. 5.0.0.1 beta – Single file restore (SFR) of VMs fails with warning
  • VM SFR fails with the following warning: 'Warning: Saveset not created' because 'tmp/mnt' directory is excluded.
Workaround: SEP is working on this issue and will provide a fix as soon as possible.
SEP sesam v. 5.0.0.1 beta – STPD shutdown may hang
  • The Sesam Transfer Protocol Server (STPD) occasionally hangs during service shutdown due to incorrect signal function.
Resolution: Fixed with version 5.0.0.x.

Severity: MINOR

SEP sesam v. 4.4.3.86–5.0.0.1 betaInitial 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.1.
SEP sesam 5.0.0.1 beta – Backing up a VMware .vmx file may fail due to a line that is too long
  • Backing up VMware virtual machine configuration (.vmx) file may result in a Segmentation fault (core dumped) error if a line is too long. (The long line comes from the appInfo feature of the VMware tools.) Consequently, the backup of the VMware configuration fails.
Resolution: Fixed with version 5.0.0.x.
SEP sesam 5.0.0.1 beta – Unable to browse backup source for Oracle VM
  • It is not possible to browse Oracle Linux Virtualization Manager (OLVM) client to specify the source and select the object(s) to be backed up.
Resolution: Fixed with version 5.0.0.x.
SEP sesam 5.0.0.1 beta – Unable to perform Hyper-V single file restore from RDS due to a failed mount
  • When performing Hyper-V single file restore from an RDS, SEP sesam fails to mount Hyper-V VM VHD on Windows RDS due to the wrong path to .map file.
Resolution: Fixed with version 5.0.0.x.
SEP sesam 5.0.0.1 beta – No Exchange Recovery Pro shortcut (RPEX) created when mounting the saveset
  • When performing Exchange single item recovery, the saveset is mounted successfully, but no RPEX shortcut is created on the Windows server.
Resolution: Fixed with version 5.0.0.x.
SEP sesam 5.0.0.1 beta – Restoring vSphere COPY backups with single saveset option does not work
  • When restoring VMware COPY backups with selected GUI option When run with backup level 'COPY', write all data into single saveset, the restore fails.
Resolution: Fixed with version 5.0.0.x.

Important fixes

Fixed with SEP sesam Server 5.0.0 Jaglion:
SEP sesam v. 4.4.3.75 – Tape restore performance is slower than backup performance
  • When restoring from tape the performance is 2-3 times slower than the performance of the backup.
Resolution: Fixed; fill the second buffer while processing the first buffer, EOF handling adapted.
SEP sesam v. ≥ 4.4.3 – Si3S does not work in case of changed STPD port on the Client
  • SEP Si3 source-side deduplication (Si3S) backup of a client to a SEP Si3 deduplication store not work, if the STPD service TCP port on the client side (in sm.ini and/or stpd.ini) is changed from the default port.
Resolution: You can now set the STPD service TCP port on the client (client properties -> Options tab -> Listen port) to the new TCP port.

Enhancements and changes

Nutanix AHV

With Jaglion, SEP sesam provides efficient data protection for Nutanix AHV virtual machines (VMs). The Nutanix AHV module is supported on SEP sesam Linux Server and on SEP sesam Windows Server, using a Linux Client as a data mover. You can easily back up and restore Nutanix AHV VMs, as described in Nutanix AHV Backup and Nutanix AHV Restore.

Authentication and authorization

The authentication and authorization concept is enhanced with two new user types - superuser, which replaces the previous admin role, and backup user. Now only a user with Superuser privileges can configure authentication and attach permissions (ACLs) to created users. For details, see About Authentication and Authorization and Using Access Control lists.

Certificate-based authentication

Now it is possible to authenticate users via a signed certificate instead of a user password if a database-based authentication is enabled. Note that the users from external authentication sources (LDAP/AD) cannot be authenticated using a certificate (only by using a password). For details, see Configuring Certificate-Based Authentication.

Automating backup process

To simplify backing up multiple VMs, you can automate the process by automatically generating tasks for VMs that are connected to the same host; you can also automatically create clients for VMs that can be assigned the generated tasks and ACLs. It is recommended to use these features when a new hypervisor is added and many new VMs need to be backed up. For details, see Automating Backup Process.

HPE Cloud Volumes storage

In addition to HPE StoreOnce Catalyst stores and HPE Cloud Bank storage, you can now use HPE Cloud Volumes as backup storage. The HPE Cloud Volumes solution provides efficient direct backup, replication, and restore. Although you can use HPE Cloud Volume store for direct backups, it is recommended that you use it more as a secondary target repository for replication. For details, see HPE Cloud Volumes Backup.

Resilient Change Tracking for Hyper-V

For Microsoft Windows Server 2016 or later, the Resilient Change Tracking feature (RCT) is supported to back up Hyper-V virtual machines. Similar to CBT for VMware and Citrix, incremental backup technology RCT for Hyper-V detects block-level changes and backs up only the data that has changed since the last incremental backup. This allows you to back up VMs faster while saving storage space. See RCT for Hyper-V.

Oracle-VM task type

The new Oracle-VM task type is available to perform agentless snapshot-based backups of all OLVM virtual machines, regardless of their workload or operating system. See OLVM Backup.

New and improved with web Restore Assistant

The web Restore Assistant supports new task types and offers new features and an intuitive user experience that makes restoring data online quick and easy. For details, see Restore Assistant.

Web single file restore (SFR) for VMs

In the web interface Restore assistant, you can now restore individual files from VMware, Hyper-V, RHV/OLVM, Citrix Hypervisor, KVM/QEMU, OpenNebula and Nutanix AHV virtual machines online, if you have been granted the appropriate permissions. SFR for Proxmox VE VM is currently not supported. For details, see Web Single File Restore for Virtual Machines.

Web Exchange restore

Now it is possible to restore a single Exchange mailbox database using SEP sesam Exchange Recovery Pro via the web interface Restore Assistant. Exchange Recovery Pro is only supported on Windows systems and must be installed on the system serving as SEP sesam Server or SEP sesam RDS. See Web Exchange Restore.

Web VMware sandbox restore

Enhanced VMware sandbox restore via the web Restore Assistant can be performed in advanced restore mode. It provides improved functionality and usability of the recovery options, i.e. the use of run and execution commands of the VMware guest tools. See VMware Sandbox Restore.

Web MS SQL restore

Online restore of MS SQL Server databases is supported with specific recovery state options (leave the database ready for use by rolling back uncommitted transactions, etc.) and additional execution options (overwrite existing items with newer/older items from backup and skip ACL settings during restore). See Web MS SQL Restore.

Web UI enhancements

SEP sesam Web UI now provides a more detailed overview of jobs and tasks, improved monitoring of the SEP sesam environment, and the possibility of performing different operations, e.g., running or locking the backups, restarting failed jobs, etc. For details, see SEP sesam Web UI.

GUI enhancements

  • Under the Configuration -> Defaults -> General tab, two additional options are available. Now you can use Sort case insensitive option to ensure that upper- and lowercase letters are treated the same when sorting results. Additionally, new filter option allows you to set a delay for reloading data when changing the filter(s). For details, see Configuration: Defaults.
  • When creating a backup task on Linux, you can now set that deleted or modified files are not reported as errors. For details, see Creating a Backup Task.
  • Now you can start the replication immediately under the Activities -> Immediate Start -> Replication, see Activities.

Technical improvements

  • In previous SEP sesam versions, the backup locked state (savesets of the backup cannot be deleted) is applied to the selected backup only, so you have to lock all backups of a backup chain manually. As of Jaglion, the locked state is automatically applied to all backups in the backup chain. See Backups by State.
  • When backing up Citrix Hypervisor VMs, you can exclude individual virtual disk (VHD) from Full/Diff/Incr backup in the SEP sesam GUI to avoid storage occupancy. For details, see Citrix XenServer Backup.
  • Expiring a tape provides a new option to delete all metadata, which erases all tape media metadata and initializes the tape (if the tape is loaded in a drive), removing access to all existing data on the tape.

End of maintenance and support

Upcoming end of support

SEP sesam 4.4.3 Grolar -> October 2021

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
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


Major fixes and changes

See also

SEP sesam Release Versions