Release Notes 4.4.3 Tigon v.2

From SEPsesam
Revision as of 14:08, 10 November 2017 by Sta (talk | contribs) (Updated.)

Template:Copyright SEP AG en

What's new in SEP sesam 4.4.3 Tigon v.2

SEP sesam 4.4.3 Tigon v.2 introduces new Kopano backup (previously Zarafa backup) and Self-Service Restore Assistant.

Backup of DB2 is enhanced with DB2 automatic archive log backup to SEP sesam.

You can now clean up orphaned save sets from data store manually, thus releasing the space that might be occupied by orphaned save sets.

The maximum initial size for Si3 deduplication store is restricted to 40 TB.

SEP sesam Server requirements

Java 8 (at least patch level 111)
SEP sesam 4.4.3 Tigon v.2 requires Java version equal to or higher than JRE 8u111 (≥ JRE 1.8.0_111). regardless of the operating system. Previous Tigon versions also require Java 8 for Windows Server and GUI, but not for other OS. For details, see Java Compatibility Matrix.
JavaFX
JavaFX is required for the web dashboard and user-defined schedules features. The dashboard can also be viewed in GUI, but only if JavaFX is present on the respective GUI client. If JavaFX is not available, the web dashboard can only be accessed by browser (http://[servername]:11401/sep/ui).
Information sign.png Note
Oracle®'s Java 8 already includes JavaFX (e.g., on Windows). Oracle®'s OpenJFX Project provides JavaFX packages that can be installed separately if some other Java version is used, such as IBM Java, which is typically installed on SuSE. Depending on your system and Java version, manually install either OpenJFX package or Oracle®'s Java 8 on your SEP sesam GUI client to have all the latest features available.
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

SEP sesam 4.4.3 Tigon v.2 was released on xx, 2017. Direct upgrade for versions xx to version 4.4.3 Tigon v.2 is supported.

Latest released versions are:

  • SEP sesam xxx Linux Tux.gif – released: xxx, 2017.
  • SEP sesam xxx Windows Win7.gif – released: xxx, 2017.
Win7.gif Windows specific

The 4.4.3 Tigon v.2 installation package on Windows also includes:

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 Tigon v.2 known issues:
SEP sesam version 4.4.3.45 – VMware backup fails after update
  • After a successful update to SEP sesam v. 4.4.3.45, VMware backup fails.
Workaround: The VDDK is required on VMware data mover; it needs to be uninstalled and then installed again. Start a Powershell as a local administrator, switch to <sesam-root>\bin\sesam, then enter ./set_vddk.ps1 -e remove and ./set_vddk.ps1 -e install.

Enhancements and changes

Kopano backup

Zarafa re-branded to Kopano in 2016; SEP sesam provides efficient data protection for this mail and messaging collaboration suite in place of Zarafa. SEP sesam backup extension for Kopano Collaboration Platform provides backup and restore of single user mails, mailboxes and public folders. For details, see Kopano Backup.

Self-Service Restore Assistant

As of 4.4.3. Tigon v.2, it is possible to restore save sets online with the Self-Service Restore Assistant. Providing that users have been granted appropriate permissions, they can restore their own data, if the following conditions are met: backed up data belongs to an ordinary Path backup (no special backup types, such as system state backup, SAP Hana, Exchange Server, can be restored online); if a backup is encrypted, the password must be stored in the SEP sesam database (SEP sesam does not provide an option to enter the encryption password online). For details, see Self-Service Restore Assistant.

DB2 automatic archive log backup

In order to enable online backups of DB2, you have to enable archive logging for DB2 by modifying the LOGARCHMETH1 and LOGARCHOPT1 database configuration parameters. This enables automatic archive log backup to SEP sesam. For details, see DB2 Backup.

Clean up orphaned save sets

You can manually remove orphaned save sets from the data stores by using the new Clean up option in the Data Stores content pane. This is useful in cases when a data store seems to be inaccessible, its storage space is occupied, or SEP sesam space check shows non-sesam data. For details, see Data Store.

Limited maximum initial size of Si3 deduplication store

To avoid issues arising from combination of too large Si3 deduplication stores and inefficient hardware, the maximum initial Si3 deduplication store size is restricted to 40 TB since Tigon V2 (4.4.3.46). This restriction is valid when creating a new Si3 deduplication store in GUI.

Information sign.png Note
Customers with special requirements for larger Si3 deduplication store should contact SEP support to be able to increase the value up to an optimum size for their specific environments.

End of maintenance and support

Obsolete SEP sesam Server version

No changes since SEP sesam version 4.4.3 Tigon.

Unsupported SEP sesam Server OS

No changes since SEP sesam version 4.4.3 Tigon.

Major fixes and changes

See also

SEP sesam Release Versions