Release Notes 5.1.0 Apollon: Difference between revisions

From SEPsesam
(First version)
Line 1: Line 1:
__NOTOC__{{Copyright SEP AG|en}}
__NOTOC__
{{draft}}


==SEP sesam 5.1.0 ''Apollon''==
<div class="boilerplate metadata" id="Additional resources" style="background-color: #f0f0f0; color:#636f73; border: 1px ridge #cdd3db; margin: 0.5em; padding: 0.5em; margin: 0 auto; width: 80%; font-size: 130%;"><center><b> SEP sesam version ''5.1.0 Apollon'': a feature, improvement, and bug fix release</b></center>
<span style="color:gray; font-size: 90%">Updated: September 6, 2022</span>
 
*<span style="color:gray; font-size: 90%">SEP sesam version ''5.1.0 Apollon'' is a feature, improvement, and bug fix release. Download ''5.1.0 Apollon'' from {{download}}.</span>
 
{{note|
For the list of known issues and limitations see section [[Release_Notes_5.1.0_Apollon#issues|Issues in ''Apollon 5.1.0'' release]] }}
 
This article contains important information about the ''Apollon'' release. It describes new features and new supported systems in ''Apollon'', installation, upgrades, and requirements, and includes a list of fixes included in the service packs.
 
<div class="boilerplate metadata" id="Additional resources" style="background-color: #f0f0f0; color:#636f73; border: 1px ridge #cdd3db; margin: 0.5em; padding: 0.5em; float: right; width: 35%; "><center><b>Now available: [http://download.sep.de/ ''5.1.0 Apollon'']</b></center>


{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"
| rowspan="2" style="padding:0px 10px 0px;" | [[File:icon_archived_docs.png|45px|link=]]
| rowspan="2" style="padding:0px 10px 0px;" | [[File:icon_archived_docs.png|45px|link=]]
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" |Installation is highly recommended as it includes various performance, stability, and other key customer fixes. For details, see [[Change report Apollon]].  
| style="padding:0px 40px 0px 10px; color: grey; font-size: 70%; text-align:left;" |January 23, 2023 <br />Installation is highly recommended as it includes various performance, stability, and other key customer fixes. For details, see [[Change report Apollon]].  
|}</div>
|}</div>
{|style="margin: auto; margin-top:50px; margin-bottom:5px; width:90%; border:0px solid grey;"
|[[File:tux.gif]] '''Download for Linux: [https://download.sep.de/ SEP sesam 5.1.0 Linux]'''
|[[File:win7.gif]] '''Download for Windows: [https://download.sep.de/ SEP sesam 5.1.0 Windows]'''
|-
|See [[Special:MyLanguage/SEP_sesam_Quick_Install_Guide#linux|Installation on Linux]]
|See [[Special:MyLanguage/SEP_sesam_Quick_Install_Guide#windows|Installation on Windows]]
|}
{{note|
You always have to update the SEP sesam Server first before updating the RDS and client components. For more information on the SEP sesam software updates, see [[Special:MyLanguage/Updating_SEP_sesam|Updating SEP sesam]].}}


<div style="text-align:left; padding:1em 1em 1em;">
<div style="text-align:left; padding:1em 1em 1em;">
<div style="display:inline-block; vertical-align:top; margin:1em; width:350px;">  
<div style="display:inline-block; vertical-align:top; margin:1em; width:350px; font-weight:bold;">  
*[[#new| What's new ]]
*[[#new| What's new]]
*[[#enhancements|Enhancements]]
*[[#enhancements|Improvements]]
*[[#license|License]]
*[[#new_systems|New supported systems & integrations]]
*[[#new_systems|New supported systems & integrations]]
*[[#fixes_v11|Fixed with ''5.1.0'' release]]</div>
<div style="display:inline-block; vertical-align:top; margin:1em; width:350px; font-weight:bold;">
*[[#issues|Issues in ''Apollon 5.1.0'' release]]
*[[#unsupported|Discontinued systems & integrations]]
*[[#unsupported|Discontinued systems & integrations]]
*[[#install| Installation and upgrades]]
*[[#requirements| SEP sesam Server requirements]]</div>
<div style="display:inline-block; vertical-align:top; margin:1em; width:350px;">
*[[#fixes_v11|Fixed with ''5.0.0.11'' release]]
*[[#fixes_SP3|Fixed with ''5.0.0.9 SP3'' release]]
*[[#issues|Issues in ''Jaglion V2 5.0.0.11'' release]]
*[[#end|End of maintenance and support]]
*[[#end|End of maintenance and support]]
*[[#changes|Change reports]]
*[[#changes|Change reports]]
</div></div>
</div></div>
The new SEP sesam version 5.0.0 ''Jaglion V2'' introduces [[Special:MyLanguage/5_0_0:SEP Immutable Storage – SiS|''SiS'' – SEP Immutable Storage]], [[Special:MyLanguage/5_0_0:Backup_to_Azure_Storage|backup to Azure]], powerful [[Special:MyLanguage/Encrypting Si3 NG Deduplication Store|Si3 NG now with encryption]], and some [[Release_Notes_5.1.0_Apollon#ui|UI improvements]].
 
-----


=== {{anchor|new}} What's new ===
=== {{anchor|new}} What's new ===
Line 44: Line 41:
With the combination of archive adjustment options ''Adjustment by barcode only'' and ''Automatic introduction'' you can put new media into a loader and the barcodes of these media are scanned and stored into SEP sesam DB. When these media are loaded into the drive, they are checked for SEP sesam label or initialized (according to your selection for handling the unknown SEP sesam media).
With the combination of archive adjustment options ''Adjustment by barcode only'' and ''Automatic introduction'' you can put new media into a loader and the barcodes of these media are scanned and stored into SEP sesam DB. When these media are loaded into the drive, they are checked for SEP sesam label or initialized (according to your selection for handling the unknown SEP sesam media).


===== Fail over media pool =====
===== [[Special:MyLanguage/5_1_0:Configuring_Si3_NG_Deduplication_Store_with_Object_Lock|S3 Object Lock]] =====


=== Notable changes===
SEP sesam now supports the Object Lock function to protect your data from alteration or deletion when backing up your data to the Amazon S3 cloud storage, Wasabi cloud storage, or other S3-compatible cloud implementation. Object Lock is a data protection feature and enables you to customize immutability of the backup objects. The retention time can be set for a fixed amount of time or indefinitely, and no one can change, delete or overwrite a backup object until its retention time is expired.  
*'''Improved directory structure for LIS files''': On the SEP sesam Server, LIS files are stored in the <SESAM_ROOT>/var/lis directory. Now, a sub-directory is created for every (Sesam) day. This significantly reduces the number of files in one directory, which can be difficult to handle and can slow down the file system operations. LIS files contain information about the backup's unique files and are used by the restore wizard to select and restore unique files.
*'''Changes in CLI commands''': <code>sm_vmdk_interface</code> is replaced by <code>sm_mount</code> and <code>sm_data_store mount_saveset</code> is replaced by <code>sm_mount mount</code>


=== {{anchor|enhancements}}Enhancements ===
===== [[Special:MyLanguage/5_0_0:Hyper-V_Backup_with_Resilient_Change_Tracking_(RCT)|Hyper-V RCT]] =====
SEP sesam supports Resilient change tracking (RCT) for Hyper-V VM disks. At the data block level, RCT tracks changes to a VM disk (VHDX) that occur in between backup operations and only blocks that have changed since the last backup are backed up. This approach is more efficient and can significantly reduce space consumption when you have multiple snapshots on a single host.


;Backup:
===== [[Special:MyLanguage/5_1_0:Configuring_a_Media_Pool|Failover media pool]] =====
*Enforced FULL level backup if the backup was successful (on the client), but errors occurred during post-processing on the server side.
A failover media pool can be configured for any media pool. In case a media pool isn't available for writing for some reason  (out of space, no free media, RDS cannot be reached), a failover media pool can be used for backups or migration.
*The new RHV option <tt>-a use_virtioscsi</tt> allows disk attachment to data mover via bus type VIRTIO_SCSI, default is VIRTIO.


;Restore:
===== [[Special:MyLanguage/5_1_0:Creating_a_Backup_Event|Failover backup task event]] =====
*RHV restore with overwrite now possible.  
In addition to failover media pool, a failover backup task event can be configured for more complex tasks. This enables you to set more options to ensure that a task completes successfully. A failover backup task event is started when data storage (media pool or data store for example) is not accessible and the original task cannot be executed successfully.  
*Fixed failed Oracle restore on older systems in combination with newer SEP sesam Server version.


;[[Special:MyLanguage/5_0_0:Restore_Assistant|Restore Assistant]] (web):
===== License =====
*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 [[Special:MyLanguage/5_0_0:Restore_Assistant|Restore Assistant]].
The new ''SEP sesam Unit'' license model (SEP sesam UNIT PURCHASE AND SUBSCRIPTION LICENSE) enables you to easily identify the license relevant Tier T1/T2/T3 Units, especially in Hyper-V Hypervisor environments. Contact our sales team for more details (sales@sep.de).
*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:
====[[Special:MyLanguage/5_1_0:Creating a Command Event|Abort command]]====
:{{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.'''
The definition for a command is extended to include also an abort command. Abort command will be run when the command event is cancelled during its execution.
*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 [[Special:MyLanguage/5_0_0:Configuring_Si3_NG_Deduplication_Store#upgrade|Configuring Si3 NG Deduplication Store]].}}
[[File:Extras_Si3_DS.jpg|thumb|Define № of Si3 NG stores|link=4_4_3_Beefalo:Configuration#rst_mode]]
*Now you can configure the maximum number of Si3 NG/Si3 deduplication stores on RDS. Note that this settings is only visible in [[Special:MyLanguage/4_4_3_Beefalo:SEP_sesam_GUI#UI_mode|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 [[Release_Notes_5.1.0_Apollon#license|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 [[Special:MyLanguage/5_0_0:Configuring_Certificate-Based_Authentication|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.


=== {{anchor|enhancements_SP1}}Enhancements introduced with service packs===
=== {{anchor|enhancements}}Improvements ===
*Support for Open Enterprise Server 2022
*Mounting Nutanix VMs on Windows Sesam Server
*[[Special:MyLanguage/4_4_3_Beefalo:Exclude_with_Regular_Expressions|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, [http://download.sep.de/servicepacks/5.0.0/5.0.0.9/ Service Pack 2] reset exclude processing to the previous state (to the default behavior before the change in exclude syntax processing).
*<!--#30781-->Full support for LTO-9 drives. See also [[Special:MyLanguage/4_4_3_Beefalo:Drives|Drives]].


=== {{anchor|ui}}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:
* '''SEP sesam settings''': All available SEP sesam global variables are stored with default settings in the SEP sesam table defaults and can be configured in UI/Web UI. '''Note:''' Customers who use global variables '''must insert the specific GLBVs into table defaults before updating''', otherwise they will be overwritten with the SEP sesam default settings.


;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 [[Special:MyLanguage/4_4_3_Beefalo:SEP_sesam_GUI#UI_mode|Selecting UI mode]].
*'''Improved directory structure for LIS files''': On the SEP sesam Server, LIS files are stored in the <SESAM_ROOT>/var/lis directory. Now, a sub-directory is created for every (Sesam) day. This significantly reduces the number of files in one directory, which can be difficult to handle and can slow down the file system operations. LIS files contain information about the backup's unique files, which is used by restore wizard to select and restore unique files. You can use the restore wizard also to check what was backed up.
:[[Image:GUI-displayed_UI_mode.jpg|750px|link=]]
*'''Changes in CLI commands''': <code>sm_vmdk_interface</code> is replaced by <code>sm_mount</code> and <code>sm_data_store mount_saveset</code> is replaced by <code>sm_mount mount</code>.
<br clear=all>
*'''Backup and restore SSH/SSL private/public keypairs''': SEP sesam database can now store the SEP sesam server key, the HTTPS certificate and other important private/public keypairs. In case of a disaster recovery, where the whole backup server needs to be restored from scratch, SEP sesam can recover these important keypairs directly from the restored SEP sesam database.
;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 [[Special:MyLanguage/4_4_3_Beefalo:SEPuler_-_an_event_calendar#event_priority|Setting Event Priorities]].
*'''Immediate start''': You can define a custom start time when you use immediate start option to override the scheduled start time for an event. In addition, immediate start option is supported for more results and tasks, and for schedules in Web UI.
:[[File:drive_channels_priority.jpg|450px|link=4_4_3_Beefalo:Configuration#rst_mode]]
[[File:GUI_Defaults-General-rts-mode_JaglionV2.jpg|thumb|Select restore interfaces|link=4_4_3_Beefalo:Configuration#rst_mode]]
;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 [[Special:MyLanguage/5_0_0:Restore Assistant|Restore Assistant]]'' instead of the ''Legacy restore (deprecated)'' option, which refers to the ''GUI restore wizard''. See [[Special:MyLanguage/4_4_3_Beefalo:SEP_sesam_GUI#rst_mode|Selecting restore interface]].


=== {{anchor|license}}License ===
;Security:
*SEP sesam now supports HTTPS protocol for all control commands and network traffic. The HTTP and FTP interfaces can be switched off and all data traffic is performed over HTTPS interfaces. For more information see [[Special:MyLanguage/Disabling_unsecure_transport_modes|Disabling unsecure transport modes]].


SEP sesam software requires a valid license. For more information, see [[Special:MyLanguage/Licensing|Licensing]].
;Restore Assistant (web):
*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.  
*'''Single File Restore for vSphere via ''attach''''': Attaching virtual disks via NFS is enabled for vSphere Single File Restore.
*This license check does not affect customers with SEP sesam Volume License that does not count the backup storage.
*'''Lifetime (abort time) and Restore Task Name''': Before starting restore, you can set the name for a restore task and define the time at which a (still running) restore task will get cancelled.  
*License violation leads to 15 days remaining run time, during which the license issue must be fixed in either of two ways:
*#The capacity of the used Si3 + Si3 NG stores must be fixed (SEP_DeDup_TB)
*#Contact [mailto:sales@sep.de 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#Licensing FAQs|Licensing FAQs]]).
=== {{anchor|new_systems}}New supported systems and integrations===
;Windows 11
:SEP sesam Server [[SEP_sesam_Release_Versions|5.1.0 'Apollon']] supports Microsoft Windows 11 (with [[Special:MyLanguage/SEP_sesam_BSR_Pro_–_Recovery|BSR Windows Disaster Recovery]]).  


;Microsoft Windows Server 2022
;Web UI enhancements:
:SEP sesam Server [[SEP_sesam_Release_Versions|5.1.0 'Apollon']] supports Microsoft Windows Server 2022 (with [[Special:MyLanguage/SEP_sesam_BSR_Pro_–_Recovery|BSR Windows Disaster Recovery]]).  
*'''Improvements to layout and navigation''': Many improvements were made to enhance the user experience. The ''Sidebar Navigation'' is redesigned, dashboard is optimized and widgets can be configured, accessibility is improved, and new layout, colors and actions are configured for Notifications. More filters are available for searching and limiting displayed entries in table views, more information is available and presented in a more comprehensive and useful way.
*'''Reports can be exported as HTML and PDF''': HTML report can be opened in a new browser tab or window, where you can download it for easier viewing and printing. You can also generate the report in PDF format. The HTML to PDF export is performed by an external tool [https://wkhtmltopdf.org/ <tt>wkhtmltopdf</tt>] which must be installed on the SEP sesam server. To activate the PDF export, add the full path to the wkhtmltopdf executable to the <tt>sm.ini</tt> file:
...
[UI]
html2pdf_converter=/usr/local/bin/wkhtmltopdf
...
*'''New Active Jobs page with timeline''': There is an additional timeline view to show active jobs. If there are no running jobs, the timeline shows the next four events. In addition, you can now view active sub-jobs in a backup details pop-up.
*'''Restart failed jobs''': You can restart failed migration parents, migrations, backups, and replications.
*'''System Configuration''': You can view, add, edit and  delete system properties (DB-Defaults).
*'''Licensing''': In Server status details pop-up you can view License Terms, and upload and install a license file.


;Open Enterprise Server 2022
;{{anchor|ui}}UI enhancements:
:Introduced with Jaglion V2 ''SP3''.
*'''Improvements to default layout and navigation''': The ''Navigation Tree'' is redesigned to improve user experience when working with the SEP sesam. Default layout is optimized, design improvements bring better scaling on high resolution displays, and dark mode is now available. In addition, new informational messages (Tip of the Day) are shown at UI startup.
*'''Saveset state''': savesets have states that indicate health of the saveset (if the saveset is OK, incomplete or corrupted). The saveset state is presented in the relevant views together with backup state (previously, State).
*'''Command definition and view''': The dialog for configuring commands is improved and extended with an option to specify an abort command. The list of configured commands and command events is now available in ''Commands'' view.
*'''Reset password''': The old password is no longer required when superuser resets the password of any user, except superuser.
*'''New exclude type for backup tasks (on Linux)''': To differentiate between files and directories a new regular expression based exclude type is provided for excluding items in a backup task.
*'''Delete multiple events''':  You can now select and delete multiple events at the same time in the event list view.


;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 [[5_0_0:SEP_sesam_OS_and_Database_Support_Matrix#ObjectStorage|SEP sesam Support Matrix – Object Storage]].
=== {{anchor|new_systems}}New supported systems and integrations===
;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 [[5_0_0:SEP_sesam_OS_and_Database_Support_Matrix#StoreOnce|SEP sesam Support Matrix – HPE StoreOnce Catalyst]].
For new supported systems with previous Jaglion version, see [[Release_Notes_5.0.0_Jaglion#new_systems|Jaglion Release Notes]]. 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}}Discontinued systems ===
{{note|On RHEL 8.6 update the VDDK to version 7.0.3, otherwise you might experience problems with vSphere restore.}}
{{Note|In SEP sesam ''Apollon'', SEP announced that it would no longer support:
*RHEL 7
*Debian 9 (Stretch)
*Windows 2012 R2
*Java 1.8
}}
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|install}}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 [[Special:MyLanguage/4_4_3_Beefalo:Updating_SEP_sesam|Updating SEP sesam]].}}
<div style="text-align:left; padding:1em 1em 1em;">
<div style="display:inline-block; vertical-align:top; margin:1em; width:500px;">
 
SEP sesam '''''Jaglion V2 5.0.0.9''''' was released on 30 June 2022. A direct '''upgrade''' from versions '''4.4.3.X''' to version Jaglion V2 '''5.0.0.9''''' is supported.<br />
The latest released  ''Jaglion V2'' versions are:
* SEP sesam 5.0.0.9 [https://download.sep.de/linux/ Linux] [[File:tux.gif]] – released: 30 June 2022.
* SEP sesam 5.0.0.9 [https://download.sep.de/windows/ Windows] [[File:win7.gif]] – released: 30 June 2022.
</div>
<div style="display:inline-block; vertical-align:top; margin:1em; width:500px;">
SEP sesam '''''Jaglion V2 SP3''''' was released on 4 August 2022. You '''must install ''5.0.0.9 Jaglion V2'' before you install ''SP3'''''.<br />
The following are SP3 versions:
* SEP sesam 5.0.0.9 SP2 [https://download.sep.de/servicepacks/5.0.0/5.0.0.9/linux/ Linux] [[File:tux.gif]] – released: 4 August 2022.
* SEP sesam 5.0.0.9 SP2 [https://download.sep.de/servicepacks/5.0.0/5.0.0.9/windows/ Windows] [[File:win7.gif]] – released: 4 August 2022.
</div></div>
 
===== {{anchor|linux}}[[File: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
 
For details, see [[Special:MyLanguage/5_0_0:SEP_sesam_Quick_Install_Guide#linux|Installation on Linux]]. For a list of supported Linux versions, see the [[5_0_0:SEP_sesam_OS_and_Database_Support_Matrix#Linux|SEP sesam Support Matrix]].
 
===== {{anchor|windows}}[[File:win7.gif]]  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 [[Special:MyLanguage/5_0_0:SEP_sesam_Quick_Install_Guide#windows|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 [[5_0_0:SEP_sesam_OS_and_Database_Support_Matrix#Windows|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 [[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_OS_and_Database_Support_Matrix#Windows|Microsoft Windows 11]]
:SEP sesam Server 5.1.0 'Apollon' supports Microsoft Windows 11 (with [[Special:MyLanguage/SEP_sesam_BSR_Pro_–_Recovery|BSR Windows Disaster Recovery]]).


====Post update task====
;[[SEP_sesam_OS_and_Database_Support_Matrix#Windows|Microsoft Windows Server 2022]]
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 [[Special:MyLanguage/5_0_0:VMware_Backup|vSphere backup]] should be performed to allow mounting and attaching VMDKs.  
:SEP sesam Server 5.1.0 'Apollon' supports Microsoft Windows Server 2022 (with [[Special:MyLanguage/SEP_sesam_BSR_Pro_–_Recovery|BSR Windows Disaster Recovery]]).


==={{anchor|requirements}}SEP sesam Server requirements===
;[[SEP_sesam_OS_and_Database_Support_Matrix#Proxmox_VE|Proxmox 7.3]]
'''Java'''  
:Introduced with ''Apollon'' in SEP sesam VM extensions


The SEP sesam GUI is based on Java and requires a Java Runtime Environment (JRE).
;[[SEP_sesam_OS_and_Database_Support_Matrix#VMware|vSphere 8]]
*SEP sesam ''5.0.0.9 Jaglion V2 '''Service Packs''''' require '''Java 11'''.
:Introduced with ''Apollon'' in SEP sesam VM extensions
*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 [[Release_Notes_5.1.0_Apollon#30942|SEP sesam installation fails if only Java 17 is installed]] for details.
The required [[Special:MyLanguage/Java_Compatibility_Matrix|Java version depends on the SEP sesam version]].


====Previous release====
For a complete list of supported OS and databases, see [[5_0_0:SEP_sesam_OS_and_Database_Support_Matrix|SEP sesam Support Matrix]].
* [[Release_Notes_5.0.0_Jaglion_V2|Release notes for SEP sesam 5.0.0 ''Jaglion V2'']]


== {{anchor|fixes_v11}}Fixes: SEP sesam Server 5.1.0 Apollon ==
== {{anchor|fixes_v11}}Fixes: SEP sesam Server 5.1.0 Apollon ==
{{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.}}
{{Box Hint|Fixed with [http://download.sep.de/ 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 5.1.0 Apollon.
}}
== {{anchor|fixes_SP3}}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.}}
{{Box Hint|Fixed with [http://download.sep.de/servicepacks/5.0.0/5.0.0.9/ 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]].
}}


== {{anchor|fixes_SP2}}Fixes: SEP sesam Server 5.0.0.9 Jaglion V2 ''SP2'' ==
{{Box Hint|Fixed with [http://download.sep.de/ 5.1.0 ''Apollon'']|
{{Box Hint|Fixed with [http://download.sep.de/servicepacks/5.0.0/5.0.0.9/ 5.0.0.9 ''Jaglion V2 SP2'']|
;Manually added exclude patterns have been deleted during update on backup clients. Version 5.1.0 (or higher) retains manually added exclude patterns on backup Clients.
;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. <tt>.tmp/$</tt>), it is recognized as directory exclude regex. If there is no trailing slash "/" at the end (e.g. <tt>.tmp</tt>), it is recognized as file exclude regex. Now to exclude a folder, the syntax is: <code>\./folder/folder_to_exclude/$</code>
: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. [http://download.sep.de/servicepacks/5.0.0/5.0.0.9/ 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 (<code>-o excl<nowiki>=</nowiki>regexp</code>; 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.
}}
}}
== {{anchor|fixes_SP1}}Fixes: SEP sesam Server 5.0.0.9 ''Jaglion V2 SP1'' ==
{{Box Hint|Fixed with [http://download.sep.de/servicepacks/5.0.0 5.0.0.9 ''Jaglion V2 SP1'']|
;[[File:Warning sign.png|20px]]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
&rArr;  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.
}}


== {{anchor|issues}}Known issues and limitations ==
== {{anchor|issues}}Known issues and limitations ==
Line 280: Line 125:
{{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.x ''Jaglion V2'' known issues|
{{Box Hint Y|5.1.0.x ''Apollon'' known issues|
-----
-----
==={{anchor|major}}Severity: MAJOR===
==={{anchor|major}}Severity: MAJOR===
<!-- delete this section when new issues are described
;SEP sesam v. 5.0.0.9 – Manually added exclude patterns get deleted during update
;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.
:* Manually added exclude patterns have been deleted during update on backup clients. The Sesam server update preserved exclude patterns on the server only.
Line 298: Line 144:
;SEP sesam v. 5.0.0.3-5.0.0.9 – Hyper-V restore of Hyper-V RCT backup fails with error
;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''.
:* 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:''' SEP is working on this issue and will provide a fix as soon as possible.  
:::'''Resolution:''' SEP is working on this issue and will provide a fix as soon as possible. -->
-----
-----
==={{anchor|normal}}Severity: NORMAL===
==={{anchor|normal}}Severity: NORMAL===
[[File:information_sign.png|20px]] SEP sesam v. 5.0.0.9 SP1 – The old syntax for regexp excludes no longer works for directories in SP1
;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
:* ''(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. <tt>.tmp/$</tt>), it is recognized as directory exclude regex. If there is no trailing slash "/" at the end (e.g. <tt>.tmp</tt>), it is recognized as file exclude regex. Now to exclude a folder, the syntax is: <code>\./folder/folder_to_exclude/$</code>
:::'''Fix:''' Install VDDK version 7.0.3 on the data mover.
: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.
<!-- replace
:::'''Workaround:''' Change the syntax in the existing tasks to distinguish between excluding files and directories. For details, see [[Special:MyLanguage/4_4_3_Beefalo:Exclude_with_Regular_Expressions|Exclude with Regular Expressions]].
;SEP sesam v. 5.0.0.9, incl. ''Service Packs'' – SEP sesam installation fails if only Java 17 is installed
:::'''Resolution:''' Fixed with '''SP2''' for Jaglion V2. [http://download.sep.de/servicepacks/5.0.0/5.0.0.9/ 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 (<code>-o excl<nowiki>=</nowiki>regexp</code>; 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 [[Special:MyLanguage/Standard_Backup_Procedure#bck_options|backup options in the GUI]] to distinguish between files and folders using ending "/$": <code>-o excl<nowiki>=</nowiki>regexp_split</code> 
 
;{{anchor|30942}}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.
:* 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 <code>sm_setup set_java_path -f <java_17_installation_path></code>.  
:::'''Workaround:''' You can enable the use of ''Java 17'' from the command line with <code>sm_setup set_java_path -f <java_17_installation_path></code>.  
Line 319: Line 162:
;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
;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.
:* 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.  
:::'''Resolution:''' SEP is working on this issue and will provide a fix as soon as possible. -->
 
-----
-----
<!-- ====''GUI issues''====
------->
==={{anchor|minor}}Severity: MINOR===
==={{anchor|minor}}Severity: MINOR===
 
<!-- replace
;SEP sesam v. 5.0.0.x – Clean installation of SEP sesam may fail on RHEL version 8.5 or higher
;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.
:*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.
Line 341: Line 181:


;SEP sesam v. 4.4.3.86–5.0.0.x – ''Initial Seeding'' functionality temporarily removed
;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.
:*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. -->
}}</onlyinclude>
}}</onlyinclude>
=== {{anchor|unsupported}}Discontinued systems ===
In SEP sesam ''Apollon'', SEP announced that it would no longer support:
*RHEL 7
*Debian 9 (Stretch)
*Windows 2012 R2
*Java 1.8
For details on discontinued systems, see [[Unsupported OS]]. For a complete list of supported SEP sesam Clients, see [[SEP_sesam_OS_and_Database_Support_Matrix|SEP sesam Support Matrix]].


== {{anchor|end}}End of maintenance and support ==
== {{anchor|end}}End of maintenance and support ==
Line 352: Line 201:
*SEP sesam [[SEP_sesam_Release_Versions|4.4.3 Tigon]] -> September 2020
*SEP sesam [[SEP_sesam_Release_Versions|4.4.3 Tigon]] -> September 2020


=== Discontinued SEP sesam Server OS ===
For the list of all SEP sesam versions see [[SEP_sesam_Release_Versions|SEP sesam Release Versions]].
{{:Unsupported OS}}


== {{anchor|changes}}Change reports ==
== {{anchor|changes}}Change reports ==
Line 359: Line 207:
*[[Change report Jaglion V2 Service Packs]]
*[[Change report Jaglion V2 Service Packs]]


== See also ==
 
[[SEP_sesam_Release_Versions|SEP sesam Release Versions]]
{{Copyright SEP AG|en}}

Revision as of 14:58, 16 March 2023


Tux.gif Download for Linux: SEP sesam 5.1.0 Linux Win7.gif Download for Windows: SEP sesam 5.1.0 Windows
See Installation on Linux See Installation on Windows
Information sign.png Note

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


What's new

Introducing new media by barcode only

SEP sesam offers the functionality for introducing new media into the loader without interrupting or blocking any backup, restore or migration. SEP sesam checks the barcodes of the tapes that are not in drives and does not block all drives for backup or restore. This enables introducing new media and adjusting the archive while the drives are in use.

With the combination of archive adjustment options Adjustment by barcode only and Automatic introduction you can put new media into a loader and the barcodes of these media are scanned and stored into SEP sesam DB. When these media are loaded into the drive, they are checked for SEP sesam label or initialized (according to your selection for handling the unknown SEP sesam media).

S3 Object Lock

SEP sesam now supports the Object Lock function to protect your data from alteration or deletion when backing up your data to the Amazon S3 cloud storage, Wasabi cloud storage, or other S3-compatible cloud implementation. Object Lock is a data protection feature and enables you to customize immutability of the backup objects. The retention time can be set for a fixed amount of time or indefinitely, and no one can change, delete or overwrite a backup object until its retention time is expired.

Hyper-V RCT

SEP sesam supports Resilient change tracking (RCT) for Hyper-V VM disks. At the data block level, RCT tracks changes to a VM disk (VHDX) that occur in between backup operations and only blocks that have changed since the last backup are backed up. This approach is more efficient and can significantly reduce space consumption when you have multiple snapshots on a single host.

Failover media pool

A failover media pool can be configured for any media pool. In case a media pool isn't available for writing for some reason (out of space, no free media, RDS cannot be reached), a failover media pool can be used for backups or migration.

Failover backup task event

In addition to failover media pool, a failover backup task event can be configured for more complex tasks. This enables you to set more options to ensure that a task completes successfully. A failover backup task event is started when data storage (media pool or data store for example) is not accessible and the original task cannot be executed successfully.

License

The new SEP sesam Unit license model (SEP sesam UNIT PURCHASE AND SUBSCRIPTION LICENSE) enables you to easily identify the license relevant Tier T1/T2/T3 Units, especially in Hyper-V Hypervisor environments. Contact our sales team for more details (sales@sep.de).

Abort command

The definition for a command is extended to include also an abort command. Abort command will be run when the command event is cancelled during its execution.

Improvements

  • SEP sesam settings: All available SEP sesam global variables are stored with default settings in the SEP sesam table defaults and can be configured in UI/Web UI. Note: Customers who use global variables must insert the specific GLBVs into table defaults before updating, otherwise they will be overwritten with the SEP sesam default settings.
  • Improved directory structure for LIS files: On the SEP sesam Server, LIS files are stored in the <SESAM_ROOT>/var/lis directory. Now, a sub-directory is created for every (Sesam) day. This significantly reduces the number of files in one directory, which can be difficult to handle and can slow down the file system operations. LIS files contain information about the backup's unique files, which is used by restore wizard to select and restore unique files. You can use the restore wizard also to check what was backed up.
  • Changes in CLI commands: sm_vmdk_interface is replaced by sm_mount and sm_data_store mount_saveset is replaced by sm_mount mount.
  • Backup and restore SSH/SSL private/public keypairs: SEP sesam database can now store the SEP sesam server key, the HTTPS certificate and other important private/public keypairs. In case of a disaster recovery, where the whole backup server needs to be restored from scratch, SEP sesam can recover these important keypairs directly from the restored SEP sesam database.
  • Immediate start: You can define a custom start time when you use immediate start option to override the scheduled start time for an event. In addition, immediate start option is supported for more results and tasks, and for schedules in Web UI.
Security
  • SEP sesam now supports HTTPS protocol for all control commands and network traffic. The HTTP and FTP interfaces can be switched off and all data traffic is performed over HTTPS interfaces. For more information see Disabling unsecure transport modes.
Restore Assistant (web)
  • Single File Restore for vSphere via attach: Attaching virtual disks via NFS is enabled for vSphere Single File Restore.
  • Lifetime (abort time) and Restore Task Name: Before starting restore, you can set the name for a restore task and define the time at which a (still running) restore task will get cancelled.
Web UI enhancements
  • Improvements to layout and navigation: Many improvements were made to enhance the user experience. The Sidebar Navigation is redesigned, dashboard is optimized and widgets can be configured, accessibility is improved, and new layout, colors and actions are configured for Notifications. More filters are available for searching and limiting displayed entries in table views, more information is available and presented in a more comprehensive and useful way.
  • Reports can be exported as HTML and PDF: HTML report can be opened in a new browser tab or window, where you can download it for easier viewing and printing. You can also generate the report in PDF format. The HTML to PDF export is performed by an external tool wkhtmltopdf which must be installed on the SEP sesam server. To activate the PDF export, add the full path to the wkhtmltopdf executable to the sm.ini file:
...
[UI]
html2pdf_converter=/usr/local/bin/wkhtmltopdf
...
  • New Active Jobs page with timeline: There is an additional timeline view to show active jobs. If there are no running jobs, the timeline shows the next four events. In addition, you can now view active sub-jobs in a backup details pop-up.
  • Restart failed jobs: You can restart failed migration parents, migrations, backups, and replications.
  • System Configuration: You can view, add, edit and delete system properties (DB-Defaults).
  • Licensing: In Server status details pop-up you can view License Terms, and upload and install a license file.
UI enhancements
  • Improvements to default layout and navigation: The Navigation Tree is redesigned to improve user experience when working with the SEP sesam. Default layout is optimized, design improvements bring better scaling on high resolution displays, and dark mode is now available. In addition, new informational messages (Tip of the Day) are shown at UI startup.
  • Saveset state: savesets have states that indicate health of the saveset (if the saveset is OK, incomplete or corrupted). The saveset state is presented in the relevant views together with backup state (previously, State).
  • Command definition and view: The dialog for configuring commands is improved and extended with an option to specify an abort command. The list of configured commands and command events is now available in Commands view.
  • Reset password: The old password is no longer required when superuser resets the password of any user, except superuser.
  • New exclude type for backup tasks (on Linux): To differentiate between files and directories a new regular expression based exclude type is provided for excluding items in a backup task.
  • Delete multiple events: You can now select and delete multiple events at the same time in the event list view.

New supported systems and integrations

Information sign.png Note
On RHEL 8.6 update the VDDK to version 7.0.3, otherwise you might experience problems with vSphere restore.
Microsoft Windows 11
SEP sesam Server 5.1.0 'Apollon' supports Microsoft Windows 11 (with BSR Windows Disaster Recovery).
Microsoft Windows Server 2022
SEP sesam Server 5.1.0 'Apollon' supports Microsoft Windows Server 2022 (with BSR Windows Disaster Recovery).
Proxmox 7.3
Introduced with Apollon in SEP sesam VM extensions
vSphere 8
Introduced with Apollon in SEP sesam VM extensions

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

Fixes: SEP sesam Server 5.1.0 Apollon

Fixed with 5.1.0 Apollon:
Manually added exclude patterns have been deleted during update on backup clients. Version 5.1.0 (or higher) retains manually added exclude patterns on backup Clients.

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.1.0.x Apollon known issues:

Severity: MAJOR


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.

Severity: MINOR

Discontinued systems

In SEP sesam Apollon, SEP announced that it would no longer support:

  • RHEL 7
  • Debian 9 (Stretch)
  • Windows 2012 R2
  • Java 1.8

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

End of maintenance and support

Obsolete SEP sesam Server versions

The following versions of SEP sesam are no longer supported:

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

Change reports


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.