Release Notes 4.4.3 Tigon: Difference between revisions
(→{{anchor|issues}}Known issues and limitations: -> Bug 22498) |
|||
(16 intermediate revisions by 2 users not shown) | |||
Line 2: | Line 2: | ||
<!--{{note|SEP AG is pleased to announce the beta release of SEP sesam 4.4.3 ''Tigon''. If you are interested in testing the beta version, please register as a beta tester by email to [mailto:beta@sep.de beta@sep.de]. Before installing the beta version, make sure that you '''''understand the beta release version status and conditions''''', available at [[Hints for beta testing]].}}--> | <!--{{note|SEP AG is pleased to announce the beta release of SEP sesam 4.4.3 ''Tigon''. If you are interested in testing the beta version, please register as a beta tester by email to [mailto:beta@sep.de beta@sep.de]. Before installing the beta version, make sure that you '''''understand the beta release version status and conditions''''', available at [[Hints for beta testing]].}}--> | ||
== {{anchor|new}}What's new in SEP sesam v. 4.4.3 ''Tigon''== | == {{anchor|new}}What's new in SEP sesam v. 4.4.3 ''Tigon''== | ||
<div class="boilerplate metadata" id="Additional resources" style="background-color: #f0f0f0; color:#636f73; border: 1px ridge #cdd3db; margin: 0.5em; padding: 0.5em; float: right; width: 35%; "><center><b> | <div class="boilerplate metadata" id="Additional resources" style="background-color: #f0f0f0; color:#636f73; border: 1px ridge #cdd3db; margin: 0.5em; padding: 0.5em; float: right; width: 35%; "><center><b>Next release</b></center> | ||
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;" | {|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;" | ||
| rowspan="2" style="padding:0px 10px 0px;" | [[File: | | rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP Tip.png|45px|link=]] | ||
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | | | style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" |What's new in the upcoming release? Check [[Release_Notes_4.4.3_Tigon_v.2|Release Notes 4.4.3 ''Tigon'' v.2]]. | ||
|}</div> | |}</div> | ||
SEP sesam new release, a hybrid Tigon, brings a fistful of features that may help improve protecting data in your environment and ease administrative tasks. | SEP sesam new release, a hybrid Tigon, brings a fistful of features that may help improve protecting data in your environment and ease administrative tasks. | ||
Line 32: | Line 32: | ||
==={{anchor|requirements}}SEP sesam Server requirements=== | ==={{anchor|requirements}}SEP sesam Server requirements=== | ||
;Java 8: SEP sesam ''Tigon v. 2'' requires Java 8 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): SEP sesam ''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]]. | ||
Line 70: | Line 70: | ||
{{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.}} | {{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.}} | ||
{{Box Hint Y|4.4.3 Tigon known issues| | {{Box Hint Y|4.4.3 Tigon known issues| | ||
;SEP sesam v. 4.4.3.45 – Hyper-V backup of several VMs silently skips some VMs: | |||
:*While trying to backup multiple virtual machines, only the last VM is backed up. The other VMs are skipped. This happens because SEP sesam erroneously backs up only the last VM in the source list. | |||
::: '''Workaround:''' SEP support is working on this issue and will provide a fix as soon as possible. | |||
;SEP sesam Server update from v. 4.4.3.25 to 4.4.3.42 – After update the GUI on clients does not start: | |||
:*After updating SEP sesam Server from v. 4.4.3.25 to 4.4.3.42, the GUI (<tt>sm_ui.jar</tt>) on SEP sesam Clients becomes outdated and cannot work together with the new SEP sesam Server GUI. This happens because SEP sesam Clients and SEP sesam Server can only work with the same GUI version. | |||
::: '''Resolve:''' You have to update the GUI on the corresponding clients by using the new GUI package or by manually copying the <tt>sm_ui.jar</tt> file from SEP sesam Server into {{path|<SESAM_BIN>/bin/gui}} folder on SEP sesam Clients. For details, see [[Updating_SEP_sesam#GUI|Updating SEP sesam GUI]]. | |||
;SEP sesam ≤ 4.4.3.45 – Migration ignores client defined by migration schedule/event: | |||
:* In SEP sesam versions equal to or lesser than 4.4.3.45, if you select a client as a migration source in the schedule/event rather than in migration task, the data is not migrated because SEP sesam erroneously ignores the client. | |||
::: '''Workaround:''' To select a client as a migration source, specify the client when creating a migration task: Main Selection -> Tasks -> Migration tasks. For details, see [[Configuring_Migration#task|Creating a migration task]]. | |||
;SEP sesam Lotus Notes Linux sbc < 4.4.3.45 – Exclude pattern with leading {{path|\.}} does not work: | |||
:* In SEP sesam versions lesser than 4.4.3.45, the exclude list, defined on Linux/UNIX in a Lotus Notes backup task, does not work if specified with {{path|\.}}. | |||
::: '''Workaround:''' For SEP sesam versions ''< 4.4.3.45'', specify the exclude list for Notes without the preceding backslash and a dot, e.g., use {{path|/srv/notesdata/help$}} instead of {{path|\./srv/notesdata/help$'}}. | |||
<!--::: '''Resolve:''' Fixed with version 4.4.3.45. You can download the latest version from [https://download.sep.de/ SEP sesam Download Center].--> | |||
;SEP sesam sbc Windows from 4.4.3 to 4.4.3.42 – A UNC path backup silently excludes files without file extension: | ;SEP sesam sbc Windows from 4.4.3 to 4.4.3.42 – A UNC path backup silently excludes files without file extension: | ||
:* As of SEP sesam v. 4.4.3, if the backup source of the UNC path backup is set at the top level to ''//server/share'', e.g., ''//myserver/users'', files without file extension are silently excluded from backup. Even though no exclude is defined, they are excluded because the source ''//server/share'' is extended with wildcard | :* As of SEP sesam v. 4.4.3, if the backup source of the UNC path backup is set at the top level to ''//server/share'', e.g., ''//myserver/users'', files without file extension are silently excluded from backup. Even though no exclude is defined, they are excluded because the source ''//server/share'' is extended with wildcard *.*, which is checked for regular files as of sbc Windows 4.4.3. This issue only occurs if the source is set at the top level; if the source is defined at the lower level, e.g., ''//myserver/users/anonymus'', all files are backed up normally. | ||
::: '''Workaround:''' When backing up a network share and your source is set at the top level, use the wildcard | ::: '''Workaround:''' When backing up a network share and your source is set at the top level, use the wildcard * to process all regular files: ''//server/share/*''; e.g., ''//myserver/users/*''. SEP support is working on this issue and will provide an sbc patch as soon as possible. | ||
::: '''Resolve:''' Fixed with a hotfix available for x64 and x86 Windows versions under https://download.sep.de/servicepacks/4.4.3_Tigon/4.4.3.39/hotfix/ with description: ''A UNC path backup silently excludes files without file extension (includes previous 4.4.3.39 patches)''. | |||
;Linux: SEP sesam unable to start necessary amount of processes since Systemd 228: | ;Linux: SEP sesam unable to start necessary amount of processes since Systemd 228: | ||
:* Linux: Since Systemd 228 and up from kernel 4.3 SEP sesam is not able to start more than 512 processes. The message "Resource temporarily unavailable" is visible in sm_qm_main log. ''Note:'' Will happen with SEP sesam server on SLES12 SP2 or on other Linux distribution using Systemd v228! See: https://github.com/systemd/systemd/blob/dd050decb6ad131ebdeabb71c4f9ecb4733269c0/NEWS | :* Linux: Since Systemd 228 and up from kernel 4.3 SEP sesam is not able to start more than 512 processes. The message "Resource temporarily unavailable" is visible in sm_qm_main log. ''Note:'' Will happen with SEP sesam server on SLES12 SP2 or on other Linux distribution using Systemd v228! See: https://github.com/systemd/systemd/blob/dd050decb6ad131ebdeabb71c4f9ecb4733269c0/NEWS | ||
::: '''Resolve:''' Resolved with entry '''TasksMax''' set to '''infinity''' in configuration file /lib/systemd/system/sepsesam.service. | ::: '''Resolve:''' Resolved with entry '''TasksMax''' set to '''infinity''' in configuration file /lib/systemd/system/sepsesam.service. | ||
;SEP sesam version 4.4.3.42 – Starting Si3 deduplication server fails: | |||
:* In SEP sesam 4.4.3.42, starting Si3 deduplication server fails with the following error: ''Starting dedup sever fails with java.lang.VerifyError: Uninitialized object exists on backward branch 209''. | |||
::: '''Resolve:''' This issue occurs if the installed Java version is not supported. SEP sesam requests a Java version equal to or higher than ''JRE 8u111'' (≥ JRE 1.8.0_111). For details, see [[Java Compatibility Matrix]]. | |||
;SEP sesam version 4.4.3.42 – Windows: IBM Domino Server aborts when starting INCR backup but 'ARCHIVE' logging style is not enabled: | ;SEP sesam version 4.4.3.42 – Windows: IBM Domino Server aborts when starting INCR backup but 'ARCHIVE' logging style is not enabled: | ||
:* In SEP sesam 4.4.3.42, when running IBM Domino INCR backup but 'ARCHIVE' logging style is not enabled then the Domino Server aborts. | :* In SEP sesam 4.4.3.42, when running IBM Domino INCR backup but 'ARCHIVE' logging style is not enabled then the Domino Server aborts. | ||
Line 203: | Line 220: | ||
== {{anchor|changes}}Major fixes and changes == | == {{anchor|changes}}Major fixes and changes == | ||
* See changes at | * See changes at [https://download.sep.de/changes/ SEP sesam download – changes]. | ||
* [[Change report 4.4.3.42 Tigon]] | |||
== See also == | |||
[[SEP_sesam_Release_Versions|SEP sesam Release Versions]] |
Revision as of 09:46, 25 September 2017
What's new in SEP sesam v. 4.4.3 Tigon
SEP sesam new release, a hybrid Tigon, brings a fistful of features that may help improve protecting data in your environment and ease administrative tasks.
Version 4.4.3 Tigon introduces new KVM-related backup extension that is already a part of a SEP sesam Tigon client. It provides efficient data protection for libvirt-based KVM virtualization.
A new extension is included for online backup of SAP ASE based on Sybase database.
SEP sesam supports automatic backup for newly added VMware virtual machines (VMs).
Windows Server 2016 is fully supported with a new version of the disaster recovery solution SEP sesam BSR Pro 2.0 for Windows.
SSL certificates are used to enhance security and help strengthen data protection by providing a secure connection for data transfer to and from SEP sesam Remote Device Server (RDS).
Si3 encryption can be defined on the Si3 deduplication store level. The Si3 deduplication store can now be used for initial seeding.
SEP sesam NDMP now supports single file restore from dump backups with selective restore and allows to exclude certain files from backups.
RHV VM restore introduces VM reduction by creating a thin-provisioned disk file.
GUI enhancements enable you to set database-based authentication and set the default data size units.
If SEP sesam Server is running, the REST API can be accessed via the base URL: http://<host>:<port>/sep/api/. For details, see Using SEP sesam REST API.
SEP sesam Server requirements
- Java 8 (at least patch level 111)
- SEP sesam 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).
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 was released on June 26st, 2017. Direct upgrade for versions 3.6/4.x to version 4.4.3 Tigon is supported.
Latest released versions are:
- SEP sesam 4.4.3.42 Linux – released: August 10th, 2017.
- SEP sesam 4.4.3.42 Windows – released: August 10th, 2017.
The 4.4.3 Tigon 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.
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
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 known issues: |
<appender name="FSCK" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>${gv_rw_stpd}/sm_dedup_fsck-${drive_num}.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>${gv_rw_stpd}/sm_dedup_fsck-${drive_num}_%d{yyyy-MM-dd}-%i.log</fileNamePattern>
<fileNamePattern>${gv_rw_stpd}/sm_dedup_fsck-${drive_num}_%d{yyyy-MM-dd}-%i.log.gz</fileNamePattern>
|
Fixed with SEP sesam Server version 4.4.3.42 Tigon: |
|
Enhancements and changes
New supported systems
SEP sesam Server 4.4.3 Tigon supports the following operating systems and applications:
Newly supported operating systems
- Windows Server 2016 now fully supported with SEP sesam BSR Pro 2.0 for Windows.
- Debian Stretch (x86-64)
Newly supported applications
- vSphere 6.5
- Hyper-V 2016
You can download SEP sesam from the SEP sesam download center. For a complete list of supported OS and databases, see SEP sesam Support Matrix.
libvirt-based KVM virtualization
New backup extension provides efficient data protection for libvirt-based KVM virtualization. It performs online backups of KVM/QEMU virtual machines using snapshot technology and provides a complete or configuration restore to the same or another target. For details, see KVM/QEMU Backup.
SAP ASE
New backup extension provides efficient data protection for SAP ASE. It performs online backups of SAP based on Sybase ASE databases using the Sybase SQL API. For details, see SAP ASE Configuration.
Automating backup of VMware virtual machines
Whenever a new vCenter or ESXi host is added and there are a lot of new VMs present, it is possible to automate VMs backup by including VMs to task groups and using the option Create VM tasks. For details, see Automating Backup of Virtual Machines.
SEP sesam BSR Pro 2.0 for Windows
New version BSR Pro 2.0 for Windows – Windows Server 2016 now fully supported – has a new user interface with improved operability, introduces command line function and live update, and has enhanced backup and imaging speed. For more details, see BSR Pro 2.0 – Disaster Recovery for Windows.
SSL secured communication
SEP sesam introduces SSL (Secure Sockets Layer) protocol to authenticate identities, encrypt and securely transfer data. SSL requires certificates to authenticate clients and establish a secure and trusted communication channel between SBC (sesam backup client) and STPD. For details on configuration, see Configuring SSL Secured Communication for SEP sesam Backup Network.
Si3 encryption
SEP sesam provides encryption for Si3 deduplication store to help ensure compliance with data protection legislation. For details, see Encrypting Si3 Deduplication Store.
Seeding Si3 deduplication store
An Si3 deduplication store can now be used for initial seeding, typically to set up a new Si3 deduplication store for the purpose of replication. For details, see Seeding Si3 Deduplication Store.
NDMP single file restore
SEP sesam introduces selective restore for NDMP. It is now possible to restore single files from dump backups (files and directories are backed up to tape). For details, see NDMP Restore.
RHV VM reduction
During RHV restore, SEP sesam uses the dd utility to create a thin-provisioned (sparse) disk file, thus restoring only the actual size of the VMs. This reduction can be configured in the last step of the restore wizard by clicking Expert Options -> tab Options: Restore options -> enter the option: -a use_dd. For details, see Restoring RHEV Virtual Machines.
GUI enhancements
Database-based authentication can be enabled from GUI by activating authentication under the Permission Management. This is the only way to set the password for the Administrator user. For details, see Configuring Database-Based Authentication.
GUI can be customized according to your needs – besides setting up different GUI layouts and filtering displayed contents, you can also change default data size units. For details, see Customizing GUI.
MSP license
The new Managed Service Provider license model is available. For more information, contact sales@sep.de.
End of maintenance and support
Obsolete SEP sesam Server version
No changes since SEP sesam version 4.4.3.
Unsupported SEP sesam Server OS
No changes since SEP sesam version 4.4.3.
Major fixes and changes
- See changes at SEP sesam download – changes.
- Change report 4.4.3.42 Tigon