Release Notes 5.1.0 Apollon: Difference between revisions

From SEPsesam
(source text cleanup)
(37 intermediate revisions by 2 users not shown)
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'': major 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;" |May 25, 2023 <br />Installation is highly recommended as it includes various performance, stability, and other key customer fixes. For details, see [[Change report 5.1.0 Apollon]].  
|}</div>
|}</div>


<div style="text-align:left; padding:1em 1em 1em;">
{|style="margin: auto; margin-top:50px; margin-bottom:5px; width:90%; border:0px solid grey;"
<div style="display:inline-block; vertical-align:top; margin:1em; width:350px;">
|[[File:tux.gif]] '''Download for Linux: [https://download.sep.de/ SEP sesam 5.1.0 Linux]'''
*[[Release_Notes_5.1.0_Apollon#new| What's new ]]
|[[File:win7.gif]] '''Download for Windows: [https://download.sep.de/ SEP sesam 5.1.0 Windows]'''
*[[Release_Notes_5.1.0_Apollon#enhancements|Enhancements]]
|-
*[[Release_Notes_5.1.0_Apollon#license|License]]
|See [[Special:MyLanguage/SEP_sesam_Quick_Install_Guide#linux|Installation on Linux]]
*[[Release_Notes_5.1.0_Apollon#new_systems|New supported systems & integrations]]
|See [[Special:MyLanguage/SEP_sesam_Quick_Install_Guide#windows|Installation on Windows]]
*[[Release_Notes_5.1.0_Apollon#install| Installation and upgrades]]
|}
*[[Release_Notes_5.1.0_Apollon#requirements| SEP sesam Server requirements]]</div>


<div style="display:inline-block; vertical-align:top; margin:1em; width:350px;">
{{note|
*[[Release_Notes_5.1.0_Apollon#fixes_v11|Fixed with ''5.0.0.11'' release]]
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]].}}
*[[Release_Notes_5.1.0_Apollon#fixes_SP3|Fixed with ''5.0.0.9 SP3'' release]]
*[[Release_Notes_5.1.0_Apollon#issues|Issues in ''Jaglion V2 5.0.0.11'' release]]
*[[Release_Notes_5.1.0_Apollon#end|End of maintenance and support]]
*[[Release_Notes_5.1.0_Apollon#changes|Change reports]]
</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 ===
===== [[Special:MyLanguage/5_1_0:Setting_up_Archive_Adjustment|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).
 
===== Fail over media pool =====
 
=== Notable changes===
* <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>
 
{{<translate>
note</translate>|<translate>gv_conf_lisdir_with_date</translate>}}
 
=== {{anchor|enhancements}}Enhancements ===
 
;Backup:
*Enforced FULL level backup if the backup was successful (on the client), but errors occurred during post-processing on the server side.
*The new RHV option <tt>-a use_virtioscsi</tt> allows disk attachment to data mover via bus type VIRTIO_SCSI, default is VIRTIO.
 
;Restore:
*RHV restore with overwrite now possible.
*Fixed failed Oracle restore on older systems in combination with newer SEP sesam Server version.
 
;[[Special:MyLanguage/5_0_0:Restore_Assistant|Restore Assistant]] (web):
*Additional task types are supported: NetIQ/Micro Focus eDirectory, Micro Focus iFolder, PostgreSQL and MySQL. You can perform a regular restore or write your backups to dump files (equivalent to the GUI option Write saveset into file). For more information, see [[Special:MyLanguage/5_0_0:Restore_Assistant|Restore Assistant]].
*Many usability improvements and new options: ''Restore ACLs'' only option added, restore task name can be changed, link to install ''guestfs'' tools added, improved messages when a backup cannot be mounted, preferred media pool can be selected as a mount option, and improved vSphere VMDK selection with clearer use cases.
 
;Si3 NG:
:{{note|The old generation '''Si3 deduplication store is deprecated'''. This means that the old generation Si3 is no longer being enhanced, but is still supported until further notice. '''SEP strongly recommends using the new Si3 NG data store instead, especially if the data is to be stored to S3 Cloud.'''
*If you are using an old generation Si3 deduplication store with S3, '''you will not be able to restore from S3 via the GUI'''.
*You can configure a new Si3 NG and an old Si3 in parallel on the same host and replicate from the old Si3 to the Si3 NG store. For details, see [[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===
*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:
 
;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]].
:[[Image:GUI-displayed_UI_mode.jpg|750px|link=]]
<br clear=all>
;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]].
:[[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 ===
 
SEP sesam software requires a valid license. For more information, see [[Special:MyLanguage/Licensing|Licensing]].
*Version 5.0.0.9 introduces a check for the Si3 NG capacity so after an update from version ''Jaglion (5.0.0.[34])'' to a new version the licensed deduplication storage may no longer be sufficient. This only affects customers who are already using Si3 NG deduplication store.
*This license check does not affect customers with SEP sesam Volume License that does not count the backup storage.
*License violation leads to 15 days remaining run time, during which the license issue must be fixed in either of two ways:
*#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.0.0.9 ''Jaglion V2'']] supports Windows 11 (without [[Special:MyLanguage/SEP_sesam_BSR_Pro_–_Recovery|BSR Windows Disaster Recovery]]).
:*''BSR Windows Disaster Recovery'' for Windows 11 is expected to be fully supported ASAP.
;Open Enterprise Server 2022
:Introduced with Jaglion V2 ''SP3''.
 
;Expanded support for S3 compatible storage:SEP sesam supports S3 as a generic interface based on the new deduplication store Si3 NG. For details on newly supported S3 targets, see [[5_0_0:SEP_sesam_OS_and_Database_Support_Matrix#ObjectStorage|SEP sesam Support Matrix – Object Storage]].
;Debian and Ubuntu supported with HPE StoreOnce Catalyst:For a full list of supported OS for SEP sesam SEP sesam integration with HPE StoreOnce Catalyst, see [[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 ===
No changes. 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="text-align:left; padding:1em 1em 1em;">
<div style="display:inline-block; vertical-align:top; margin:1em; width:500px;">
<div style="display:inline-block; vertical-align:top; margin:1em; width:350px; font-weight:bold;">
*[[#new| What's new]]
*[[#enhancements|Improvements]]
*[[#new_systems|New supported systems & integrations]]
*[[#fixes_v11|Fixed with ''5.1.0'' release]]</div>


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 />
<div style="display:inline-block; vertical-align:top; margin:1em; width:350px; font-weight:bold;">
The latest released  ''Jaglion V2'' versions are:
*[[#issues|Issues in ''Apollon 5.1.0'' release]]
* SEP sesam 5.0.0.9 [https://download.sep.de/linux/ Linux] [[File:tux.gif]] – released: 30 June 2022.
*[[#unsupported|Discontinued systems & integrations]]
* SEP sesam 5.0.0.9 [https://download.sep.de/windows/ Windows] [[File:win7.gif]] – released: 30 June 2022.
*[[#end|End of maintenance and support]]
</div>
*[[#changes|Change reports]]
<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>
</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:
=== {{anchor|new}} What's new ===
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]].
===== [[Special:MyLanguage/5_1_0:Configuring_Si3_NG_Deduplication_Store_with_Object_Lock|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.  


===== {{anchor|windows}}[[File:win7.gif]] Windows specific =====
===== [[Special:MyLanguage/5_1_0:Performing_a_Virus_Scan_Before_Single_File_Restore|Performing virus scan with IKARUS scan.server]] =====
;Installation
SEP sesam introduces a new feature that enables a virus scan on selected files before initiating a Single File Restore. By performing a virus scan with the latest Virus Database (VDB) before starting the restore, SEP sesam effectively prevents restoring any known infections that might have gone undetected during the backup process.
:*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]].
===== [[Special:MyLanguage/5_1_0:SEP_Immutable_Storage_–_SiS|Fighting ransomware with SEP sesam Immutable Storage – SiS]] =====
SEP Immutable Storage or SiS is a file storage feature resistant to ransomware attacks, based on Si3 NG on Linux. Even with full admin access to the SEP sesam backup server, attackers cannot delete, modify, or encrypt data stored on SiS. The idea behind SEP sesam Immutable Storage is that stored data remains completely static in its original and unchanged form throughout its lifetime. This means that businesses can quickly recover from a ransomware attack, even if they have lost access to their data and servers, by using stored data copies that have remained unchanged and intact to restore the entire operating environment.


====Post update task====
====[[Special:MyLanguage/5_1_0:SEP_Customer_Experience|SEP Customer Experience Program (SCE)]]====
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 Customer Experience (SCE) collects technical information from participating customers. This data is used to improve SEP sesam, both for existing needs and for future development.


==={{anchor|requirements}}SEP sesam Server requirements===
===== [[Special:MyLanguage/5_0_0:Hyper-V_Backup_with_Resilient_Change_Tracking_(RCT)|Hyper-V Resilient Change Tracking (RCT)]] =====
'''Java'''
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.


The SEP sesam GUI is based on Java and requires a Java Runtime Environment (JRE).
===== [[Special:MyLanguage/5_1_0:Configuring_a_Media_Pool|Failover media pool]] =====
*SEP sesam ''5.0.0.9 Jaglion V2 '''Service Packs''''' require '''Java 11'''.
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.
*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====
===== [[Special:MyLanguage/5_1_0:Creating_a_Backup_Event|Failover backup task event]] =====
* [[Release_Notes_5.0.0_Jaglion_V2|Release notes for SEP sesam 5.0.0 ''Jaglion V2'']]
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.  


== {{anchor|fixes_v11}}Fixes: SEP sesam Server 5.1.0 Apollon ==
====[[Special:MyLanguage/5_1_0:Creating a Command Event|Abort command]]====
{{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.}}
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.
{{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'' ==
===== [[Special:MyLanguage/5_1_0:Setting_up_Archive_Adjustment|Introducing new media by barcode only]]=====
{{Box Hint|Fixed with [http://download.sep.de/servicepacks/5.0.0/5.0.0.9/ 5.0.0.9 ''Jaglion V2 SP2'']|
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.  
;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'' ==
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).
{{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
====[[Special:MyLanguage/5_1_0:Tape Management#save_metadata|Saving backup metadata on tape]]====
:*External job remains in queue when submit timeout expires due to incorrect check for backup operation.
Saving backup metadata on tape allows backup administrators to store critical information about a backup on the tape, which can be used for restoring data in the event of a disaster or data loss. Backup metadata information includes important details about the backup and can be used to recreate DB entries that are required for FULL restore.


;SEP sesam v. 5.0.0.3-5.0.0.9 – Problems with Si3 NG on S3
To enable saving the meta file archive (LIS/SGM/DB entries) on tape by default, set the global variable <tt>gv_conf_no_info_upload_sms</tt> to 0.
&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
===== [[Special:MyLanguage/Licensing|License]] =====
:*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.
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).


;SEP sesam v. 5.0.0.9 – The GUI shows an incorrect maintenance expiration message instead of the more important license expiration message
=== {{anchor|enhancements}}Improvements ===
:*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 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.


;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
*'''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.
:* 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.
*'''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>.
*'''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.


;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
;Security:
:*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 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 v. 5.0.0.9 – The sesam bootstrap DB export does not contain information about the migrated sesam backup
;Restore Assistant (web):
:* 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.  
*'''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.  


;SEP sesam v. 5.0.0.9 – The incorrect operation of ''Cancel Current Running Activities'' stops all running sm_break_task processes
;Web UI enhancements:
:* 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.
*'''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.


;SEP sesam v. 5.0.0.9 – Backup of ACLs on a CIFS share fails with ERROR_PRIVILEGE_NOT_HELD (1314)  
;{{anchor|ui}}UI enhancements:
:* 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''.  
*'''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.


;SEP sesam v. 4.4.3-5.0.0.9 – Backup of virtual machines in subdirectories fails
=== {{anchor|new_systems}}New supported systems and integrations===
:* 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)''
{{note|On RHEL 8.6 update the VDDK to version 7.0.3, otherwise you might experience problems with vSphere restore.}}
:* 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
;[[SEP_sesam_OS_and_Database_Support_Matrix#Windows|Microsoft Windows 11]]
:* 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 Server 5.1.0 ''Apollon'' supports Microsoft Windows 11 (with [[Special:MyLanguage/SEP_sesam_BSR_Pro_–_Recovery|BSR Windows Disaster Recovery]]).


;SEP sesam v. 5.0.0.9 – Deactivated VM tasks are not excluded from the license count
;[[SEP_sesam_OS_and_Database_Support_Matrix#Windows|Microsoft Windows Server 2022]]
:* After deactivating VM tasks that exceed the number of allowed tasks defined by the license, a license violation still occurs.
:SEP sesam Server 5.1.0 ''Apollon'' supports Microsoft Windows Server 2022 (with [[Special:MyLanguage/SEP_sesam_BSR_Pro_–_Recovery|BSR Windows Disaster Recovery]]).


;SEP sesam v. 5.0.0.9 – The status of a data store is incorrectly displayed as OK when RDS is unreachable
;[[SEP_sesam_OS_and_Database_Support_Matrix#Proxmox_VE|Proxmox 7.3]]
:*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.
:Introduced with ''Apollon'' in SEP sesam VM extensions.


;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
;[[SEP_sesam_OS_and_Database_Support_Matrix#VMware|vSphere 8]]
:*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.
:Introduced with ''Apollon'' in SEP sesam VM extensions.


;SEP sesam v. 4.4.3.86-5.0.0.9 – ''DB:results.stop_time'' written in wrong format
For a complete list of supported OS and databases, see [[5_0_0:SEP_sesam_OS_and_Database_Support_Matrix|SEP sesam Support Matrix]].
:* 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
== {{anchor|fixes_v11}}Fixes: SEP sesam Server 5.1.0 Apollon ==
:* 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
{{Box Hint|Fixed with [http://download.sep.de/ 5.1.0.5 ''Apollon'']|
:* Since migrations and replications are no longer represented in the ''DB:results'' table, the ''Migration'' and ''Replication'' filters have no effect.
;SEP sesam since v. 5.1.0.2 - Hyper-V RCT INCR may run with wrong reference if previous Hyper-V backup failed or was aborted
::Hyper-V may exhibit a backup issue where the timestamp for RCT backups may be set incorrectly if backup failed or was aborted, which can lead to an invalid backup chain. In such cases the subsequent INCR backups may reference the failed backup instead of the last successful backup.
:::'''Workaround:''' Start a FULL backup in case a FULL or INCR backup did not finish sucessfully. This will ensure that the backup timestamp is correctly set, preventing any further issues in the backup chain. It is also recommended to regularly test the validity of backups and monitor backup logs for any errors or anomalies.
:::'''Resolution:''' Fixed with '''5.1.0.5'''.


;BUGFIX: Fixing the double free problem in sm_qm_main that can trigger sm_qm_main crash.
* Hyper-V restore and Hyper-V Mount and SFR restore
* Restore of a sparse file bigger than 4GB gets stuck but destination file becomes larger and larger
* (#32096) Update of client via Sesam server may fail because sub-processes are still running
* (#32100) Web UI: Write correct target path for NDMP restore to original location
* (#32035) NDMP generation restore of migrated saveset with one selected directory failed due to empty SEL file for FULL saveset
* (#32035) NDMP restore failed because of spaces in name of the selected file or directory
* (#32091) Nutanix VM mount failed
}}
}}


== {{anchor|issues}}Known issues and limitations ==
== {{anchor|issues}}Known issues and limitations ==
Line 272: Line 150:
{{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===
;SEP sesam v. 5.0.0.9 – Manually added exclude patterns get deleted during update
:* Manually added exclude patterns have been deleted during update on backup clients. The Sesam server update preserved exclude patterns on the server only.
:::'''Resolution:''' If you have sm.ini [SBC_EXCLUDE] patterns set manually, avoid update with SEP sesam version lower than 5.0.0.11 on backup Clients. Perform update with '''5.0.0.11''' to retain manually added exclude patterns. See [[Special:MyLanguage/Creating_Exclude_List#Using_sm.ini_to_completely_exclude_files_from_backups_on_the_client|Creating exclude list]].
;SEP sesam v. 5.0.0.9 – Possible data loss due to a faulty purge function
:* Due to the missing database entry by the purge process ('Delete everything older than the oldest Sesam day'), an FSCK error may occur as <tt>sm_pur_status</tt> could accidentally remove backup information for migrated savesets. Although the migrated version of the backup still exists, it is no longer listed in the database. Consequently, the administrator may decide to use the function ''Clean up Data Store'' to fix the error, which results in the deletion of the migrated saveset and loss of data.
:::'''Resolution:''' Fixed with '''SP3'''.


;SEP sesam v. 5.0.0.2-5.0.0.9 – Linux backup silently skips a directory if [[Special:MyLanguage/Creating_Exclude_List#nosbc|<tt>.nosbc</tt>]] file is part of backup source
:* ''(Linux only)'' When backing up a backup source that contains one or more [[Special:MyLanguage/Creating_Exclude_List#nosbc|<tt>.nosbc</tt>]] files, a directory is silently skipped, but the backup is marked as successful. For example, if there is a backup source ''/data'' that contains ''/data/ds1/.nosbc'', ''/data/ds1/pages/'' and ''/data/ds1/trash/'', then the ''pages/'' or ''trash/'' directories are not backed up. If a backup source does not contain a <tt>.nosbc</tt> file, all files are backed up successfully.
:::'''Workaround:''' Since [[Special:MyLanguage/SEP_sesam_Glossary#SBC|sbc]] incorrectly excludes a directory from backup if a file <tt>.nosbc</tt> is part of the backup source,  use the ''-o noexcl'' switch in the backup options (backup task properties, tab ''Options'' -> ''Backup options'') when backing up a backup source with a <tt>.nosbc</tt> file.
:::'''Resolution:''' SEP is working on this issue and will provide a fix as soon as possible.


;SEP sesam v. 5.0.0.3-5.0.0.9 – Hyper-V restore of Hyper-V RCT backup fails with error
:* When restoring a Hyper-V VM from a Hyper-V VM RTC backup under a new VM name, the restore fails with an error: ''Failed to read metadata file''.
:::'''Resolution:''' 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.1.0.5 - (#32381) PostgreSQL startup failure after changing SEP sesam service user (Windows only)
:* ''(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>
::By default, the SEP sesam service starts under the SYSTEM user account. At installation, postgreSQL database is set to start under this account. However, if the user name of the SEP sesam service is changed from SYSTEM (for example, to Administrator) after installation, PostgreSQL encounters startup issues and fails to start.
: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.
::Changing the user name of the SEP sesam service affects the ownership and permissions of the PostgreSQL data directory, typically the <tt>db_pg</tt> folder. As a result, PostgreSQL is unable to access the necessary files and resources, causing failure to start up.
:::'''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]].
:::'''Solution:''' You can revert to the previous SEP sesam service account (SYSTEM), or change the ownership and permissions of the PostgreSQL data directory (<tt>db_pg</tt> folder) to the used SEP sesam service account user. In this case make sure you change ownership and permissions for subfolders and files as well (use Windows Explorer option ''Replace owner on subcontainers and objects''). PostgreSQL regains the necessary access rights, enabling it to start successfully. Note that this workaround modifies the folder's ownership and permissions, so make sure that the used user account has appropriate privileges for managing the SEP sesam database.
:::'''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 v. 5.1.0.5 - (#32359) The GUI options for handling running events during NEWDAY are not functioning as intended
:* 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.
::The functions of the two options for handling running events during NEWDAY have been inadvertently swapped, causing them to perform the opposite of their expected behavior. These two options can be found in Newday event Properties window, accessed from ''Main Selection -> Scheduling -> Schedules'' by double-clicking the Newday event (for more information see [[Special:MyLanguage/5_1_0:Newday_Event|Newday Event]]).
:::'''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:''' To achieve the desired behavior, select the opposite option of your intended action. For instance, if you want Newday to continue all running activities, select the option '''Cancel all running activities''' (and vice versa).
:::'''Resolution:''' ''Java 17'' is planned to be supported with the next major release.  
:::'''Resolution:''' SEP is working on this issue and will provide a fix as soon as possible.


;SEP sesam v. 5.0.0.3-5.0.0.9 – New Hyper-V RCT backups do not support single file restore (via VFS mount)
;SEP sesam v. 5.1.0.5 - (#32360) On the German GUI Client the default setting for deleting savesets after migration is set to ON
:* As of 5.0.0 Jaglion, SEP sesam uses Resilient Change Tracking (RCT) by default for Hyper-V backups on Windows Server ≥ 2016 (Hyper-V VM ≥ 6.2). Single file restore (VFS mount) is currently only supported for VM Hyper-V backups without RCT option (old approach with VSS snapshots creating ''.avhdx'' files instead of the new Resilient Change Tracking). The new RCT backups have a 'RCT' attribute and the mount option is not shown. For older backups without the 'RCT' attribute, the mount option is available.
::When creating a new migration task in German language version of the GUI, the option '''Nach erfolgreicher Migration löschen''' is by default set to '''An (Mit nächstem 'Bereinigen' löschen)'''. This option can be found in Migration Task window, accessed from ''Main Selection -> Tasks -> Migration Tasks'' by clicking ''New Migration Task'' (for more information see [[Special:MyLanguage/Creating_a_Migration_Task|Creating a Migration Task]]). Note that in the English version, this option is set to ''Off''.
:::'''Workaround:''' When restoring a Hyper-V RCT backup, perform a regular VM restore of the virtual machine as described in [[Special:MyLanguage/4_4_3_Beefalo:Hyper-V_Restore#VM_restore|Restoring a Hyper-V virtual machine]].  
:::'''Workaround:''' When creating a new migration task, review and modify the setting for this option as required.
:::'''Resolution:''' SEP development is working on a single file restore via mount for Hyper-V RTC backups and will implement it as soon as possible.  
:::'''Resolution:''' SEP is working on this issue and will provide a fix as soon as possible.


;SEP sesam v. 5.0.0.3-5.0.0.9 Hyper-V restore fails, if the data store path from the original VM does not exist on the target server
;SEP sesam v. 5.0.0.x BSR Pro fails to update during silent SEP sesam update
:* 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.
::BSR Pro is not updated when you update a SEP sesam Server, RDS or Client component including BSR in silent mode, e.g. via the powershell command line.
:::'''Resolution:''' SEP is working on this issue and will provide a fix as soon as possible.  
::BSR Pro is installed with own MSI installer and cannot be included automatically in a chained installation. During a manual update using the installer EXE, or during the remote update installation via the SEP sesam GUI (<tt>sm_update_client</tt>) BSR Pro will be updated normally. During the silent installation the update of BSR Pro is not performed.
:::'''Workaround:''' Start a regular GUI-based update or use the SEP sesam GUI (<tt>sm_update_client</tt>), which includes updated version of BSR Pro.


-----
-----
<!-- ====''GUI issues''====
------->
==={{anchor|minor}}Severity: MINOR===
==={{anchor|minor}}Severity: MINOR===


;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.1.0 – SEP sesam Wiki documentation update in progress
:*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.
:Major restructuring and rewriting of SEP sesam Wiki is in progress. The articles are in process of being moved and updated. Some links may be broken, some articles may not be available anymore, and some articles do not yet reflect current state.
:::'''Workaround:''' We recommend to first install Java version 11 or higher before you start the SEP sesam installation.  
:::'''Resolution:''' SEP is working on this issue and will bring the documention up to date as soon as possible.
 
}}</onlyinclude>
 
=== {{anchor|unsupported}}Discontinued systems ===
 
{{note|With Apollon release SEP sesam no longer supports Java JRE 1.8 release. During SEP sesam Server update, Java update to version 11 or higher is enforced. On RDS component, you have to upgrade Java to version 11 or higher manually.
If you are using Si3 or Si3-NG deduplication store, which require Java, update the Java version before updating the RDS component, otherwise Si3 might not start.}}


;SEP sesam v. 5.0.0.x – Proxmox VE backup does not work with the client name as plain IP address
In SEP sesam ''Apollon'', SEP announced that it would no longer support:
:*If the node added to the SEP sesam environment is not set up correctly and an IP address is used as the client name instead of the client's hostname matching the hostname returned by the Proxmox server, the backup fails.
*RHEL 7
:::'''Resolution:''' This problem can only be solved by correctly configuring the Proxmox clients in the SEP sesam environment. For more details on configuring the client name correctly, see [[Special:MyLanguage/4_4_3_Beefalo:Proxmox_VE_Backup#client_name|Proxmox VE Backup: Adding the Proxmox server (and nodes) to the SEP sesam environment]].
*Debian 9 (Stretch)
*Windows 2012 R2


;SEP sesam v. 5.0.0.x – Kopano backup containing non-ASCII characters fails to create index, but backup is marked as successful
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.
:*A Kopano backup containing non-ASCII characters results in the error ''UnicodeEncodeError: 'ascii' codec can't encode character...'' Consequently, the mail subject index cannot be created, but the backup is marked as successful.
:::'''Resolution:''' The index problem can only be fixed by creating the correct locale:
:::<code>#vi /etc/locale.gen</code> and then enable <code>de_DE.UTF-8 UTF-8</code>
:::<code>#locale-gen</code>


;SEP sesam v. 4.4.3.86–5.0.0.x – ''Initial Seeding'' functionality temporarily removed
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.
:*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>
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 340: Line 206:
===Obsolete SEP sesam Server versions===
===Obsolete SEP sesam Server versions===
The following versions of SEP sesam are no longer supported:
The following versions of SEP sesam are no longer supported:
*SEP sesam [[SEP_sesam_Release_Versions|4.4.3 Beefalo V2]] -> August 2023
*SEP sesam [[SEP_sesam_Release_Versions|4.4.3 Beefalo]] -> August 2022
*SEP sesam [[SEP_sesam_Release_Versions|4.4.3 Grolar]] -> October 2021
*SEP sesam [[SEP_sesam_Release_Versions|4.4.3 Grolar]] -> October 2021
*SEP sesam [[SEP_sesam_Release_Versions|4.4.3 Tigon V2]] -> December 2020
*SEP sesam [[SEP_sesam_Release_Versions|4.4.3 Tigon V2]] -> December 2020
*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 ==
*[[Change report 5.0.0.9 Jaglion V2]]
*[[Change report 5.1.0 Apollon]]
*[[Change report Jaglion V2 Service Packs]]
<!-- *[[Change report Apollon Service Packs]] -->
 


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

Revision as of 08:53, 5 June 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

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.

Performing virus scan with IKARUS scan.server

SEP sesam introduces a new feature that enables a virus scan on selected files before initiating a Single File Restore. By performing a virus scan with the latest Virus Database (VDB) before starting the restore, SEP sesam effectively prevents restoring any known infections that might have gone undetected during the backup process.

Fighting ransomware with SEP sesam Immutable Storage – SiS

SEP Immutable Storage or SiS is a file storage feature resistant to ransomware attacks, based on Si3 NG on Linux. Even with full admin access to the SEP sesam backup server, attackers cannot delete, modify, or encrypt data stored on SiS. The idea behind SEP sesam Immutable Storage is that stored data remains completely static in its original and unchanged form throughout its lifetime. This means that businesses can quickly recover from a ransomware attack, even if they have lost access to their data and servers, by using stored data copies that have remained unchanged and intact to restore the entire operating environment.

SEP Customer Experience Program (SCE)

SEP Customer Experience (SCE) collects technical information from participating customers. This data is used to improve SEP sesam, both for existing needs and for future development.

Hyper-V Resilient Change Tracking (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.

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.

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

Saving backup metadata on tape

Saving backup metadata on tape allows backup administrators to store critical information about a backup on the tape, which can be used for restoring data in the event of a disaster or data loss. Backup metadata information includes important details about the backup and can be used to recreate DB entries that are required for FULL restore.

To enable saving the meta file archive (LIS/SGM/DB entries) on tape by default, set the global variable gv_conf_no_info_upload_sms to 0.

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

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.5 Apollon:
SEP sesam since v. 5.1.0.2 - Hyper-V RCT INCR may run with wrong reference if previous Hyper-V backup failed or was aborted
Hyper-V may exhibit a backup issue where the timestamp for RCT backups may be set incorrectly if backup failed or was aborted, which can lead to an invalid backup chain. In such cases the subsequent INCR backups may reference the failed backup instead of the last successful backup.
Workaround: Start a FULL backup in case a FULL or INCR backup did not finish sucessfully. This will ensure that the backup timestamp is correctly set, preventing any further issues in the backup chain. It is also recommended to regularly test the validity of backups and monitor backup logs for any errors or anomalies.
Resolution: Fixed with 5.1.0.5.
  • Hyper-V restore and Hyper-V Mount and SFR restore
  • Restore of a sparse file bigger than 4GB gets stuck but destination file becomes larger and larger
  • (#32096) Update of client via Sesam server may fail because sub-processes are still running
  • (#32100) Web UI: Write correct target path for NDMP restore to original location
  • (#32035) NDMP generation restore of migrated saveset with one selected directory failed due to empty SEL file for FULL saveset
  • (#32035) NDMP restore failed because of spaces in name of the selected file or directory
  • (#32091) Nutanix VM mount failed

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.1.0.5 - (#32381) PostgreSQL startup failure after changing SEP sesam service user (Windows only)
By default, the SEP sesam service starts under the SYSTEM user account. At installation, postgreSQL database is set to start under this account. However, if the user name of the SEP sesam service is changed from SYSTEM (for example, to Administrator) after installation, PostgreSQL encounters startup issues and fails to start.
Changing the user name of the SEP sesam service affects the ownership and permissions of the PostgreSQL data directory, typically the db_pg folder. As a result, PostgreSQL is unable to access the necessary files and resources, causing failure to start up.
Solution: You can revert to the previous SEP sesam service account (SYSTEM), or change the ownership and permissions of the PostgreSQL data directory (db_pg folder) to the used SEP sesam service account user. In this case make sure you change ownership and permissions for subfolders and files as well (use Windows Explorer option Replace owner on subcontainers and objects). PostgreSQL regains the necessary access rights, enabling it to start successfully. Note that this workaround modifies the folder's ownership and permissions, so make sure that the used user account has appropriate privileges for managing the SEP sesam database.
SEP sesam v. 5.1.0.5 - (#32359) The GUI options for handling running events during NEWDAY are not functioning as intended
The functions of the two options for handling running events during NEWDAY have been inadvertently swapped, causing them to perform the opposite of their expected behavior. These two options can be found in Newday event Properties window, accessed from Main Selection -> Scheduling -> Schedules by double-clicking the Newday event (for more information see Newday Event).
Workaround: To achieve the desired behavior, select the opposite option of your intended action. For instance, if you want Newday to continue all running activities, select the option Cancel all running activities (and vice versa).
Resolution: SEP is working on this issue and will provide a fix as soon as possible.
SEP sesam v. 5.1.0.5 - (#32360) On the German GUI Client the default setting for deleting savesets after migration is set to ON
When creating a new migration task in German language version of the GUI, the option Nach erfolgreicher Migration löschen is by default set to An (Mit nächstem 'Bereinigen' löschen). This option can be found in Migration Task window, accessed from Main Selection -> Tasks -> Migration Tasks by clicking New Migration Task (for more information see Creating a Migration Task). Note that in the English version, this option is set to Off.
Workaround: When creating a new migration task, review and modify the setting for this option as required.
Resolution: SEP is working on this issue and will provide a fix as soon as possible.
SEP sesam v. 5.0.0.x – BSR Pro fails to update during silent SEP sesam update
BSR Pro is not updated when you update a SEP sesam Server, RDS or Client component including BSR in silent mode, e.g. via the powershell command line.
BSR Pro is installed with own MSI installer and cannot be included automatically in a chained installation. During a manual update using the installer EXE, or during the remote update installation via the SEP sesam GUI (sm_update_client) BSR Pro will be updated normally. During the silent installation the update of BSR Pro is not performed.
Workaround: Start a regular GUI-based update or use the SEP sesam GUI (sm_update_client), which includes updated version of BSR Pro.

Severity: MINOR

SEP sesam v. 5.1.0 – SEP sesam Wiki documentation update in progress
Major restructuring and rewriting of SEP sesam Wiki is in progress. The articles are in process of being moved and updated. Some links may be broken, some articles may not be available anymore, and some articles do not yet reflect current state.
Resolution: SEP is working on this issue and will bring the documention up to date as soon as possible.


Discontinued systems

Information sign.png Note
With Apollon release SEP sesam no longer supports Java JRE 1.8 release. During SEP sesam Server update, Java update to version 11 or higher is enforced. On RDS component, you have to upgrade Java to version 11 or higher manually.

If you are using Si3 or Si3-NG deduplication store, which require Java, update the Java version before updating the RDS component, otherwise Si3 might not start.

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

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

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

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

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

End of maintenance and support

Obsolete SEP sesam Server versions

The following versions of SEP sesam are no longer supported:

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

Change reports


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.