View source for Release Notes 4.4.3 Grolar

{{Copyright SEP AG en}}
{{Navigation_previous|link=[[Release_Notes|latest Release Notes]]}}

<!--{{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 [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 4.4.3 ''Grolar''==
<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;"
| 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;" |This is not the latest version of SEP sesam Release Notes. To check which is the latest version available, see [[SEP sesam Release Versions]].
|}</div>
SEP sesam new release, a hybrid Grolar, brings a fistful of features that help you enhance data protection in your environment and ease administrative tasks.

Version 4.4.3 ''Grolar'' introduces new [[Special:MyLanguage/Release_Notes_4.4.3_Grolar#S3|''S3 cloud storage'']] to be able to safely store and retrieve your business data. Also new is enhanced capability to utilize [[Special:MyLanguage/Release_Notes_4.4.3_Grolar#NetApp|''NetApp hardware storage snapshots'']] for backup.

SEP sesam no longer supports [[Special:MyLanguage/Release_Notes_4.4.3_Grolar#Hyper-V|''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. However, you can now restore single items from Hyper-V FULL backups if the saveset is stored on a data store or Si3 deduplication store.

SEP sesam introduces '''changed block tracking''' (CBT) support for ''Citrix XenServer 7.3 and higher'' thus providing incremental backup capabilities; new backup levels are available accordingly for [[Special:MyLanguage/Release_Notes_4.4.3_Grolar#Citrix|''Citrix XenServer'']] backups.

SEP sesam allows administrators to configure [[Special:MyLanguage/Release_Notes_4.4.3_Grolar#ACL|''access control lists'']] (ACLs) for locations and clients, if they are granted appropriate permissions.

[[Special:MyLanguage/Release_Notes_4.4.3_Grolar#DAR|''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 [[Special:MyLanguage/Release_Notes_4.4.3_Grolar#assistant|''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 [[Special:MyLanguage/Release_Notes_4.4.3_Grolar#access_mode|''access mode'']] is now changed from ''CTRL'' to ''SM_SSH'' to provide more secure communication. Note that it is strongly recommended to use the default ''SM_SSH'' instead of ''CTRL'' access mode whenever possible.

With SEP sesam ''Grolar'' SP2 [[Special:MyLanguage/Release_Notes_4.4.3_Grolar#Kopano|''differential backups'']] are supported for Kopano. 

[[Special:MyLanguage/Release_Notes_4.4.3_Grolar#EOL|''Managing EOL'']] has slightly changed for migrated savesets; this behaviour is version specific and it differs from the default behaviour implemented in previous versions.

You can now exclude patterns (directories or files) from BSR image backup (''BSR Pro 2.0'') and activate compression. For details, see [[Special:MyLanguage/4_4_3_Tigon:SEP_sesam_BSR_Pro_–_Backup_Configuration|SEP sesam BSR Pro – Backup Configuration.]]

This release provides [[Special:MyLanguage/Release_Notes_4.4.3_Grolar#improved|''improved functionality'']] for exclude processing for Windows VSS writers and for mounting savesets containing umlauts (ä, ü, ö, ...). 

[[Special:MyLanguage/Release_Notes_4.4.3_Grolar#GUI|''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, manage multiple drives, and set additional options. 

[http://rythmengine.org/ ''Rythm templates''] can be used for customized advanced reporting. They are installed in the {{path|<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 [[Special:MyLanguage/List_of_Licenses#maintenance|SEP Consulting Service]]. 

==={{anchor|requirements}}SEP sesam Server requirements===
;JavaFX: JavaFX is required for the [[Special:MyLanguage/SEP sesam Dashboard|web dashboard]] and [[Special:MyLanguage/Creating Custom Calendar|user-defined schedules]]. For details on the exact version, see [[Java Compatibility Matrix]].

::{{Note|Java 17 is not supported by SEP sesam. For a list of supported Java versions, see the [[Special:MyLanguage/Java_Compatibility_Matrix|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_OS_and_database_support_matrix|SEP sesam Support Matrix]].

For details, see [[SEP_sesam_OS_and_database_support_matrix|SEP sesam Support Matrix]] and [[Special:MyLanguage/Hardware_requirements|SEP sesam Server hardware requirements]].

==={{anchor|installation}}Installation and upgrades===

SEP sesam 4.4.3 ''Grolar'' was released on 23<sup>rd</sup> of July, 2018. Direct '''upgrade''' for versions '''3.6/4.x''' to version '''4.4.3 ''Grolar''''' is supported.

Latest released versions are:
* SEP sesam 4.4.3.64 [https://download.sep.de/linux Linux] [[File:tux.gif]] – released: 29<sup>th</sup> of October, 2018.
* SEP sesam 4.4.3.64 [https://download.sep.de/windows Windows] [[File:win7.gif]] – released: 29<sup>th</sup> of October, 2018.

<!--
* SEP sesam 4.4.3.62 [https://download.sep.de/linux Linux] [[File:tux.gif]] – released: 17<sup>th</sup> of September, 2018.
* SEP sesam 4.4.3.62 [https://download.sep.de/windows Windows] [[File:win7.gif]] – released: 17<sup>th</sup> of September, 2018.
* SEP sesam 4.4.3.61 [https://download.sep.de/linux Linux] [[File:tux.gif]] – released: 25<sup>th</sup> of July, 2018.
* SEP sesam 4.4.3.61 [https://download.sep.de/windows Windows] [[File:win7.gif]] – released: 25<sup>th</sup> of July, 2018.
* SEP sesam 4.4.3.60 [https://download.sep.de/linux Linux] [[File:tux.gif]] – released: 23<sup>rd</sup> of July, 2018.
* SEP sesam 4.4.3.60 [https://download.sep.de/windows Windows] [[File:win7.gif]] – released: 23<sup>rd</sup> of July, 2018.

* Beta release on 7<sup>th</sup> of June 2018.
** SEP sesam 4.4.3.56 [http://beta.sep.de/linux Linux] [[File:tux.gif]] – released: 7<sup>th</sup> of June, 2018.
** SEP sesam 4.4.3.56 [http://beta.sep.de/windows Windows] [[File:win7.gif]] – released: 7<sup>th</sup> of June, 2018.
-->
;[[File:win7.gif]]  Windows specific:
The 4.4.3 ''Grolar''''' 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 savesets which are stored on SEP sesam local [[SEP_sesam_Glossary#data_store|data store]] or [[SEP_sesam_Glossary#Si3_store|Si3 deduplication store]]. {{note|A CBFS driver is needed for the virtual file system layer ([[SEP_sesam_Glossary#XPRFS|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.xx 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 [[Special:MyLanguage/Automatic Updates|Automatic Updates]] and [[Special:MyLanguage/Automatic_Installation_On_Windows| Automatic Installation on Windows]].

{{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: 

*[https://support.microsoft.com/en-us/help/2763674/you-cannot-run-an-application-that-is-signed-with-a-sha-256-certificat 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] 
*[https://support.microsoft.com/de-de/help/2763674/you-cannot-run-an-application-that-is-signed-with-a-sha-256-certificat 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].}}

'''Newer release'''
* [[Release Notes 4.4.3 Beefalo|Release notes for SEP sesam 4.4.3 ''Beefalo'']]

'''Previous release'''
* [[Release_Notes_4.4.3_Tigon_v.2|Release notes for SEP sesam 4.4.3 ''Tigon'' V2]]

== {{anchor|issues}}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.}}
{{Box Hint Y|SEP sesam v. 4.4.3.61-64 known issues|
;SEP sesam v. 4.4.3-4.4.3.84 – Si3S does not work in case of changed STPD port on the Client 
:*[[Special:MyLanguage/SEP_sesam_Glossary#Si3S|SEP Si3 source-side deduplication]] (Si3S) backup of a client to a SEP Si3 deduplication store not work, if the STPD service TCP port on the client side (''client properties'' -> ''Options tab'' -> ''STPD options'') is changed from the default port.

:::'''Workaround:''' Make sure that you use the default STPD TCP port on the client side. For details, see [[Special:MyLanguage/4_4_3_Tigon:List_of_Ports_Used_by_SEP_sesam|List of Ports Used by SEP sesam]].
;SEP sesam v. 4.4.3.42–64 – (''Windows'') A data block is not written to tape when EOM is reached together with the segment size, thus making a restore of data referencing this block impossible 
:*(''Applies only to Windows'') When backing up to tape, a data block is not written to tape when the segment size is reached at [[Special:MyLanguage/SEP_sesam_Glossary#EOM|EOM]], therefore a restore of data referencing this block is not possible. While a Path Archive can still be restored until EOM is reached, a complete restore or migration will fail.
:::'''Resolution:''' Fixed with the patch for ''Beefalo V2'', contact SEP sesam support at [mailto:support@sep.de support@sep.de] for assistance. 
;SEP sesam v. 4.4.3.60–64 (≥ Univention UCS 4.3) – Backup on Univention UCS 4.3 and higher may fail due to incomplete SBC logging
:*Running backups on ≥ Univention UCS 4.3 may fail due to a different OpenSSL version that remained linked to SBC. The following error is shown: "''SBC logging without final state message.''"
:::'''Fixed:''' Note that you should only apply the following patch for your Univention system ≥ UCS 4.3 (not for regular Debian or any other Linux Distribution) and only if your backups are failing with the above error. The patch is available under https://download.sep.de/servicepacks/4.4.3/4.4.3.64/linux/ucs/ or directly by clicking  [https://download.sep.de/servicepacks/4.4.3/4.4.3.64/linux/ucs/sbc.gz UCS patch].
;SEP sesam v. 4.4.3.64 – Selective NDMP restore is taking very long:
:*Selective NDMP restore from tape is taking too long and may eventually fail with an error.
:::'''Workaround:''' SEP support is working on this issue and will provide  a fix as soon as possible. Please contact SEP sesam support at [mailto:support@sep.de support@sep.de] for assistance.
;SEP sesam v. 4.4.3.64 – Client SMS access settings are cleared on the Micro Focus Linux client after update to version 4.4.3.64:
:*If you open the properties of an already configured Micro Focus client with Linux OS and click ''OK'', Micro Focus Storage Management Services (SMS) access settings are cleared.
:::'''Workaround:''' In the client properties, select ''OES-Linux'' from the ''Operating system'' drop-down list and then re-enter and save the settings. SEP support is working on this issue and will provide a fix as soon as possible. 
::: '''Resolution:''' Fixed with service pack available under {{DDL|servicepacks/4.4.3/4.4.3.64/ (GUI)}}.
;SEP sesam v. 4.4.3.62 – When restoring a Hyper-V VM to a different hypervisor node, hypervisor system volume may get full due to temporarily stored files:
:*If you restore a Hyper-V VM to a different hypervisor node (other than original), then some data, such as memory files (''.vmrs''), is temporarily stored in the folder <tt><SEPsesam\var\tmp></tt> on the target hypervisor. In case of restoring a Hyper-V VM with large memory size (RAM), temporarily stored data may result in full hypervisor system volume.
:::'''Workaround:''' SEP support is working on this issue and will provide a solution as soon as possible. 
;SEP sesam Server v. 4.4.3.61/.62 – VMware mount/attach does not work with Windows data mover v. 4.4.3.48:
:*If SEP Server version is 4.4.3.61, but the Windows data mover is still 4.4.3.48, VMware mount/attach does not work.
:::'''Resolution:''' New backups can be mounted/attached without problems when both, the Windows data mover and SEP sesam Server have the same version – update the data mover to the same version as your SEP sesam Server!
;SEP sesam Server v. 4.4.3.61/.62 – VMware mount/attach does not work for incremental (INCR) backups performed with previous version:
:*If SEP Server version is 4.4.3.61 and INCR VMware backups have been performed with the previous SEP sesam version, attaching and mounting VMDK is not possible. The problem is that in the <tt>.lis</tt> file the date format of INCR savesets is incorrect, while ''sm_vfs'' expects a date and time greater than the time of the corresponding FULL backup.
:::'''Workaround:''' <ul>
:::<li>Please contact SEP sesam support at [mailto:support@sep.de support@sep.de] for assistance OR </li>
:::<li>Perform the following tasks manually to fix the date in the  <tt>.lis</tt> files: Delete all <tt>.lsl</tt> and <tt>.lst</tt> files. Then use a plain text editor, such as Notepad++, to modify the dates in all <tt>.lis</tt> files: Use Windows Explorer to navigate to ''lis'' folder and search for: ''*_V?201*.lis''. Select all found files and use the right mouse button to open them. Then find and replace (use ''Search > Replace'') the date "0000-00-00 00:00:00" with any real date, for example, "2018-01-01 01:01:01". In all subsequent INCR files there must be a time stamp that is more recent, e.g. "2018-01-01 01:01:02",  "2018-01-01 01:01:03"! </li> </ul>
;SEP sesam v. 4.4.3.56-4.4.3.62 – After the last Windows 10 update, system state restore fails to set standard attributes for Windows Defender files and directories:
:*After automatically updating Windows 10, system state restore finishes with warnings because standard attributes for Windows Defender files and directories are not set.   
:::'''Workaround:''' SEP support is working on this issue and will provide a solution as soon as possible.
;SEP sesam v. 4.4.2.xx and 4.4.3.xx – Restore of multiple Oracle archive log files from tape fails:
:*When restoring multiple Oracle archive log files that were written at different time intervals to the same tape, restore fails. The problems is that RMAN starts a restore for every Oracle log file with no drive number set, thus the restore job is submitted into queue manager without drive number, using different drives. Then restore requires a tape which is already mounted on another drive and, consequently, fails.  
:::'''Workaround:''' To ensure that only one tape drive is used during the backup, start the RMAN restore with only one drive by setting the value of <tt>SESAM_DRIVE</tt>.
}}
{{Box Hint|{{anchor|fixed}}Fixed with [https://download.sep.de/ SEP sesam Server 4.4.3.64 SP2]|
For the whole set of solved issues, see [[Change_report_Grolar|Change report]].
;Multiple issues in master GUI table view:
:*In the 4.4.3.64 GUI with parameter -M1 only the master is shown in the table view. In the running messages and in the tree structure both servers are visible; switching between the servers does not show the correct results.
;In v. 4.4.3.57, migration using the same drive group and multiple drives in the group is no longer possible:
:*Media pools connected to the same drive group are filtered out from the target pool selection, therefore the migration using the same drive group is not possible.
;RHEV task type is not set when browsing for RHEV VM backup source:
:*When creating a backup task for RHEV VM and selecting a backup source by browsing, task type is incorrectly set to ''Path'' instead of ''RHEV'' automatically.
;SEP sesam v. 4.4.3.64 – Backups may fail with ''"Error reading SSH protocol banner"'':
:*In a high load environment with many backups running simultaneously, backups may fail with ''"Error reading SSH protocol banner"''.  This happens when the default access mode ''SM_SSH'' is used and SEP sesam Server cannot connect to RDS due to limited allowed connections.
;SEP sesam v. 4.4.3.56-4.4.3.64 – Windows system state backup fails sporadically:
:* Sometimes the system state backup ends with ''[BackupProcessing: For the specified backup source no volumes could be determined. Sources - system_state]''.
}}
{{Box Hint|{{anchor|fixed}}Fixed with [https://download.sep.de/ SEP sesam Server 4.4.3.64 SP1]|
For the whole set of solved issues, see [[Change_report_Grolar|Change report]].
;SEP sesam v. ≤ 4.4.3.62 – (''CVE-2018-1000805'') ''Paramiko'' contains a Incorrect Access Control vulnerability in SSH server that can result in Remote Code Execution (RCE):
:*SEP sesam uses ''Paramiko'' for the SM_SSH access mode. ''Paramiko'' contains a Incorrect Access Control vulnerability in SSH server that can result in RCE. This attack appear to be exploitable via network connectivity. The vendor has confirmed the vulnerability; it relates to Paramiko versions 2.4.1, 2.3.2, 2.2.3, 2.1.5, 2.0.8, 1.18.5, 1.17.6. This issue is listed as ''CVE-2018-1000805'' in the MITRE CVE dictionary and in the [https://nvd.nist.gov/vuln/detail/CVE-2018-1000805 NIST NVD].
:::'''Fixed:''' With version [http://www.paramiko.org/changelog.html ''Paramiko 2.4.2''] included in SEP sesam v. 4.4.3.64.
;SEP sesam v. 4.4.3.62 – After upgrading SEP sesam to v. 4.4.3.62, backup of CIFS shares ending with <tt>$</tt>, e.g., <tt>//win-server/D$</tt>, does not work:
:*After installing the update 4.4.3.62, backing up CIFS shares with path <tt>//path</tt> ending with <tt>$</tt>, e.g., backup source <tt>//win-server/D$</tt>, no longer works as it is passed as URI encoded. Backup of CIFS shares without the <tt>$</tt> character works without problems because it does not contain any special characters.
;SEP sesam v. 4.4.3.60-4.4.3.62 – Restore from tape takes a long time or may be aborted due to positioning of the tape taking too long:
:*As of 4.4.3.60 Grolar, SEP sesam does not use fast forward (fast positioning) to the file mark where the saveset is stored on tape; instead the tape is read from the beginning which causes the restore process to take longer or the restore timed out.
}}
{{Box Hint|Fixed with [https://download.sep.de/ SEP sesam version 4.4.3.62]|
;SEP sesam v. ≤ 4.4.3.61 – (''CVE-2018-7750'') ''Paramiko transport.py'' authentication bypass in the SSH Server functionality; possible security risk because SM_SSH access mode uses weak ciphers:
:*SEP sesam uses ''Paramiko transport.py'' for the SM_SSH access mode. A vulnerability in ''Paramiko transport.py'' could allow unauthorized access to SEP sesam because ''transport.py'' in the SSH server implementation of Paramiko before 1.17.6, 1.18.x before 1.18.5, 2.0.x before 2.0.8, 2.1.x before 2.1.5, 2.2.x before 2.2.3, 2.3.x before 2.3.2, and 2.4.x before 2.4.1 does not properly check whether authentication is completed before processing other requests. A customized SSH client can simply skip the authentication step. By using a customized SSH client, an attacker can skip the authentication step and gain unauthorized access to resources on the SEP sesam system. This issue is listed as ''CVE-2018-7750'' in the MITRE CVE dictionary and in the [https://nvd.nist.gov/vuln/detail/CVE-2018-7750 NIST NVD]. 
:*Weak ciphers/MAC are available for connection with SM_SSH access. 
:::'''Fixed:''' New python ''paramiko'' module solves issues with unauthorized access and weak ciphers. Update all SEP sesam Clients, SEP sesam Servers and Remote Device Servers to SEP sesam version 4.4.3.62 ''Grolar''.
;SEP sesam v. 4.4.61 – When using the ''Browser'' button to select a new NDMP target restore volume/directory, NetApp NDMP restore does not restore to the specified restore target, but restores data to the original volume instead:
:*When using the ''Browser'' button to find the target directory/volume for restore, the target path for NetApp NDMP restore is incorrectly specified with prefix ''NDMP:'', which leads to relocation source. Consequently, the data is restored to the original volume instead to the specified target. Note that entering the target restore path manually in the field correctly restores data to the specified target.    
;SEP sesam v. 4.4.3.61 – Citrix XenServer new FULL/DIFF/INCR backup levels with CBT  do not handle correctly the master/slave configuration:
:*After update, Citrix XEN module supports FULL/DIFF/INCR backup levels with CBT but this new feature does not handle master/slave configuration. '''Note''': In 4.4.3.61 the backup worked if the task was configured for the master system, but it did not work if configured for the slave.
;SEP sesam v. 4.4.3.61 – SEP sesam default access mode SM_SSH converts UTF-8 characters to a non-UTF-8 locale which can result in data loss:
:*Due to newly introduced default SM_SSH access mode, SEP sesam installations with special backup source encoding (e.g., a multi-byte character set such as Chinese or Japanese) may face issues due to incorrect conversion of UTF-8 characters to a non-UTF-8 local encoding which does not provide the required characters. Such conversion may result in data loss. 
:::'''Fixed:''' Special characters are transferred with URI (Uniform Resource Indicator) encoding.
;SEP sesam v. 4.4.3.61 – Browsing RHV/RHEV does not work :
:* Browsing the RHV management system fails with ''invalid AccessMode: PROXY''.
;SEP sesam v. 4.4.3.61 – No operations possible anymore with [[Special:MyLanguage/Licensing#SAP|SAP Business One license]]:
:*If the license used is ''SAP Business One'' and the drive is set to more than 1 stream in the database, then operations related to the drive are no longer possible.
;SEP sesam v. 4.4.3.60 – BSR Pro backup fails:
:*BSR Pro backup fails with ''BSR Pro unknown return code (0X1)''. On some Windows OS (mainly Windows Server 2008 [R2]) this error could happen due to problems when checking the areas that are not to be compressed. 
:::'''Fixed:''' With version ''BSR Pro 3.3.185''.
;SEP sesam v. 4.4.3.56/4.4.3.59 (beta) – After upgrading to Windows server 2016, Windows restore fails:
:*On Windows 2016, the UTF-8 conversion fails when restoring a file with invalid character, e.g., <tt>C:\Windows\System32\LogFiles\Sum\<invalid_character></tt>; consequently, the restore fails. This issue is caused by the Microsoft User Access Logging (UAL) (https://docs.microsoft.com/en-us/windows-server/administration/user-access-logging/manage-user-access-logging) that sometimes generates invalid filenames.
;SEP sesam v. 4.4.3.53 - Selective restore of NDMP saveset on NetApp via HTTP interface fails:
:*Selective restore failed because <tt>sbc_ndmp</tt> did not always process the HTTP buffers correctly. 
}}
{{Box Hint|Fixed with [https://download.sep.de/ SEP sesam Server 4.4.3.61]|
;SEP sesam v. 4.4.3.60 – Starting a command event by using ''Activities'' -> ''Immediate start'' button does not work:
:*Trying to start a command event from menu: ''Activities'' -> ''Immediate Start'' -> ''Command'' fails to open the dialog box and the command cannot be started manually.
;SEP sesam v. 4.4.3.60 – Windows Installation on x86 creates MSI Exception:
:* In case of Windows systems with x86 architecture an MSI exception appears in the event log during the update of the SEP sesam together with ''SEP sesam BSR Pro Windows'' installation; however, all sesam services are running and SEP sesam is working properly.
}}</onlyinclude>

===Limitations===
;SEP sesam backup for hypervisors (VMware, Hyper-V, Citrix Xen, KVM, OpenNebula) cannot back up the data on external disks: 
The data of such disks is silently skipped from backup, hence the backup saveset contains no data for the external disk while the backup succeeds and no warning about the missing data is issued (except for VMware, see below). 
:*In case of VMware, SEP sesam cannot back up the data on the independent or Raw Device Mapping (RDM) disks due to a [https://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vsphere.vm_admin.doc_50%2FGUID-53F65726-A23B-4CF0-A7D5-48E584B88613.html VMware limitation] that does not support including independent/RDM disks in virtual machine snapshots. As of ''Grolar'', SEP sesam issues a warning about the missing data for VMware independent/RDM disk. To avoid the warnings and have a successful backup, you should exclude the independent disks/RDMs from the backup task or install a SEP sesam Client in the virtual machine and perform an additional file or application backup to back up this data.  
:*In case of other hypevisors (Hyper-V, Citrix Xen, KVM, OpenNebula), SEP sesam cannot back up the data on the RDM disks or on a VM without attached SCSI controller(s). To back these hypervisors, you have to add one or more SCSI controller to the virtual machine before performing a backup, even if there are no devices to use the SCSI, or you have to install a SEP sesam Client in the virtual machine and perform an additional file or application backup to back up this data.     
{{warning|If a restore of a VM with external disk is performed to the original VM by using the option ''overwrite'', the disk is re-created and all existing data on the restore target is lost.}}
;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. 
:*Reconfigure your old ''disk_info'' Linux backup tasks by selecting the ''Linux BSR'' as a [[Special:MyLanguage/SEP_sesam_Glossary#task_type|task type]] in the task properties or create new backup tasks with type ''Linux BSR''. For details, see [[Disaster_Recovery_for_Linux_3.0_en|Disaster Recovery for Linux 3.0]]. 
{{warning|SEP AG is not responsible for potential data loss that may occur as a result of backing up data with unsupported backup task.}}
;BSR Pro ''Direct forensic'' imaging method does not work with SEP sesam versions [[SEP_sesam_Release_Versions|Tigon V2 and Grolar]]:
BSR Pro ''Direct forensic'' imaging method is only possible if a special snapshot driver is installed and the system is rebooted after installation. It is otherwise not possible to create a consistent image. 
:*The existing ''BSR Pro'' installation package containing the driver is stored in the {{Path|<SESAM_BIN>/skel}} directory. Follow the steps for installing additional driver as described in [[Special:MyLanguage/4_4_3_Tigon:SEP_sesam_BSR_Pro_–_Backup_Configuration#driver|Steps for using Direct forensic option]].

== {{anchor|enhancements}}Enhancements and changes ==

==={{anchor|Kopano}}Kopano differential backup===

In addition to previously existing ''COPY'' backup level, backup levels ''FULL'' and ''DIFF'' are supported  for Kopano backup with SEP sesam ''Grolar'' SP2. For details, see [[Special:MyLanguage/4_4_3_Tigon:Kopano_Backup|Kopano Backup]].

==={{anchor|EOL}}EOL-related changes=== 

*It is now possible to enable extended retention period of another media pool for migrated savesets by using a specific GLBV. For details, see [[Special:MyLanguage/Managing_EOL#EOL_migration|Managing EOL]].   
*Every time EOL is modified, corresponding information is shown in the main log. See [[Special:MyLanguage/Managing_EOL#automated_EOL|Automated EOL adjustment]]. 

==={{anchor|S3}}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 [[Special:MyLanguage/4_4_3_Grolar:S3_Cloud_Storage_Backup|S3 Cloud Storage Backup]].

==={{anchor|NetApp}}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 [[Special:MyLanguage/4_4_3_Grolar:NetApp_Storage_Snapshots_Backup|NetApp Storage Snapshots Backup]].

==={{anchor|Hyper-V}}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 [[Special:MyLanguage/4_4_3_Grolar:Hyper-V_Backup|Hyper-V Backup]].
;Single item restore for Hyper-V: Now you can restore single items from Hyper-V FULL backups if the saveset is stored on a data store or Si3 deduplication store. For details, see [[Special:MyLanguage/4_4_3_Grolar:Hyper-V_Restore##single_file|Hyper-V Restore]].

==={{anchor|Citrix}}Changed block tracking (CBT) support for Citrix XenServer 7.3: Citrix XenServer new backup levels===

SEP sesam introduces support for the XenServer changed block tracking feature (CBT) that offers incremental backup capabilities; hence, new [[Special:MyLanguage/SEP_sesam_Glossary#backup_level|backup levels]] (''FULL'', ''INC'' and ''DIFF'') are available for Citrix XenServer backups. For details, see [[Special:MyLanguage/5_0_0:Citrix_XenServer_Backup|Citrix XenServer Backup]]. 

==={{anchor|ACL}}Access control lists (ACLs)===

The administrators can configure ACLs to enable or disable access to [[Special:MyLanguage/SEP_sesam_Glossary#location|location]] (group of clients) or specific [[Special:MyLanguage/SEP_sesam_Glossary#SBC|client]]. Note that before configuring ACLs, database-based authentication must be activated and users configured and added to the relevant group. For details, see [[Special:MyLanguage/4_4_3_Grolar:Using_Access_Control_Lists|Using Access Control Lists]].

==={{anchor|DAR}}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 [[Special:MyLanguage/4_4_3_Grolar:NDMP_Backup|NDMP Backup]]. 

==={{anchor|assistant}}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 [[Special:MyLanguage/4_4_3_Grolar:Self-Service_Restore_Assistant|Self-Service Restore Assistant]].

==={{anchor|access_mode}}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 include <tt>libmicrohttpd</tt>, <tt>libcurl</tt>, and <tt>libopenssl</tt>. <br />Note that it is strongly recommended to use the default ''SM_SSH'' instead of ''CTRL'' access mode whenever possible.

==={{anchor|improved}}Improved functionality===
*Exclude processing for Windows VSS writers is improved. If you have an issue with backing up your data using snapshot technology, you can exclude a specific VSS writer from being used during a snapshot. For details, see [[SEP_sesam_Volume_Shadow_Copy_Service_(VSS)_for_Windows#exclude|Manually excluding a VSS writer from backup]].
*The '''Mount saveset''' feature for single file restore has been improved and now supports mounting folders and files containing umlauts (ä, ü, ö, ...). For details on mounting a saveset, see [[Special:MyLanguage/Cross-Platform_Recovery_File_System_Layer|Option Mount saveset – Cross-Platform Recovery File System Layer]]. 

==={{anchor|GUI}}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 [[Special:MyLanguage/Configuring_a_Data_Store|Configuring a Data Store]] and [[Special:MyLanguage/4_4_3_Grolar:Configuring_Si3_Deduplication_Store|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. For details, see [[4_4_3_Grolar:About_Authentication_and_Authorization|About Authentication and Authorization]], [[4_4_3_Grolar:Configuring_LDAP/AD_Authentication|Configuring LDAP/AD Authentication]], and [[4_4_3_Grolar:Configuring_Database-Based_Authentication|Configuring Database-Based Authentication]].
*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 [[Special:MyLanguage/Configuration_4.4#Grolar|UI Mode]].
*A force refresh can be used to clear the GUI cache memory and consequently to update the view. For details, see [[Special:MyLanguage/All_Results_by_State_4.4|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 [[Special:MyLanguage/4_4_3_Grolar:Disabling_and_Enabling_Backup_Task|Disabling and Enabling Backup Task]] and [[Special:MyLanguage/4_4_3_Grolar:Disabling_and_Enabling_Task_Group|Disabling and Enabling Task Group]].
*New ''Manage multiple drives'' option is introduced to enable you to easier change drives properties (e.g., maximum number of parallel streams (max channels), delete drives, create new drives, etc). It lists all configured drives and allows you to change the properties settings of multiple drives, after which SEP sesam restarts the drives automatically. For details, see [[Special:MyLanguage/Drives_4.4#multiple|Manage multiple drives]]. Now it is also possible to reconfigure all drives by using ''Configure all drives'' option.

==={{anchor|license}}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'

== {{anchor|end}}End of maintenance and support ==
=== Unsupported SEP sesam Server OS ===
<!-- No changes since [[Release_Notes_4.4.3_Tigon_v.2#end|SEP sesam version 4.4.3 ''Tigon'' V2]]. -->
The following operating systems are no longer supported for SEP sesam Server:
<Ul><li>Ubuntu 14.04</li>

<li>Windows Server 2008 [[File:win7.gif]]</li>
{{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_OS_and_Database_Support_Matrix|SEP sesam support matrix]].}}</ul>
For a complete list of supported SEP sesam clients, see [[SEP_sesam_OS_and_database_support_matrix_4.4| SEP sesam Support Matrix]].
<!-- 
=== <span style="color:darkgreen">Unsupported OS</span> ===
The following operating systems are no longer supported:
* Windows 2008 [[File:win7.gif]]
'''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_OS_and_database_support_matrix_4.4| SEP sesam Support Matrix]].
-->

== {{anchor|changes}}Major fixes and changes ==

SEP AG recommends that you update to latest Grolar version 4.4.3.64. 

There are service packs available at {{DDL|servicepacks/4.4.3/4.4.3.64/}}. These patches provide necessary fixes for 
* GUI issues 
* Common issues
* Windows specific backup and restore problems -> download {{DDL|servicepacks/4.4.3/4.4.3.64/windows/}}.
* Sesam Loader Utility (SLU): Added support for tape encryption for LTO-8 and LTO-M8 

See [[Change report Grolar]] for major fixes and changes. See all changes at [https://download.sep.de/changes/ SEP sesam download – changes].

== See also ==
[[SEP_sesam_Release_Versions|SEP sesam Release Versions]]

[[Category:4.4.3 Grolar]]