Release Notes 4.4.3 Grolar

From SEPsesam
Jump to: navigation, search
This page is a draft. Treat the information on this page with caution as it may be incomplete.

Copyright © SEP AG 1999-2018. 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.

Information sign.png Note
SEP AG is pleased to announce the beta release of SEP sesam 4.4.3 Grolar. If you are interested in testing the beta version, please register as a beta tester by email to Before installing the beta version, make sure that you understand the beta release version status and conditions, available at Hints for beta testing.

What's new in SEP sesam 4.4.3 Grolar

SEP sesam new release, a hybrid Grolar, brings a fistful of features that may help improve protecting data in your environment and ease administrative tasks.

Version 4.4.3 Grolar introduces new S3 cloud storage to be able to safely store and retrieve your business data. Also new is enhanced capability to utilize NetApp hardware storage snapshots for backup.

SEP sesam no longer supports Hyper-V multiple virtual machine backup (by specifying all as a source) in one backup task. You have to configure a backup task for each virtual machine. Now it is also possible to restore single items from a Hyper-V backup.

New backup levels are available for Citrix XenServer backups.

SEP sesam allows administrators to configure access control lists (ACLs) for locations and clients, if they are granted appropriate permissions.

Direct access recovery (DAR) is now enabled by default during NDMP backup to enable selective restore. Previous special configuration of DAR is no longer required nor supported.

With Self-Service Restore Assistant you can now restore a data from a regular Path, NDMP and NSS backups as well as email(s) from Kopano backup.

Default access mode is now changed from CTRL to SM_SSH to provide more secure communication.

You can now exclude patterns (directories or files) from BSR image backup (BSR Pro 2.0) and activate compression. For details, see SEP sesam BSR Pro – Backup Configuration.

GUI enhancements enable you to check the Si3 deduplication store state, set your preferred GUI mode, clear the GUI cache memory, disable a particular backup task or a task group from running for a certain period of time, and set additional options.

Rythm templates can be used for customized advanced reporting. They are installed in the <SESAM_BIN>/skel/templates/rythm directory. Note, however, that such custom reports are beyond the scope of SEP sesam standard support; they require additional technical assistance provided by SEP Consulting Service.

SEP sesam Server requirements

JavaFX is required for the web dashboard and user-defined schedules. For details on the exact version, see Java Compatibility Matrix.
64-bit or PowerPC (PPC) architecture required
SEP sesam Server requires an operating system running on 64-bit or a PowerPC (PPC) architecture. PowerPC (PPC) is supported for several Linux distributions, see SEP sesam Support Matrix.

For details, see SEP sesam Support Matrix and SEP sesam Server hardware requirements.

Installation and upgrades

Information sign.png Note
As of Grolar release, SEP sesam executables are single signed with SHA256. Because of the buffer limitation of the GetCertHash() function on Windows Server 2008 SP2, the SEP sesam executables which are now signed with a SHA256 certificate cannot run on Windows Server 2008. To install/upgrade SEP sesam on the respective Windows Server version, you have to install a special Windows update first. For details and update download, see any of the following links:

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 Grolar known issues
SEP sesam v. – After fresh installation and configuration of Si3, snapshots are not synchronized to S3 cloud storage
  • SEP sesam cloud storage feature uses clone media pool to save the snapshots and synchronizes data to S3 cloud; the clone media pool has to be active to be available for sync and other operations. However, after the initial setup of the clone media pool its inactive value is not set to any real value but rather to NULL; consequently, comparison of a value to NULL returns unknown which means that the clone media pool is not recognized and cannot be used for data sync.
Workaround: To change the inactive value for a clone media pool from NULL to an existing value, double-click the clone media pool to open its properties and select the check box Set media pool inactive; then deselect the check box again to make the media pool active. When you select and then deselect the check box, you change its value from unknown NULL and activate the clone media pool for upload – synchronization with the S3 cloud. SEP support is working on this issue and will provide a solution as soon as possible.
SEP sesam version – Kopano restore fails with python error OSError: [Errno 2] No such file or directory
  • In SEP sesam, the following error appears when performing a Kopano restore: OSError: [Errno 2] No such file or directory. Consequently, restore fails with a status: 0-RESTORE Restore failed. No data has been restored!
Resolve: Fixed with a patch. You can download it from
SEP sesam v. – Old disk_info Linux backup task is no longer supported – its usage may result in data loss
  • During update all customers which are still using backup task with source disk_info backup task are notified that the disk_info Linux backup task is no longer supported. It has been replaced by BSR Linux/REAR. If you still use the obsolete disk_info backup task, you will no longer be able to restore your data.
Resolve: Reconfigure your old disk_info Linux backup tasks by selecting the Linux BSR as a task type in the task properties or create new backup tasks with type Linux BSR. For details, see Disaster Recovery for Linux 3.0. Note that SEP AG is not responsible for potential data loss that may occur as a result of backing up data with unsupported backup task.
SEP sesam v. – Windows Installer crashes when updating SEP sesam Server
  • During SEP sesam Server update to Grolar version, the MSI installer crashes; however, all sesam services are running and SEP sesam Server is working normally. The problem is caused by the BSR Pro module.
Workaround: The users should not have any problems and can continue to use the updated version. SEP support is working on this issue and will provide a solution as soon as possible.


SEP sesam backup for hypervisors (VMware, Hyper-V, Citrix XEN, KVM, OpenNebula) cannot back up the data on the independent disks or Raw Device Mapping (RDM) disks
When backing up via hypervisor and using external disk, SEP sesam cannot back up the data on the independent or RDM disks due to a hypervisor limitation that does not support including independent disks in virtual machine snapshots. The data of such disks is silently skipped from backup, hence the backup saveset contains no data for the independent disk while the backup succeeds and no warning about the missing data is issued.
  • VMware does not support including independent disks in VM snapshots. As of Grolar version, SEP sesam issues a warning about the missing data for VMware. To avoid the warnings and have a successful backup, the independent disks and RDMs have to be excluded from the backup task or (see next item)
  • To back up virtual machines that contain independent independent disks and RDMs, you have to install the SEP sesam Client in the virtual machine and perform an additional file or application backup to back up this data.
SEP Warning.png Warning
If a restore of a VM with independent disk is performed to the original VM by using the option overwrite, the independent disk is re-created and all existing data on the restore target is lost.

Enhancements and changes

S3 cloud storage

An S3 (simple storage solution) cloud storage can now be used to safely store and retrieve your business data. SEP sesam treats the S3 cloud storage like any other devices. It creates the snapshots and synchronizes data to the cloud. For details, see S3 Cloud Storage Backup.

NetApp storage snapshots

SEP sesam provides backup and restore integration built on NetApp Snapshot copies. You need to configure a new data store type – NetApp Snap Store to easily use hardware snapshots as usual backups. For details, see NetApp Storage Snapshots Backup.

Hyper-V backup and restore

Separate task for each VM
It is no longer possible to back up multiple VMs running on a Hyper-V with a single task. Now you have to create a separate task for each VM running on a Hyper-V standalone server or Hyper-V cluster. However, you can assign individual backup tasks to a task group and then trigger the backup of all tasks belonging to that group with a single event. For details, see Hyper-V Backup.
Single item restore for Hyper-V
Now you can restore single items from a Hyper-V backup if the saveset is stored on a data store. For details, see Hyper-V Restore.

Citrix XenServer new backup levels

SEP sesam introduces new backup levels (FULL, INC and DIFF) for Citrix XenServer backups. Note that COPY backup is no longer supported. For details, see Citrix XenServer Backup.

Access control lists (ACLs)

The administrators can configure ACLs to enable or disable access to location (group of clients) or specific client. Note that before configuring ACLs, database-based authentication must be activated and users configured and added to the relevant group. For details, see Using Access Control Lists.

NDMP direct access recovery (DAR)

Direct access recovery (DAR) index is required to restore a directory or a single file from a NDMP backup (selective restore). As of version 4.4.3 Grolar, DAR is enabled by default (no configuration is required). While DAR can greatly reduce the time it takes to restore individual files, it might be unnecessary in case you want to backup and consequently restore only the whole volume. In such case, you may disable DAR to improve backup performance. For details, see NDMP Backup.

Self-Service Restore Assistant

It is now possible to use web restore assistant to restore data not only from regular Path backups, but also from NDMP and NSS file system Path backups as well as emails from Kopano backups with a few simple steps. You can connect to web restore assistant and perform a restore if you have appropriate permissions. If a backup is encrypted and the password is not stored in the SEP sesam database, it is now possible to enter the encryption password online. For details, see Self-Service Restore Assistant.

New default access mode

The default access mode is now SM_SSH (previously CTRL) which provides strong authentication and secured data communication for clients and servers in the SEP sesam environment. SSL libraries now iclude libmicrohttpd, libcurl, and libopenssl.

GUI enhancements

  • SEP sesam introduces a number of data store enhancements (S3 credentials tab, Si3 State tab, new data store type, etc.). For details, see Configuring a Data Store and Configuring Si3 Deduplication Store.
  • Database-based authentication and authorization are extended and can be combined with the LDAP authentication and authorization and/or with AD (Active Directory). SEP sesam authorizes the users based on the mapped roles and their associated privileges.
  • SEP sesam features a GUI that can be customized and now also adjusted by selecting one of the following UI modes: basic, advanced or expert. The mode can be changed in GUI: from the menu bar select Configuration -> Defaults -> Extras -> UI Mode. For details, see UI Mode.
  • A force refresh can be used to clear the GUI cache memory and consequently to update the view. For details, see All Results by State.
  • Rather than deactivating a schedule (and all related jobs), you can now deactivate a single task but keep it in the list of tasks. You can also disable a whole task group by using the same option the Execution is blocked. You can enable a disabled task and/or task group again at any time. For details, see Disabling and Enabling Backup Task.

Changes in SEP sesam License

  • New license editions VM Essential and VM Essential Plus introduce a CPU socket based license for VMware and Hyper-V backup.
  • New license for 'source Side Deduplication'

End of maintenance and support

Unsupported SEP sesam Server OS

The following operating systems are no longer supported for SEP sesam Server:

  • Windows Server 2008 Win7.gif
Information sign.png Note
The limitation applies only to SEP sesam Server systems and does not affect SEP sesam Clients. Windows Server 2008 R2 SP1 is still supported. For a complete list of supported SEP sesam Clients, see SEP sesam support matrix.

Major fixes and changes

See also

SEP sesam Release Versions