Release Notes 4.4.3 Beefalo: Difference between revisions

From SEPsesam
(Update in progress)
mNo edit summary
Line 120: Line 120:


====Allowed extending retention period of another media pool for migrated savesets====
====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: <tt>eol_adjust_migration_on_other_pool|1|sesam</tt>. For details, see [[Special:MyLanguage/Managing_EOL#EOL_migration|Managing_EOL]].   
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: <tt>eol_adjust_migration_on_other_pool|1|sesam</tt>. For details, see [[Special:MyLanguage/Managing_EOL#EOL_migration|Managing EOL]].   


==={{anchor|GUI}}GUI enhancements===
==={{anchor|GUI}}GUI enhancements===

Revision as of 09:50, 23 May 2019

Template:Copyright SEP AG en

Draft.png WORK IN PROGRESS
This article is in the initial stage and may be updated, replaced or deleted at any time. It is inappropriate to use this document as reference material as it is a work in progress and should be treated as such.

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 moduls that help you improve and manage your SEP sesam environment.

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 and new VIRTUAL access mode for VMs is introduced allowing to configure VMs as clients
  • 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.

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. 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 distributions that are available free of charge.

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

SEP sesam Server requirements

Java xx
For details, see Java Compatibility Matrix.

Installation and upgrades

SEP sesam 4.4.3 Beefalo was released on xth of xx, 2018. Direct upgrade for versions xx to version 4.4.3 Beefalo is supported.

Latest released versions are:

  • SEP sesam 4.4.3.xx Linux Tux.gif – released: xth of xx, 2018.
  • SEP sesam 4.4.3.xx Windows Win7.gif – released: xth of xx, 2018.
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.64 – Client SMS access settings are cleared on the Micro Focus Linux client after update to version 4.4.3.64
  • If you open the properties of an already configured Micro Focus client with Linux OS and click OK, Micro Focus Storage Management Services (SMS) access settings are cleared.
Workaround: In the client properties, select OES-Linux from the Operating system drop-down list and then re-enter and save the settings. SEP support is working on this issue and will provide a fix as soon as possible.
SEP sesam v. 4.4.3.62 – When restoring a Hyper-V VM to a different hypervisor node, hypervisor system volume may get full due to temporarily stored files
  • If you restore a Hyper-V VM to a different hypervisor node (other than original), then some data, such as memory files (.vmrs), is temporarily stored in the folder <SEPsesam\var\tmp> on the target hypervisor. In case of restoring a Hyper-V VM with large memory size (RAM), temporarily stored data may result in full hypervisor system volume.
Workaround: SEP support is working on this issue and will provide a solution as soon as possible.
SEP sesam Server v. 4.4.3.61/.62 – VMware mount/attach does not work with Windows data mover v. 4.4.3.48
  • If SEP Server version is 4.4.3.61, but the Windows data mover is still 4.4.3.48, VMware mount/attach does not work.
Resolve: New backups can be mounted/attached without problems when both, the Windows data mover and SEP sesam Server have the same version – update the data mover to the same version as your SEP sesam Server!
SEP sesam Server v. 4.4.3.61/.62 – VMware mount/attach does not work for incremental (INCR) backups performed with the previous version
  • If SEP Server version is 4.4.3.61 and INCR VMware backups have been performed with the previous SEP sesam version, attaching and mounting VMDK is not possible. The problem is that in the .lis file the date format of INCR savesets is incorrect, while sm_vfs expects a date and time greater than the time of the corresponding FULL backup.
Workaround:
  • Please contact SEP sesam support at support@sep.de for assistance OR
  • Perform the following tasks manually to fix the date in the .lis files: Delete all .lsl and .lst files. Then use a plain text editor, such as Notepad++, to modify the dates in all .lis files: Use Windows Explorer to navigate to lis folder and search for: *_V?201*.lis. Select all found files and use the right mouse button to open them. Then find and replace (use Search > Replace) the date "0000-00-00 00:00:00" with any real date, for example, "2018-01-01 01:01:01". In all subsequent INCR files there must be a time stamp that is more recent, e.g. "2018-01-01 01:01:02", "2018-01-01 01:01:03"!
  • SEP sesam v. 4.4.3.56-4.4.3.62 – After the last Windows 10 update, system state restore fails to set standard attributes for Windows Defender files and directories
    • After automatically updating Windows 10, system state restore finishes with warnings because standard attributes for Windows Defender files and directories are not set.
    Workaround: SEP support is working on this issue and will provide a solution as soon as possible.
    SEP sesam v. 4.4.2.xx and 4.4.3.xx – Restore of multiple Oracle archive log files from tape fails
    • When restoring multiple Oracle archive log files that were written at different time intervals to the same tape, restore fails. The problems is that RMAN starts a restore for every Oracle log file with no drive number set, thus the restore job is submitted into queue manager without drive number, using different drives. Then restore requires a tape which is already mounted on another drive and, consequently, fails.
    Workaround: To ensure that only one tape drive is used during the backup, start the RMAN restore with only one drive by setting the value of SESAM_DRIVE.
    Fixed with SEP sesam Server 4.4.3.xx Beefalo:


    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 confguration 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.

    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.

    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.

    New VIRTUAL access mode

    Now it is possible to configure the VMs as clients with a new VIRTUAL access mode. This access mode is intended to manage individual VMs as individual clients by allowing to configure specific ACLs for individual VMs. For details, see Access Modes.

    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.

    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.

    Unsupported 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