Release Notes 4.4.3 Beefalo

This is not the latest version of SEP sesam documentation and, as such, does not provide information on features introduced in the latest release. For more information on SEP sesam releases, see SEP sesam Release Versions. For the latest documentation, check latest Release Notes.

What's new in SEP sesam 4.4.3 Beefalo

Next release

This is not the latest version of SEP sesam Release Notes. To check which is the latest version available, see SEP sesam Release Versions.

SEP sesam new release, solid and reliable Beefalo, provides exciting new features and enhancements to many of the existing modules that help you improve and manage your SEP sesam environment.

Features at glance

New data store type is available for Hewlett Packard Enterprise (HPE) StoreOnce Catalyst Stores which are used as backup storage. SEP sesam integrates with StoreOnce Catalyst client to provide high-performance backup and restore.

SEP sesam expands support for virtualization environments and introduces new features for the already supported ones:

New: Proxmox VE backup and restore
Enhanced backup and restore for existing virtualization platforms, e.g., VMware sandbox restore is supported to easily verify backup integrity
Single file restore from INCR backups is introduced for Hyper-V
Single file restore is supported for Citrix XenServer backups

DIFF and INCR backup level for IBM Domino (previously Lotus Domino) has changed compared to previous SEP sesam versions; DIFF now saves all IBM Domino files that have been changed from the last FULL or DIFF backup including new DBIID, and INCR saves all relevant transaction logs, all new IBM Domino files and IBM Domino files with new DBIID.

A repository with signed RPM packages is provided to ease the installation on SLES and Red Hat.

Configuration of LDAP/AD authentication has been enhanced.

EOL behavior is improved compared to the previous versions and now allows for extending retention period of the referenced savesets on other media pools (not only on the target media pool) thus increasing retention period of migrated savesets only.

In order to improve usability, SEP sesam GUI is redesigned to be more user-friendly and more appealing without significantly changing the interface logic and affecting existing functions.

To make sure you are running the latest SEP sesam version, SEP sesam GUI Server can be automatically updated when a new version is available in the SEP Download Center by selecting the Download and install updates automatically in the newly introduced Install/Update configuration options.
The new GUI has been enhanced with new features, e.g., finding a specific content item (task, client, data store ...) is made easy with integrated filtering.

With the new Oracle Java licensing and release strategy, SEP sesam introduces support for OpenJDK LTS (long term support) distributions that are available free of charge. With the relevant Java version, now also HiDPI displays are supported.

New Encryption support matrix provides detailed overview of supported encryption types with Beefalo.

New supported systems

SEP sesam Server 4.4.3 Beefalo now also supports the following systems:

RHEL 8
Debian 10 Buster
Windows Server 2019
Oracle Linux 8
Hyper-V Server 2019
Microsoft Exchange 2019

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

Discontinued systems

	Note
	In SEP sesam Beefalo, SEP announced that it would no longer support SEP sesam Server on Windows Server 2008 R2. This desupport has been revoked. SEP sesam Server packages 4.4.3.70–72 and SP2 can be normally installed on Windows Server 2008 R2.

As of v. 4.4.3 Beefalo, the following systems are no longer supported for update:

JIRA
RHEL 6
SLES 11 (changed for Beefalo V2)
Debian Jessie
Windows 7
All Windows operating systems with x86 architecture (32-bit)

	Note
	Currently it is not possible to upgrade IBM Domino (Lotus Notes) on Linux to version 4.4.3.70 Beefalo. Last version with IBM Domino support is 4.4.3.64 SLES 11. See Release Notes 4.4.3 Beefalo V2

See also Unsupported OS. For a complete list of supported SEP sesam Clients, see SEP sesam Support Matrix.

SEP sesam Server requirements

Java 11 or OpenJDK 11 LTS: For details, see Java Compatibility Matrix.

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

Installation and upgrades

SEP sesam 4.4.3 Beefalo beta 1 was released on 17^th of Jun, 2019. Direct upgrade for versions 4.4.3.X to version 4.4.3 Beefalo is supported.

Latest released versions are:

SEP sesam 4.4.3.72 Linux – early released: 9^th of September, 2019.
SEP sesam 4.4.3.72 Windows – early released: 9^th of September, 2019.

Windows specific

The 4.4.3 Beefalo installation package on Windows also includes:

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 Automatic Updates and Automatic Installation on Windows.

Newer release

Release notes for SEP sesam 4.4.3 Beefalo V2

Previous release

Release notes for SEP sesam 4.4.3 Grolar

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.

4.4.3 Beefalo known issues:

SEP sesam v. 4.4.3.42–72 – (Windows) A data block is not written to tape when EOM is reached together with the segment size, thus making a restore of data referencing this block impossible

(Applies only to Windows) When backing up to tape, a data block is not written to tape when the segment size is reached at EOM, therefore a restore of data referencing this block is not possible. While a Path Archive can still be restored until EOM is reached, a complete restore or migration will fail.

Resolution: Fixed with the patch for Beefalo V2, contact SEP sesam support at support@sep.de for assistance.

SEP sesam v. 4.4.3.70-72 – Backing up Citrix Hypervisor 8.1 might result in error "Unable to create a snapshot [['MESSAGE_REMOVED']]"

As creating quiesced snapshots is no longer supported in Citrix Hypervisor ≥ 8.1 and in the version ≥ 9.0.x.x drivers, running hot backups in combination with the COPY backup level results in the above error.

Workaround 1: The SEP sesam version 4.4.3.64 Grolar is not affected by this problem. It is still possible to use a SEP sesam Client as data mover if the SEP sesam software hasn't been upgraded to the Beefalo release yet.

Workaround 2: If you can afford the downtime of your affected virtual machines, you can change the settings from hot backup to cold backup as no snapshot creation is needed in this case.

Workaround 3: If your license allows the use of the CBT feature in Citrix Hypervisor, back up your virtual machines with the FULL/DIFF/INCR backup level instead of COPY.

SEP sesam v. 4.4.3.70–72 – VMware VM backups might fail due to a new vCenter Server version: 6.7 Update 3b

Due to a change in the VMware latest vCenter 6.7 Update 3b (6.7.0.42000), no VM backups can be performed by SEP sesam. This applies to all SEP sesam versions.

Workaround: Add the the exclude keyword ALL to the exclude list of the affected vmware VM task. If one or more VMDKs are already excluded, add the value separated by a comma (without spaces) at the end, for example: [vmstore] myVM/myVM_1.vmdk,ALL. For details, see VMware Backup - Creating a backup task.

Resolution: Fixed with Beefalo V2 4.4.3.84.

SEP sesam v. 4.4.3.70–72 – When several paths are specified for Linux or Windows path backup, only the last path is backed up

Linux and Windows path backups may incorrectly back up only the last backup source, if a SEP sesam Server v. 4.4.3.70–72 Beefalo is used together with a SEP sesam Client v. 4.4.3.64 Grolar and at least two backup sources are defined for a path backup. For example, if there are more sources specified, such as /var/www, /root, /etc, only the last backup source /etc is backed up, but the backup finished successfully without any errors.

Resolution: If not yet done, upgrade the SEP sesam Server to version 4.4.3.72 and then install a service pack, available under http://download.sep.de/servicepacks/4.4.3/4.4.3.72.

SEP sesam v. 4.4.3.70–72 – Migration from saveset on sayTEC-sayFUSE leads to error 'Checksum of saveset copy does not match'

In case of VMware VMDK saveset, migration from tape (sayFUSE) to tape (sayFUSE) ends with checksum error 'Checksum of saveset copy does not match'.

Resolution: If not yet done, upgrade the SEP sesam Server to version 4.4.3.72 and then install a service pack, available under http://download.sep.de/servicepacks/4.4.3/4.4.3.72.

SEP sesam v. 4.4.3.72 – BSR restore on Windows from a bootable image does not work when the boot image is created on the GUI installation on D:

Restoring BSR on Windows from a bootable image does not work, when the BSR ISO boot image is created on the GUI installation installed on the D: volume.

Workaround: Install BSR Pro to the system volume C: or use the SEP sesam Server installation package for GUI installation, see SEP sesam Quick Install Guide. SEP is working on this issue and will provide a solution as soon as possible.

SEP sesam v. 4.4.3.70–72 – Linux BSR backup fails if the task type is selected manually

If you select the Linux BSR task type manually from the drop-down list when creating a backup task for Linux BSR backup, the backup will fail. However, if you select the Linux BSR backup source by browsing and let the task type to be set automatically, the backup will work.

Resolution: If not yet done, upgrade the SEP sesam Server to version 4.4.3.72 and then install a service pack, available under http://download.sep.de/servicepacks/4.4.3/4.4.3.72.

SEP sesam v. 4.4.3.70–72 – Si3 service does not start if key Log_Levels is missing in stpd.ini

Si3 service fails to start after update because the command sm_dedup_interface exits with error message "STATUS=ERROR MSG=No such node (STPD_Logging.Log_Levels)"
Backups on Datastore fail with error message "Error: Could not access data store. No such node (STPD_Logging.Log_Levels) No such node (STPD_Logging.Log_Levels)"

Workaround: Locate the stpd.ini file (<SESAM_ROOT>/var/ini/stpd.ini) on the SEP sesam Server/RDS, open it using a text editor and set the log setting Log_Levels=0 1 2 under [STPD_Logging]. Execute the command sm_config_drives afterwards to regenerate the drive configuration.

Resolution: Upgrade the SEP sesam Server to version 4.4.3.72 and then install a service pack, available under http://download.sep.de/servicepacks/4.4.3/4.4.3.72.

SEP sesam v. 4.4.3.72 – Hyper-V single file restore only available in UI mode Expert

Single file restore for Hyper-V can only be used in the Expert UI mode. In addition, the single file restore function is only available after a SEP sesam Server update and not after a new installation.

Workaround: To enable single file restore for Hyper-V, go to the Defaults menu and in the tab General select the Expert UI mode. Then, if the SEP sesam Server has been newly installed, update it using the same package as used for the installation. After the update, you will be able to use Hyper-V single file restore.

SEP sesam v. ≤ 4.4.3.71 – SQL injection vulnerability in SEP sesam versions ≤ 4.4.3.71

The SQL injection vulnerability can pose a major security threat to SEP sesam as it can completely paralyze SEP sesam operations.