Release Notes 5.1.0 Apollon: Difference between revisions
(First version) |
|||
Line 1: | Line 1: | ||
__NOTOC__ | __NOTOC__ | ||
<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> | |||
<div class="boilerplate metadata" id="Additional resources" style="background-color: #f0f0f0; color:#636f73; border: 1px ridge #cdd3db; margin: 0.5em; padding: 0.5em; | |||
{|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: | | 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|Improvements]] | ||
*[[#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]] | ||
*[[#end|End of maintenance and support]] | *[[#end|End of maintenance and support]] | ||
*[[#changes|Change reports]] | *[[#changes|Change reports]] | ||
</div></div> | </div></div> | ||
----- | |||
=== {{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). | ||
===== | ===== [[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. | |||
=== | ===== [[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. | |||
===== [[Special:MyLanguage/5_1_0:Configuring_a_Media_Pool|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. | |||
===== [[Special:MyLanguage/5_1_0:Creating_a_Backup_Event|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). | |||
====[[Special:MyLanguage/5_1_0:Creating a Command Event|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. | |||
=== {{anchor| | === {{anchor|enhancements}}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''': <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. | |||
;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]]. | |||
;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: | ||
:SEP sesam | *'''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. | |||
; | ;{{anchor|ui}}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. | |||
=== {{anchor|new_systems}}New supported systems and integrations=== | |||
{{note|On RHEL 8.6 update the VDDK to version 7.0.3, otherwise you might experience problems with vSphere restore.}} | |||
; | ;[[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]]). | |||
;[[SEP_sesam_OS_and_Database_Support_Matrix#Windows|Microsoft Windows Server 2022]] | |||
: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_OS_and_Database_Support_Matrix#Proxmox_VE|Proxmox 7.3]] | |||
'' | :Introduced with ''Apollon'' in SEP sesam VM extensions | ||
;[[SEP_sesam_OS_and_Database_Support_Matrix#VMware|vSphere 8]] | |||
:Introduced with ''Apollon'' in SEP sesam VM extensions | |||
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|fixes_v11}}Fixes: SEP sesam Server 5.1.0 Apollon == | == {{anchor|fixes_v11}}Fixes: SEP sesam Server 5.1.0 Apollon == | ||
{{Box Hint|Fixed with [http://download.sep.de/ 5.1.0 ''Apollon'']| | |||
{{Box Hint|Fixed with [http://download.sep.de | ;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. | ||
; | |||
}} | }} | ||
== {{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. | {{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=== | ||
;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. | |||
<!-- replace | |||
:::''' | ;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. --> | ||
----- | ----- | ||
==={{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 | ||
For the list of all SEP sesam versions see [[SEP_sesam_Release_Versions|SEP sesam Release Versions]]. | |||
== {{anchor|changes}}Change reports == | == {{anchor|changes}}Change reports == | ||
Line 359: | Line 207: | ||
*[[Change report Jaglion V2 Service Packs]] | *[[Change report Jaglion V2 Service Packs]] | ||
{{Copyright SEP AG|en}} |
Revision as of 14:58, 16 March 2023
Download for Linux: SEP sesam 5.1.0 Linux | Download for Windows: SEP sesam 5.1.0 Windows |
See Installation on Linux | See Installation on Windows |
Note | |
You always have to update the SEP sesam Server first before updating the RDS and client components. For more information on the SEP sesam software updates, see Updating SEP sesam. |
What's new
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 bysm_mount
andsm_data_store mount_saveset
is replaced bysm_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
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: |
|
Known issues and limitations
Note | |
Antivirus programs may disrupt network communication and cause SEP sesam processes, such as backup and replication, to fail. One program that is known to cause SEP sesam processes to terminate is Sophos Firewall with IPS (Intrusion Prevention System) enabled. Make sure that there are no antivirus, firewall, IDS or IPS programs preventing interaction with SEP sesam. |
5.1.0.x Apollon known issues: |
Severity: MAJORSeverity: NORMAL
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:
- SEP sesam 4.4.3 Grolar -> October 2021
- SEP sesam 4.4.3 Tigon V2 -> December 2020
- SEP sesam 4.4.3 Tigon -> September 2020
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.