Release Notes 4.4.3 Beefalo: Difference between revisions

From SEPsesam
(Update for # 25955, 25953, 25950, 25949, 25936, 25934, 25933, 25924, 25901, 25776, 25773, 25753, 24648)
mNo edit summary
Line 132: Line 132:
;SEP sesam v. < 4.4.3.66 – All data store-related actions fail for ''Path'' data store on RDS  
;SEP sesam v. < 4.4.3.66 – All data store-related actions fail for ''Path'' data store on RDS  
:*All data store actions, such as purge, checkspace, etc., fail for the ''Path'' data store type on RDS with SEP sesam versions < 4.4.3.66 due to the accessibility issues.  
:*All data store actions, such as purge, checkspace, etc., fail for the ''Path'' data store type on RDS with SEP sesam versions < 4.4.3.66 due to the accessibility issues.  
:::Workaround: Update all RDS to SEP sesam version ≥ 4.4.3.69
:::'''Workaround''': Update all RDS to SEP sesam version ≥ 4.4.3.69
;SEP sesam v. 4.4.3.64 – Automatic update of clients with <tt>sm_update_client</tt> fails
;SEP sesam v. 4.4.3.64 – Automatic update of clients with <tt>sm_update_client</tt> fails
:*Automatic remote update using the <tt>sm_update_client</tt> command fails due to files being in use during update.
:*Automatic remote update using the <tt>sm_update_client</tt> command fails due to files being in use during update.
:::Workaround: Update SEP sesam clients manually. Will be fixed with SEP sesam version 4.4.3.70.  
:::'''Workaround''': Update SEP sesam clients manually. Will be fixed with SEP sesam version 4.4.3.70.  
}}</onlyinclude>
}}</onlyinclude>
<!--{{Box Hint|Fixed with [https://download.sep.de/ SEP sesam Server 4.4.3.xx Beefalo]|
<!--{{Box Hint|Fixed with [https://download.sep.de/ SEP sesam Server 4.4.3.xx Beefalo]|

Revision as of 16:19, 16 July 2019

Template:Copyright SEP AG en

What's new in SEP sesam 4.4.3 Beefalo

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 Buster
  • Windows Server 2019

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

Discontinued systems

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

  • RHEL 6
  • SLES 11
  • Debian Jessie

SEP sesam Server requirements

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

Installation and upgrades

SEP sesam 4.4.3 Beefalo beta 1 was released on 17th 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.69 Linux Tux.gif – early released: 8th of July, 2019.
  • SEP sesam 4.4.3.69 Windows Win7.gif – early released: 8th of July, 2019.
Win7.gif 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.

Previous release

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.
4.4.3 Beefalo known issues:
SEP sesam v. 4.4.3.69 – Creating HPE StoreOnce store results in NullPointerException (NPE)
  • Creating the HPE StoreOnce store causes an NPE error that occurs after closing and reopening the GUI; NPE is thrown when clicking the Data Stores in the GUI's Main Selection window.
Workaround: Do not use the Tree view mode for displaying the data stores. Will be fixed with SEP sesam version 4.4.3.70.
SEP sesam v. 4.4.3.69 – Read-only drive is allocated as read/write drive
  • Read-only drive is being periodically incorrectly switched to read/write drive.
Workaround: Will be fixed with SEP sesam version 4.4.3.70.
SEP sesam v. 4.4.3.60–69 (≥ Univention UCS 4.3) – Backup on Univention UCS 4.3 and higher may fail due to incomplete SBC logging
  • Running backups on ≥ Univention UCS 4.3 may fail due to a different OpenSSL version that remained linked to SBC. The following error is shown: "SBC logging without final state message."
Fixed: Note that you should only apply the following patch for your Univention ≥ UCS 4.3 (not Debian or any other system) and only if your backups are failing with the above error. The patch is available under https://download.sep.de/servicepacks/4.4.3/4.4.3.64/linux/ucs/ or directly by clicking UCS patch.
SEP sesam v. 4.4.3.69 – VMware vSphere FDI restore from StoreOnce Catalyst store fails with error
  • VMware vSphere FDI restore from HPE StoreOnce store fails with "Error: db_write_block: Disk current sector out of range" due to the incorrect file size – caused by the padding bytes added to savesets written into a data store.
Workaround: SEP support is working on this issue and will provide a solution as soon as possible. Please contact SEP sesam support at support@sep.de for assistance.
SEP sesam v. 4.4.3.69 – Changing the HPE StoreOnce store drive properties is not possible
  • Changing the HPE StoreOnce data store drive properties is blocked by a pop-up prompting for specifying a path for the data store, which is not relevant for the HPE StoreOnce store and can therefore not be specified.
Workaround: Will be fixed with SEP sesam version 4.4.3.70.
SEP sesam v. 4.4.3.68 – File system consistency check (FSCK) on the SEP Si3 Deduplication store on RDS fails with IOError
  • FSCK on the SEP Si3 Deduplication on SEP sesam RDS does not work due to incorrect return code that causes the IOError: [Errno 0] Error in sm_popen.
Workaround: Will be fixed with SEP sesam version 4.4.3.70.
SEP sesam v. 4.4.3.68 – Hyper-V single file restore fails with error when mounting Hyper-V VHDX, while browsing in GUI is still possible
  • Hyper-V single file restore fails with the 102 error, however, no information about the failure is shown in the Mount to device server window while browsing for source is still possible.
Workaround: SEP support is working on this issue and will provide a solution as soon as possible.
SEP sesam v. 4.4.3.68 – BSR Pro backup of all volumes fails
  • BSR Pro backup with all volumes selected fails with error "invalid parameter" when trying to backup SystemReserved and C:, D:, E: volumes.
Workaround: SEP support is working on this issue and will provide a fix as soon as possible. Please contact SEP sesam support at support@sep.de for assistance.
SEP sesam v. 4.4.3.68 – SEP sesam GUI Save Layout function does not work correctly
  • When using the Save Layout function, the rearranged layout is not saved and the order and display of tabs is not preserved.
Workaround: Do not use this function until the problem is fixed. SEP support is working on this issue and will provide a solution as soon as possible.
SEP sesam v. 4.4.3.67 beta – Configuring Hyper-V restore task fails with NPE error
  • When opening the existing Hyper-V restore task and clicking Next or when trying to start a saved restore task by using Immediate start, the operation fails with the NPE error. The problem is caused by not setting the restore option Start / Do not start virtual machine after restore.
Workaround: Manually select one of the following restore options: Start virtual machine after restore or Do not start virtual machine after restore.
SEP sesam v. 4.4.3.67 beta – User-defined calendar configuration is not working
  • SEP sesam user interface is using Java 11 or OpenJDK 11 which does not include JavaFX. As user-defined calendar is JavaFX-based, it is no longer working.
Workaround: Use List All Calendars instead. SEP support is working on this issue and will provide a fix with the next version of SEP sesam Beefalo.
SEP sesam v. 4.4.3.67 beta – Hyper-V single file restore from INCR backups fails
  • When trying to restore Hyper-V VM single files from incremental (INCR) backup, the restore job fails with error.
Workaround: You can restore single files from the Hyper-V FULL backups instead, as described in Restoring Hyper-V single files. SEP support is working on this issue and will provide a solution as soon as possible.
SEP sesam v. 4.4.3.67 beta – Mounting a backup via VFS does not display the correct content (no subfolders are shown)
  • When mounting a backup via VFS (virtual file system), the subfolders are not shown due to errors in sm_vfs that result in displaying the wrong content.
Workaround: Will be fixed with SEP sesam version 4.4.3.70.
SEP sesam v. 4.4.3.67 beta – Wrong warning message during VMware restore
  • VMware restore shows a warning "Set network name '<name>' failed. Network name does not exist on target" even though the network name does exist on the target. In this case, SEP sesam issues a wrong error message, however, restores under these circumstances are successful regardless of the warning.
Workaround: Will be fixed with SEP sesam version 4.4.3.70.
SEP sesam v. 4.4.3.66 – Hyper-V restore from a powered-on VM fails with VSS API error
  • The restore of a Hyper-V backup from a powered-on VM to another Hyper-V server fails with: VSS API error: NHyperV::FindSingleObject: Failed to enumerate objectsClass name is "Msvm_ComputerSystem"
Workaround: You can only restore a Hyper-V VM to another server if the VM is powered off. SEP support is working on this issue and will provide a solution as soon as possible.
SEP sesam v. < 4.4.3.66 – All data store-related actions fail for Path data store on RDS
  • All data store actions, such as purge, checkspace, etc., fail for the Path data store type on RDS with SEP sesam versions < 4.4.3.66 due to the accessibility issues.
Workaround: Update all RDS to SEP sesam version ≥ 4.4.3.69
SEP sesam v. 4.4.3.64 – Automatic update of clients with sm_update_client fails
  • Automatic remote update using the sm_update_client command fails due to files being in use during update.
Workaround: Update SEP sesam clients manually. Will be fixed with SEP sesam version 4.4.3.70.

Enhancements and changes

HPE StoreOnce Catalyst stores

The Hewlett Packard Enterprise (HPE) StoreOnce backup appliance allows you to configure more Catalyst stores which can be used as a backup storage. HPE StoreOnce fully controls the backup data and enables efficent encryption, deduplication, replication, and recovery. For details, see HPE StoreOnce Configuration, HPE StoreOnce Backup, HPE StoreOnce Restore and Saving Encryption Key Store for HPE StoreOnce Catalyst.

IBM Domino

Lotus Domino has been rebranded as IBM Domino. DIFF and INCR backup levels are enhanced to simplify backup configuration for differential and incremental backups, as described in IBM Domino Server Backup.

Proxmox VE

SEP sesam provides efficient data protection for Proxmox VE, an open-source server virtualization environment that supports a variety of guest operating systems as well as a variety of storage devices, allowing you to back up your Proxmox VE to any virtual machine-supported storage. You can use the integrated Si3 target deduplication for Proxmox backups and benefit from reduced disk capacity and increased overall storage performance. For details, see Proxmox VE Backup and Proxmox VE Restore.

VMware sandbox restore

SEP sesam introduces support for the VMware sandbox restore (SBR). SEP sesam sandbox for VMware is an isolated environment where you can recover and start one or several virtual machines (VMs). It is useful for verifying the VM backups, performing a training, troubleshooting issues, etc. For details, see VMware Sandbox Restore.

Hyper-V

Single file restore

Item-level restore of files and folders can now also be performed from an INCR backup of Hyper-V virtual machine by mounting VHD or VHDX on a device server and browsing the content of a virtual disk file. For details, see Hyper-V single file restore.

Start virtual machine after restore

Automatically starting a virtual machine directly after it has been restored can now be performed from a Hyper-V backup. For details, see Hyper-V Restore.

Citrix XenServer single file restore

Now you can restore single files from the FULL, DIFF or INCR Citrix XenServer backup if the saveset is stored on a data store or Si3 deduplication store. For more information, see Citrix XenServer single file restore.

RPM packages

SEP sesam provides RPM packages for installation on SLES and RedHat. Now you can use distributions package manager (zypper, yum) to ease installation and validation of the packages via signatures. For details, see RPM Repository.

Configuration of LDAP/AD authentication

Configuration of LDAP/AD authentication has been slightly remodeled; configuration windows are redesigned, options are renamed and some options are only visible if UI mode is set to Expert. For details, see Configuring LDAP/AD Authentication.

EOL-related improvements

Improved handling of modified backup EOL

Modifying the backup EOL – retention time for all data that belongs to the same backup – now results in expected behavior of the changed retention setting being applied to only individual savesets based on the same backup as follows:

  • If you are extending the backup EOL (expiration date), the EOL is now adjusted only for the saveset that already has the longest EOL, while EOL of other backups is not affected. This behavior has changed compared to the previous versions, where extended backup EOL resulted in extended EOL for all save sets based on the same backup, i.e., original backup, migrated backup, replicated backup, as well as for all backups in a backup chain, if a save set with adjusted backup EOL was part of it.
  • If you are reducing the backup EOL, it is now adjusted only for the savesets with EOL longer than the newly given EOL, while the savesets with the shorter EOL are not affected; their EOL remains unchanged. For details, see automated EOL adjustment.

Allowed extending retention period of another media pool for migrated savesets

It is now possible for migration to increase EOL of the referenced savesets on other media pools too, not only on the target media pool. This is achieved by adding the following key to global settings in GUI: eol_adjust_migration_on_other_pool|1|sesam. For details, see Managing EOL.

HiDPI display

Now HiDPI displays are supported. These screens with a high resolution in a relatively small format (e.g., high-end laptops and monitors) provide a very clean and crisp display, however, the HiDPI mode may not be supported by all user interfaces, browsers and other accompanying software. Therefore, SEP sesam v. ≥ 4.4.3 Beefalo user interface might not be appropriately displayed and you may need to adjust your environment for SEP sesam HiDPI display. For details, see HiDPI Display Support.

Automatic updates of GUI Server

SEP sesam GUI Server can be set to automatically update when a new version is available at SEP Download Center. Automatic updates can be enabled from the SEP sesam menu bar -> Configuration -> Defaults -> tab Install/Update -> Update mode. For details, see Configuration: GUI update.

GUI enhancements

In addition to GUI redesign and improved functionality with integrated filtering, GUI enhancements enable you to update the clients, change the view mode, check a trace log for finished backups and restores, set additional notification options, etc.

  • SEP sesam provides additional View Mode button that enables you to switch between the table and tree view easily. It is also possible to group the same backup tasks states in one item. For details, see View Mode.
  • New Trace Log tab is introduced in the properties of a finished backup or restore which records detailed information about the backup or restore process depending on the configured log level. For details, see Trace Log.

Encryption support matrix

New encryption matrix shows supported encryption types according to the operating system and task type. If the backups are performed externally by another utility, SEP sesam encryption is replaced by external encyption, done outside SEP sesam. For more information, see Encryption Support Matrix.

End of maintenance and support

Obsolete SEP sesam Server version

No changes since SEP sesam version 4.4.3 Grolar.

Discountinued SEP sesam Server OS

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 sesam Release Versions

Operating system Last available version Release Notes
Windows Server 2012 5.1.0.7 Apollon 5.1.0 Apollon
RHEL 7 5.1.0.7 Apollon 5.1.0 Apollon
Debian 9 »Stretch« 5.0.0.15 Jaglion V2 5.0.0 Jaglion V2
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 available 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 available SEP sesam Server release for Windows Server 2008 R2 is Beefalo V2.
Ubuntu 16.04 4.4.3.84 Beefalo V2 4.4.3 Beefalo V2
RHEL 6 4.4.3.64 Grolar 4.4.3 Grolar
Debian 8 »Jessie« 4.4.3.64 Grolar 4.4.3 Grolar
Debian 7 »Wheezy« 4.4.3.64 Grolar 4.4.3 Grolar Version 4.4.3.64 only available for sesam-cli on amd64
Windows Server 2008 4.4.3.64 Grolar 4.4.3 Grolar
Windows 7 4.4.3.64 Grolar 4.4.3 Grolar
Ubuntu 14.04 4.4.3.48 Tigon V2 4.4.3 Tigon V2
All 32-bit operating systems 4.2.2.40 4.2.2 For some operating systems SEP sesam client is still available in 32-bit.
SLES 10 4.2.2.40 4.2.2
RHEL 5 4.2.2.40 4.2.2
Debian 6 »Squeeze« 4.2.2.40 4.2.2 sesam-cli also available in version 4.4.1.22
Windows Server 2003 4.2.2.40 4.2.2
Debian 5 »Lenny« 4.2.1.34 4.2.1
SLES 11 ≤ SP1 4.2.1.34 4.2.1 Initial SLES 11 Release and Servicepack 1


Major fixes and changes

See also

SEP sesam Release Versions