Release Notes 4.4.3 Grolar

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 safely store and retrieve your business data.

SEP sesam no longer supports Hyper-V multiple virtual machine backup (by specifying the source all) in one backup task. You have to configure a backup task for each virtual machine.

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 mails from Kopano backups online (in addition to regular save sets restore).

SEP sesam Server requirements

Java xx

For details, see Java Compatibility Matrix.

Installation and upgrades

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: You cannot run an application that is signed with a SHA-256 certificate on a computer that is running Windows Vista SP2 or Windows Server 2008 SP2 Eine Anwendung, die mit SHA-256-Zertifikat signiert ist, kann nicht auf einem Computer ausgeführt werden, der Windows Vista SP2 oder Windows Server 2008 SP2 ausführt.

SEP sesam 4.4.3 Grolar was released on x^th of xx, 2018. Direct upgrade for versions xx to version 4.4.3 Grolar is supported.

Latest released versions are:

• SEP sesam 4.4.3.xx Linux – released: x^th of xx, 2018.
• SEP sesam 4.4.3.xx Windows – released: x^th of xx, 2018.

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

• Release notes for SEP sesam 4.4.3 Tigon V2

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 Grolar known issues:

SEP sesam v. 4.4.3.48 – Using old disk_info Linux backup task may result in data loss The disk_info 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 task 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. 4.4.3.48 – Slow performance with Linux backup which uses Blowfish Encryption, *.lis files are missing In SEP sesam version 4.4.3.48, backup on Linux/UNIX client which uses the Blowfish Encryption causes the entire backup process to slow down due to high STPD output logging which halts generation of *.lis files. SEP sesam uses the *.lis files to create information about the backup unique files, which are then used by the restore wizard, therefore any potential restore would be incomplete and data would be lost. Workaround: Create a new set of backup tasks for your Linux/UNIX clients with Advanced Encryption Standard (AES) encryption. SEP support is working on this issue and will provide a STPD patch as soon as possible. SEP sesam v. 4.4.3.48 – Hyper-V restore – import fails if only a Windows Client package is installed on the Hyper-V Server In SEP sesam Windows Client package 4.4.3.48, a hyperv_import.dll is missing. Consequently, Hyper-V restore – import fails if only the SEP sesam Windows Client package is installed on the Hyper-V standalone server or on Hyper-V cluster nodes. Workaround: Uninstall the SEP sesam Client package and install the SEP sesam Server package (includes the Client and GUI components) on your Hyper-V standalone server and, if clustered, on Hyper-V cluster nodes. For details, see Microsoft Windows installation. SEP sesam v. 4.4.3.48 – Installation is aborted with a misleading error message In SEP sesam version 4.4.3.48, Java 8 requirement is checked during installation. If the required Java version (at least patch level 111 ≥ JRE 1.8.0_111) is not present or the existing version is too low (e.g., Java 1.8.0_101), SEP sesam installation is aborted with an incorrect error message; instead of reporting that SEP sesam requires at least Java 1.8.0_111, a message similar to the following is shown: Unable to launch <path>sm_db_update.exe ...SetVDDK failed. sm_db_update.exe returned 2., and the installation is aborted. Workaround: Make sure that you install the required Java version and repeat SEP sesam installation/update procedure. SEP support is working on this issue and will provide a fix as soon as possible. SEP sesam v. 4.4.3.48 – The Loader content in GUI may show incorrect status In SEP sesam version 4.4.3.48, the Loader content is not updated in GUI if only the slot content has been changed manually. The Loader content is only updated if a drive-related change was performed, such as unload or load. In case you have changed the content of your tape device manually and then performed archive adjustment by using the option Adjustment by barcode only (checking the barcodes of all tapes which are not in drives – without loading them into the drive and reading the label), the manually changed slot content is not recognized and the Loader content in GUI is not updated. Workaround: SEP support is working on this issue and will provide a fix as soon as possible. SEP sesam v. 4.4.3.48 – The data store cannot be deleted in SEP sesam GUI In SEP sesam version 4.4.3.48, it is not possible to delete a data store via SEP sesam GUI even though the data store does not contain any valid or locked data. Workaround: SEP support is working on this issue and will provide a fix as soon as possible.

Fixed with SEP sesam Server 4.4.3.xx Grolar:

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.

Hyper-V backup

As of version 4.4.3 Grolar, it is no longer possible to back up multiple VMs running on a Hyper-V standalone server or on a Hyper-V cluster 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.

Citrix XenServer backup levels

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

Access control lists (ACLs)

An ACL specifies which users or groups are granted access to objects, as well as what operations are allowed on given objects (read, write or execute). The administrators can configure ACLs for a location (group of clients) or a specific client, if they are granted appropriate permissions (admin). 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

As of v. 4.4.3. Grolar, it is possible to use web restore assistant to perform an online restore of mails from Kopano backups. Self-Service Restore Assistant enables you to restore not only save sets (files), but also mails (Kopano only) with web UI in a few simple steps. You can connect to web restore assistant 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.

End of maintenance and support

Obsolete SEP sesam Server version

No changes since SEP sesam version 4.4.3 Tigon V2.

Unsupported OS

The following operating systems are no longer supported:

• Windows 2008
• Windows 2008 R2

NOTE: Windows 2008 [R2] is still supported with previous SEP sesam version 4.4.3 Tigon V2. 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.
• Change report 4.4.3.xx Grolar

See also

SEP sesam Release Versions