The support matrix lists all configurations and versions currently available by SEP sesam and SEP IT-Save. SEP sesam automatically detects the hardware configuration of your environment. Note that SEP sesam only recognizes storage devices that are known to or listed by the operating system, such as OS where the Master Server/Remote Device Server will be installed. For details, see Storage Hardware page.
See also the new Release Notes v. 5.1.0 Apollon.
Note
SEP sesam Client versions that are last available for a platform, are still supported.
SEP sesam Backup Servers and Clients
It is recommended to upgrade the SEP sesam Server and Client components to the latest version as part of the regular upgrade process (check the list of SEP sesam release versions). This ensures the highest possible protection of the SEP sesam Clients. Customers with a valid license are entitled to a free SEP sesam upgrade for each new version until the end of the license term. Before upgrading your SEP sesam environment, check the support matrix.
The SEP sesam Micro Focus (Novell) OES module is already a part of the SLES 12 and SLES 15 packages. It is not required to download and install any separate sesam-novell-client package.
Noteb
OES 11 SP2 eDirectory (NetIQ Directory) has been available by SEP sesam since version 4.2.2-40 and with SEP Sesam Novell Client 4.2.2-35. For additional information, see OES11Sp2 eDir.
Notec
For Sesam Server installations, SLES12 Service Pack 5 is required.
Windows Server 2022 support (without BSR Windows Disaster Recovery) was introduced with version 5.0.0 Jaglion, while Windows 11 support (without BSR Windows Disaster Recovery) was introduced with version 5.0.0 Jaglion V2. BSR Windows Disaster Recovery is fully supported for both, Windows Server 2022 and Windows 11, with 5.1.0 Apollon.
Noteb
Windows Server 2019 support was introduced with version 4.4.3 Grolar, but was recognized as Windows Server 2016. With version 5.0, Windows Server 2019 is normally detected.
Notec
Microsoft Data Deduplication Enabled Volumes are supported since version 4.4.
Noted
The only supported edition is the Windows SBS Standard Edition. The Essentials Edition is not supported!
As of version 5.0.0.x Jaglion, SEP sesam supports S3 as a generic interface based on the new deduplication store Si3 NG.
Some S3 targets are already supported, others have been looked at in more detail (see list below) and are currently being tested.
SEP sesam Si3 NG can be used with various S3-compatible cloud implementations. The configuration and management of Si3 NG in an S3-compatible cloud implementation is similar to the example shown in Backup to S3 Cloud Storage. Note, however, that only some S3-compatible cloud environments have already been validated by SEP, while others may not work in some cases. You are solely responsible for using SEP sesam in a non-S3 compatible cloud environment and agree that SEP shall not be responsible for it.
4.4.3.64 Grolar only if UEFI BIOS is used. Version 4.4.3.64 is the last version with integrated REAR 2.4. Later REAR versions (≥ REAR 2.5) no longer support SLES 11 (with UEFI).
To continue using BSR SLES 11, you should not upgrade to a later version of SEP sesam.
SLES 10 ≥ SP2
i386, x86-64
RHEL 9
x86-64
5.1
RHEL 8
x86-64
5.0 Supported up to Service Pack 3 (RHEL 8.3)
RHEL 7
x86-64, Power*
RHEL 6
i386, x86-64, Power*
CentOS 8
i386, x86-64
5.1
CentOS 6
i386, x86-64
Debian 12 Bookworm
x86-64
5.1
Debian 11 Bullseye
x86-64
5.1
Debian 10 Buster
x86-64
5.0
Debian 8 Jessie
i386, x86-64
Debian 7 Wheezy
i386, x86-64
Note
Systems that use UEFI as a boot loader are currently only supported on SLES
On SLES creating a UEFI-bootable recovery image is only possible with additional packages. For details, see UEFI.
Virtual machines running on XEN cannot be backed up with SEP sesam BSR solution
The resulting ISO image containing a paravirtualized kernel is not bootable. Please use the SEP Sesam Citrix XEN module for Citrix XEN Server to create a consistent and relevant backup for a disaster recovery.
Power PC
For PowerPC and Linux One Systems, contact SEP sesam sales.
These architectures may not work out of the box or require special configuration. Consultation for these systems is available according to the price list.
vSphere 7.0 with VDDK 6.5.2 is not officially supported by VMware. However, some customers are backing up vSphere 7.0 with Beefalo version 2, which contains VDDK 6.5.2. Although this version of VDDK is not officially supported for vSphere 7.0, it appears to work. Note that any issues related to the use of this officially unsupported version are the responsibility of the user and not SEP sesam or VMware.
As of VMware vSphere 5, backup with SEP sesam is only supported with a licensed ESXi hypervisor. Backup of ESXi 5.5 hypervisors is supported as of SEP sesam version 4.2.2.40.
Noteb
The VMware policy concerning backward and forward compatibility is for VDDK to support N-2 and N+1 releases (except for new features).
For example,
VDDK 7.0 (and all its update releases) supports vSphere 6.0, 6.5 and 8.0,
VDDK 6.0 (and all its update releases) supports vSphere 5.1, 5.5, and 6.5.
Notec
VDDK 6.5.2 was tested by VMware with the following operating systems to perform proxy backup:
Windows Server 2008 R2
Windows Server 2012 and 2012 R2
Windows Server 2016
Windows 10
Red Hat Enterprise Linux; RHEL 6.7, 6.8, 7.2 and 7.3
SUSE Linux Enterprise Server; SLES 11 SP4 and SLES 12 SP1
Noted
VDDK 7.0.3 supports the following operating systems:
Windows Server 2019
Windows Server 2016, including versions 1709 and 1803
Windows Server 2012 and 2012 R2
Red Hat Enterprise Linux RHEL 7.7, 8.0 and 8.3
CentOS 7.7 and 8.3
SUSE Linux Enterprise Server SLES 12 SP5 and 15 SP1
VSS and quiesced snapshots of Windows VMs are only supported in Citrix Hypervisor 8.0 and earlier; they have been removed in Citrix Hypervisor ≥ 8.1 and in the version ≥ 9.0.x.x drivers. For more information, see Citrix Hypervisor 8.1 Deprecations and removals.
Noteb
To continue using the quiesced snapshot feature with Windows VMs hosted on Citrix Hypervisor 8.0 and earlier, keep your current 8.2.x.x version of the Windows I/O drivers and do not update to the 9.0.x.x drivers.
Notec
Citrix Hypervisor (XenServer) Changed Block Tracking (CBT) is required for single file restore.
As XCP-ng is based on Citrix Hypervisor that has removed support for VSS and quiesced snapshots in Citrix Hypervisor ≥ 8.1 and in version ≥ 9.0.x.x drivers, the following applies: To continue using the quiesced snapshot feature with Windows VMs hosted on XCP-ng 8.0 and earlier, keep your current 8.2.x.x version of the Windows I/O drivers and do not update to the 9.0.x.x drivers. For more information, see XCP ng 8.1 Release Notes and Citrix Hypervisor 8.1 Deprecations and removals.
The RHV module supports the oVirt framework for virtualization that is also used by Oracle Linux Virtualization Manager. For details, see the OLVM documentation.
With Oracle databases v. ≥ 12c, multitenant architecture is supported to enable backup and restore of multitenant container databases (CDBs) and pluggable databases (PDBs) in a similar way to traditional Oracle databases (non-CDBs). For details, see Backing up CDBs and PDBs.
All components for setting up the SAP Adaptive Server Enterprise (ASE) 16.0 (formerly SAP Sybase ASE) extension are already included in the SEP sesam installation packages.
Support is provided by the libsepsybasebr library, which is based on the library for SAP ASE.
More detailed information on the SAP IQ module is available on request via contact SEP sesam sales.
All components for setting up the SAP HANA extension are already included in the SEP sesam installation packages. For more information on certified integration with SAP applications, see SAP solutions.
All components for setting up the SAP NetWeaver extension are already included in the SEP sesam installation packages. For more information on certified integration with SAP applications, see SAP solutions.
All required components for IBM DB2 may already be included in the SEP sesam Client package. If not, you can download the extension from the SEP Download Center.
All required components are included in the SEP sesam Client package. Note that the SEP sesam installation on RHEL changes the permissions of /var/run/postgresql to grant PostgreSQL access rights to the SEP sesam user.
The SQLMGR.DLL is a .NET assembly build with the Any CPU platform and can run on both x64 and x86 architectures.
Single item restore (site, document, etc.) is supported for: SharePoint 2007, 2010, 2013 and 2016 in combination with SQL Server 2005, 2008, 2008 R2, 2012 SP1 and 2014.
All required components for HCL Domino Server (formerly IBM Domino/Lotus Domino) may already be included in the SEP sesam Client package. If not, you can download the extension from the SEP Download Center.
The following table lists the last available version of SEP sesam Server or RDS components for specified operating systems. You can continue using the last available version of SEP sesam on these operating systems, but SEP AG no longer provides updates or fixes for the specified versions.
For SEP sesam Client versions, backward compatibility is maintained and the last available versions for a platform are continuously supported. On older platforms you can use older versions of SEP sesam Client component, but it is recommended to combine such clients with the latest versions of SEP sesam Server and RDS components.
SEP announced that it would no longer support SLES 11 SP2, SP3, SP4 with SEP sesam Beefalo, but has re-established support for Beefalo V2, where all SEP sesam Beefalo V2 packages (Server, Client, etc.) can be used. However, Beefalo V2 is the last available SEP sesam release for SLES 11 SP2, SP3, SP4 .
SEP announced that it would no longer support SEP sesam Server on Windows Server 2008 R2 with SEP sesam Beefalo, but has re-established this support already in Beefalo. This actually means that the last available SEP sesam Server release for Windows Server 2008 R2 is Beefalo V2.
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.
