Release Notes 4.4.3 Beefalo V2
Copyright © SEP AG 1999-2021. 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.
- 1 What's new in SEP sesam 4.4.3 Beefalo V2
- 2 Known issues and limitations
- 3 Enhancements and changes
- 3.1 Single file restore from all supported hypervisors except Proxmox
- 3.2 Extended Catalyst integration
- 3.3 MS SQL AlwaysOn Availability Groups
- 3.4 SAP HANA housekeeping
- 3.5 SAP HANA multistreaming data backups (v. 126.96.36.199)
- 3.6 VMware sandbox restore
- 3.7 Redesigned SEP sesam Dashboard and Restore Assistant
- 3.8 RHV support for oVirt-based platforms
- 3.9 GUI enhancements
- 3.10 Installation improvements (188.8.131.52)
- 3.11 Technical improvements
- 3.12 Managing failed backups (EOL) has changed
- 3.13 Increased exclude pattern range
- 4 End of maintenance and support
- 5 Major fixes and changes
- 6 See also
What's new in SEP sesam 4.4.3 Beefalo V2
SEP sesam Beefalo V2 brings new remarkable features that help improve managing and protecting data in your SEP sesam environment. As Beefalo V2 is regularly enhanced with new service packs that include various fixes, make sure that you use the latest Beefalo V2 version. (See SEP sesam Release Versions.)
SEP sesam now supports single file restore for all hypervisors except Proxmox.
SEP sesam Catalyst integration for HPE StoreOnce is extended with Catalyst copy, HPE Cloud Bank Storage as a Catalyst copy target, and application-side deduplication.
SEP sesam 4.4.3 Beefalo V2 introduces support for the VMware sandbox restore via its enhanced (web) Restore Assistant.
Additionally, SEP sesam web Dashboard and Restore Assistant have been completely redesigned to provide an intuitive overview of the SEP sesam environment and a simple wizard that walks you through the restore process.
GUI enhancements include a new Install/Update tab (in the Configuration -> Defaults) that eases the update process and simplifies the deployment of clients. Schedules provide a more intuitive and responsive calendar.
Technical improvements include the possibility to set the device block size for LTO Ultrium tape drives.
SEP sesam RHV module also provides support for oVirt-based platforms within OLVM (Oracle Linux Virtualization Manager) in the same way as for RHV environments.
- Managing failed backups (EOL) has changed. SEP sesam now keeps failed backups according to the media pool retention time (previously: 3 days), but allows you to customize your backup retention policy by using retention-related keys.
- The exclude pattern range has been increased for SEP internal exclude patterns.
New in version 184.108.40.206
SEP sesam now enables faster export and import of SEP sesam Server databases, improved is license check performance, and increased security with SHA-256 algorithm.
New in version 220.127.116.11
New supported systems
SEP sesam Server 4.4.3 Beefalo V2 now also supports the following:
- OpenNebula 5.10.1 and 6.0 (since version 18.104.22.168)
- Dell EMC Unity NDMP backup client (since version 22.214.171.124)
- Citrix Hypervisor 8.2 (since version 126.96.36.199)
- Ubuntu 20.04 LTS
- SLES 15 up to SP3 with the exception of SEP sesam Server - the latter is not supported for SLES15 SP3. Also not supported with SP3: KVM backup. See also: Unsupported systems.
- oVirt-based platforms within Oracle Linux Virtualization Manager (OLVM).
For a complete list of supported OS and databases, see SEP sesam Support Matrix.
|In SEP sesam Beefalo, SEP announced that it would no longer support:
This desupport has been revoked. SEP sesam Server packages 188.8.131.52–8x Beefalo V2 can be normally installed on Windows Server 2008 R2 and all SEP sesam packages 184.108.40.206-8x Beefalo V2 (Server, Client, etc.) can be used on SLES 11 SP2, SP3, SP4.
|In SEP sesam 220.127.116.11 Beefalo V2, SEP announced that it does not support:
SEP sesam Server requirements
SEP sesam GUI is based on Java and requires a Java Runtime Environment (JRE). The required Java version depends on the SEP sesam version.
|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 V2 was initially released on 11th of May, 2020. A direct upgrade from version 4.4.3.X to version 4.4.3 Beefalo V2 is supported. It is strongly recommended to upgrade to the latest version 18.104.22.168 as it contains a number of fixes and improvements that were not available in the original version of Beefalo V2. For details, see 22.214.171.124 Beefalo V2 Release.
Latest released versions are:
- SEP sesam 126.96.36.199 Linux – released: 5th of July, 2021.
- SEP sesam 188.8.131.52 Windows – released: 5th of July, 2021.
- SEP sesam 184.108.40.206 Linux – released: 3rd of August, 2020.
- SEP sesam 220.127.116.11 Windows – released: 3rd of August, 2020.
In order to meet all required dependencies for the SEP sesam Client packages on SLES 15 SP1 or SP2, it may be required to activate the following package modules prior to SEP sesam installation:
Module-Basesystem Module-Server-Applications Module-Legacy
These modules are part of the installation DVD; in case no online subscription is available, they can be added via:
zypper ar dvd:/Module-Server-Applications DVD-Server zypper ar dvd:/Module-Basesystem DVD-BASE zypper ar dvd:/Module-Legacy DVD-Legacy
The 4.4.3 Beefalo V2 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 Updating SEP sesam and Remote Installation of Windows Clients.
Known issues and limitations
|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 V2 known issues:|
#>sm_main stop node #>cd /opt/sesam #>tar xvzf <hotfix file> #>sm_main start node
Enhancements and changes
Single file restore from all supported hypervisors except Proxmox
SEP sesam allows for single file restore from VM snapshot backups. This feature is now available for all supported hypervisors except Proxmox: VMware, Hyper-V, Citrix XenServer, Red Hat Virtualization and Oracle Linux Virtualization Manager (OLVM) (supported by the RHV module with the only difference that the relevant OLVM objects should be selected instead of RHV), KVM QEMU, OpenNebula.
Extended Catalyst integration
SEP sesam Catalyst integration for HPE StoreOnce is extended with Catalyst copy and HPE Cloud Bank Storage as a Catalyst copy target for replicating your data. HPE Cloud Bank Storage stores data to public or private cloud storage and is ideal for long-term retention and archiving of backups and off-site backup copies for disaster recovery. For details, see HPE StoreOnce Replication.
Additionally, SEP sesam supports all Catalyst data deduplication modes, including application-side deduplication. This is a software-based source-side deduplication that uses the SEP sesam Client (without RDS) to perform the deduplication process and writes the deduplicated data directly to HPE StoreOnce, without using the Media Server. The application-side deduplication is enabled by selecting the HPE StoreOnce Bandwidth Optimized Data Transfer option in the properties of the HPE StoreOnce backup event. For details on available deduplication modes and their requirements, see Catalyst data deduplication modes. For details on selecting the application-side deduplication, see HPE StoreOnce Backup: Option HPE StoreOnce Bandwidth Optimized Data Transfer.
MS SQL AlwaysOn Availability Groups
SEP sesam currently supports backups of MS SQL Server AlwaysOn Availability Groups (AOAG) on the primary replica via the listener. AOAG provide various options for better database availability. For details, see Support for MS SQL AlwaysOn Availability Groups.
SAP HANA housekeeping
Now you can use SAP HANA housekeeping to delete (purge) SEP sesam backups that are no longer needed or can no longer be used for recovery. To perform SAP HANA housekeeping, the relevant commands should be executed on the SAP HANA server. For details, see SAP HANA housekeeping.
SAP HANA multistreaming data backups (v. 18.104.22.168)
As of version 22.214.171.124, SEP sesam supports SAP HANA multistreaming – a special feature supported for large SAP HANA databases. This capability allows you to distribute backup data in parallel to multiple devices of the same pool. It is a part of the SEP sesam backup configuration. SEP sesam provides the necessary stream handling, e.g., setting up multistreaming for a backup task. During a restore, SAP HANA is able to recognize how many channels were used for backup and automatically uses this number of channels for the restore.
For details on multistreaming, see SAP HANA article Multistreaming Data Backups with Third-Party Backup Tools.
VMware sandbox restore
SEP sesam introduces an online VMware sandbox restore which can be performed via a Restore Assistant. SEP sesam sandbox restore for VMware is performed in an isolated environment where you can recover and start one or more virtual machines (VMs). It is useful for checking the VM environment, testing backups, and troubleshooting issues. For details, see VMware Sandbox Restore.
Redesigned SEP sesam Dashboard and Restore Assistant
SEP sesam web Dashboard and Restore Assistant have been completely redesigned to provide a detailed overview and improved monitoring of the SEP sesam environment. Restore Assistant is structured as a simple wizard that guides you through the restore process. It also offers some additional options when compared to GUI, such as VMware sandbox restore (see above). The availability of restore options in the Restore Assistant depends on the used UI mode (basic or advanced). Switching between Restore Assistant, Monitor and Dashboard is easy. For details, see SEP sesam Web UI and Restore Assistant.
RHV support for oVirt-based platforms
SEP sesam RHV module provides support for oVirt-based platforms within Oracle Linux Virtualization Manager (OLVM) in the same way as for RHV environments (with the same options and steps). The only difference is that the relevant OLVM components should be configured instead of RHV. For details, see RHV Backup.
- The sm_update_client command has been extended. Now you can check in the SEP sesam GUI whether an update is available for your clients and select to update automatically or manually. You can update all clients within the location at once or update only the selected client. You can also exclude a specific client from the update or install SEP sesam component(s) on new Windows clients. For details, see Updating SEP sesam and Updating client(s).
- SEP sesam remote automatic installation is a Windows-only feature that enables you to remotely install any SEP sesam package (Client, RDS, etc.) to any Windows system by using SEP sesam GUI. For details, see Remote Installation of Windows Clients.
- SEP sesam calendar became more user-friendly and intuitive. It provides flexible scheduling features to customize how and when your events are processed and how your calendar is set up. For details, see Creating a Custom Calendar.
Installation improvements (126.96.36.199)
As of version 188.8.131.52, SEP sesam introduces installation improvements for bigger installations with many backups by providing enhanced data processing.
- It is possible to change the default write density for tapes to achieve better tape performance by using a new Device Block Size option in the drive properties. You can increase the tape block size if you are using LTO Ultrium tape drives and your backup environment supports larger tape blocks; see Setting device block size.
Managing failed backups (EOL) has changed
How SEP sesam manages failed backups depends on its version. Starting with Beefalo V2, SEP sesam keeps the failed backup(s) according to the media pool retention time together with the last successful backup or migration saveset (in previous versions failed backups were automatically deleted after 3 days). At the same time it introduces retention-related keys that allow you to customize your backup retention policy and control how long the failed backup(s) should be kept. For details, see Customizing retention policy.
Increased exclude pattern range
With Beefalo V2 the exclude pattern range ExcludePattern900 and higher is used for SEP internal exclude patterns. Now the lower numbers should be used in order to define specific exclude patterns. For details, see section Using sm.ini to completely exclude files from backups on the client.
End of maintenance and support
Obsolete SEP sesam Server version
SEP sesam 4.4.3 Tigon V2 -> December 2020
SEP sesam 4.4.3 Tigon V1 -> September 2020
Upcoming end of support
SEP sesam 4.4.3 Grolar -> October 2021
Discontinued SEP sesam Server OS
The following table lists the last supported version of SEP sesam for specified operating systems. You can continue using the last supported version of SEP sesam on these operating systems, but SEP AG no longer provides updates or fixes for the specified versions.
|Operating system||Last supported version||Release||Notes|
|SLES 11 SP2, SP3, SP4||4.4.3.x Beefalo V2, see notes||4.4.3 Beefalo V2||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 supported SEP sesam release for SLES 11 SP2, SP3, SP4 .|
|Windows Server 2008 R2||4.4.3.x Beefalo V2, see notes||4.4.3 Beefalo V2||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 supported SEP sesam Server release for Windows Server 2008 R2 is Beefalo V2.|
|Ubuntu 16.04||184.108.40.206 Beefalo V2||4.4.3 Beefalo V2|
|RHEL 6||220.127.116.11 Grolar||4.4.3 Grolar|
|Debian 8 »Jessie«||18.104.22.168 Grolar||4.4.3 Grolar|
|Debian 7 »Wheezy«||22.214.171.124 Grolar||4.4.3 Grolar||Version 126.96.36.199 only available for sesam-cli on amd64|
|Windows Server 2008||188.8.131.52 Grolar||4.4.3 Grolar|
|Windows 7||184.108.40.206 Grolar||4.4.3 Grolar|
|Ubuntu 14.04||220.127.116.11 Tigon V2||4.4.3 Tigon V2|
|All 32-bit operating systems||18.104.22.168||4.2.2||For some operating systems SEP sesam client is still available in 32-bit.|
|Debian 6 »Squeeze«||22.214.171.124||4.2.2||sesam-cli also available in version 126.96.36.199|
|Windows Server 2003||188.8.131.52||4.2.2|
|Debian 5 »Lenny«||184.108.40.206||4.2.1|
|SLES 11 ≤ SP1||220.127.116.11||4.2.1||Initial SLES 11 Release and Servicepack 1|
For a complete list of supported SEP sesam clients, see SEP sesam Support Matrix.
Major fixes and changes
- See changes at SEP sesam download – changes.