Release Notes 4.4.3 Tigon v.2: Difference between revisions

From SEPsesam
Line 19: Line 19:
   
   
==={{anchor|requirements}}SEP sesam Server requirements===
==={{anchor|requirements}}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]].
;Java 8 (at least patch level 111; note that Java 9 is not supported!): 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 [[Special:MyLanguage/SEP sesam Dashboard|web dashboard]] and [[Special:MyLanguage/Creating Custom Calendar|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). {{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.}}
;JavaFX: JavaFX is required for the [[Special:MyLanguage/SEP sesam Dashboard|web dashboard]] and [[Special:MyLanguage/Creating Custom Calendar|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). {{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_OS_and_database_support_matrix|SEP sesam Support 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_OS_and_database_support_matrix|SEP sesam Support Matrix]].

Revision as of 11:07, 5 December 2017

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.

GUI enhancements enable you to clean up orphaned save sets from data store manually, quickly scan the success of backup jobs by toggle grouping, use improved smart grouping when generating a task for grouped VMs, and examine the progress of the replication.

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

SEP sesam will automatically retain the last successful backup or migration save set in the same pool when the next backup/migration fails. Note that this behavior is version specific and it differs from the default behavior implemented in version 4.4.3.42 Tigon. For details, see Managing EOL.

SEP sesam Server requirements

Java 8 (at least patch level 111; note that Java 9 is not supported!)
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 5th of December, 2017. Direct upgrade for versions 3.6/4.x to version 4.4.3 Tigon v.2 is supported.

Latest released versions are:

  • SEP sesam 4.4.3.48 Linux Tux.gif – released: 5th of December, 2017.
  • SEP sesam 4.4.3.48 Windows Win7.gif – released: 5th of December, 2017.
Win7.gif Windows specific

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

  • VMware® Virtual Disk Development Kit (VDDK) version 6.5 for Windows.
  • Callback File System® (CBFS®) version 6.1.181 from EldoS Corporation, used to create virtual file systems and disks for save sets which are stored on SEP sesam local data store or Si3 deduplication store.
Information sign.png Note
A CBFS driver is needed for the virtual file system layer (Cross Platform Recovery File System – XPRFS). The installation/update of this driver requires a reboot of your newly installed or updated Windows SEP sesam Server unless this driver is already installed with a previous SEP sesam 4.4.3 installation.

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 Tigon v.2 known issues:
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.48 Tigon V2:
SEP sesam version ≤ 4.4.3.45 – Throughput for local backups is very low
  • In some Linux systems, e.g., SLES 12, the local loopback device lo is often configured with MTU (Maximum Transmission Unit) size 65536 (64K). This may decrease the local transfer throughput because the MTU size is equal to the transfer buffer size used in SEP sesam.
  • Fixed: SEP sesam Server version 4.4.3.48 (Tigon V2).

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 v. 4.4.3. Tigon v.2, it is possible to restore save sets online with the Self-Service Restore Assistant. After authentication users can restore their own data, if they belong to the user group restore and 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.

SAP ASE

The SAP ASE backup extension is now implemented as an internal backup appliance to provide efficient data protection for SAP ASE and simplify the restore process. It performs online backups of SAP based on Sybase ASE databases using the Sybase SQL API. For details, see SAP ASE Backup.

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.

GUI enhancements

  • 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.
  • You can use additional Toggle Grouping option in the Backups content pane to group the same backup task states in one item and display its current status. Grouping allows you to quickly scan the success of backup jobs. For details, see Toggle Grouping.
  • When automating backup of virtual machines by creating VMware tasks, you can use the improved Create VM tasks option with a powerful Attributes feature to enable smart grouping of existing or new VMs that fit certain criteria for backups. For details, see Automating Backup of Virtual Machines.
  • In the Migration and Replications content pane you can examine the progress of the replication and see how much data is being transferred; you can check data size, physical and nominal data in the new columns Data Size, Transferred, Transferred (Brutto) and Progress. For details, see Checking replication status.

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