Difference between revisions of "Release Notes 4.4.3"

From SEPsesam
Jump to: navigation, search
(Fixed broken link.)
(Added limitations for hypervisors.)
 
(12 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
{{Copyright SEP AG en}}
 
{{Copyright SEP AG en}}
<!-- SEP AG is pleased to announce the beta release of SEP sesam 4.4.3. 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]]. -->
+
<!-- SEP AG is pleased to announce the beta release of SEP sesam 4.4.3. 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]]. -->{{Navigation_previous|link=[[Release_Notes|latest Release Notes]]}}
  
 
== {{anchor|new}}What's new in SEP sesam v. 4.4.3 ==
 
== {{anchor|new}}What's new in SEP sesam v. 4.4.3 ==
Line 7: Line 7:
 
{|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:SEP Tip.png|45px|link=]]
 
| 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;" |What's new in the upcoming release? Check the [[Release Notes 4.4.3 Tigon|Release Notes 4.4.3 ''Tigon'']].
+
| 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>
 
|}</div>
 
SEP sesam introduces '''[[SEP_sesam_Dashboard|web dashboard]]''' – an easy-to-use online monitoring tool that constantly tracks SEP sesam operations and their state and provides key metrics of your backup environment. Two new modules are introduced: '''[[Jira Backup Module|JIRA backup module]]''' and '''[[RHEV_backup|SEP sesam Red Hat Virtualization (RHV) backup module]]'''.
 
SEP sesam introduces '''[[SEP_sesam_Dashboard|web dashboard]]''' – an easy-to-use online monitoring tool that constantly tracks SEP sesam operations and their state and provides key metrics of your backup environment. Two new modules are introduced: '''[[Jira Backup Module|JIRA backup module]]''' and '''[[RHEV_backup|SEP sesam Red Hat Virtualization (RHV) backup module]]'''.
Line 15: Line 15:
 
A hybrid of both, target-based (Si3T) and newly introduced '''[[Source_Side_Dedup|source-side deduplication]]''' (Si3S) is now available. GUI is enhanced with '''flexible scheduling''' that may prevent scheduled jobs from running during holidays by using [[Creating Custom Calendar|user defined]] option.
 
A hybrid of both, target-based (Si3T) and newly introduced '''[[Source_Side_Dedup|source-side deduplication]]''' (Si3S) is now available. GUI is enhanced with '''flexible scheduling''' that may prevent scheduled jobs from running during holidays by using [[Creating Custom Calendar|user defined]] option.
  
Storage file servers can be efficiently protected by new '''[[NDMP Backup|NDMP backup]]'''. Additionally, SEP sesam '''[[HSM-aware_Backup_for_Windows|HSM-aware backup for Windows]]''' is included in SEP sesam package. For details on all changes, see [[#Enhancements and Changes|Enhancements and Changes]].
+
Storage file servers can be efficiently protected by new '''[[4_4_3:NDMP_Backup|NDMP backup]]'''. Additionally, SEP sesam '''[[HSM-aware_Backup_for_Windows|HSM-aware backup for Windows]]''' is included in SEP sesam package. For details on all changes, see [[#Enhancements and Changes|Enhancements and Changes]].
  
 
==={{anchor|requirements}}SEP sesam Server requirements===
 
==={{anchor|requirements}}SEP sesam Server requirements===
Line 31: Line 31:
 
* SEP sesam 4.4.3.28 [http://download.sep.de/linux Linux] [[File:tux.gif]] – released: March 15th, 2017.
 
* SEP sesam 4.4.3.28 [http://download.sep.de/linux Linux] [[File:tux.gif]] – released: March 15th, 2017.
 
* SEP sesam 4.4.3.28 [http://download.sep.de/windows Windows] [[File:win7.gif]] – released: March 15th, 2017.
 
* SEP sesam 4.4.3.28 [http://download.sep.de/windows Windows] [[File:win7.gif]] – released: March 15th, 2017.
* SEP sesam 4.4.3.25 [http://download.sep.de/linux Linux] [[File:tux.gif]] – released: Dectember 7th, 2016.
+
* SEP sesam 4.4.3.25 [http://download.sep.de/linux Linux] [[File:tux.gif]] – released: December 7th, 2016.
 
* SEP sesam 4.4.3.25 [http://download.sep.de/windows Windows] [[File:win7.gif]] – released: December 7th, 2016.
 
* SEP sesam 4.4.3.25 [http://download.sep.de/windows Windows] [[File:win7.gif]] – released: December 7th, 2016.
 
* SEP sesam 4.4.3.22 [http://download.sep.de/testing/linux Linux] [[File:tux.gif]] – released: September 21st, 2016.
 
* SEP sesam 4.4.3.22 [http://download.sep.de/testing/linux Linux] [[File:tux.gif]] – released: September 21st, 2016.
Line 44: Line 44:
 
The 4.4.3 '''installation package on Windows''' also includes:
 
The 4.4.3 '''installation package on Windows''' also includes:
 
* ''VMware® Virtual Disk Development Kit (VDDK) version 6.0.2'' for Windows.
 
* ''VMware® Virtual Disk Development Kit (VDDK) version 6.0.2'' for Windows.
* New ''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 [[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.}}  
+
* New ''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.}}  
  
 
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| Automatic Installation on Windows]].
 
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| Automatic Installation on Windows]].
Line 55: Line 55:
 
{{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 known issues|
 
{{Box Hint Y|4.4.3 known issues|
<!--
+
;SEP sesam version 4.4.3.22 – SEP sesam backup for hypervisors (VMware, Hyper-V, Citrix XEN, KVM, OpenNebula) cannot back up the data on the independent disks or Raw Device Mapping (RDM) disks:
;SEP sesam version 4.4.3.25 - Migration of DIFF/INCR backups ends with warning if referenced migrated save set is also replicated:
+
:*When backing up via hypervisor and using external disk, SEP sesam cannot back up the data on the independent or RDM disks, because hypervisors are not able to back up such devices. The data of such disks is silently skipped from backup, hence the backup saveset contains no data for the independent or RDM disks while the backup succeeds and no warning about the missing data is issued. If a restore of a VM with independent/RDM disk is performed to the original VM by using the option ''overwrite'', the independent/RDM disk is re-created and all existing data on the restore target is lost.
:* In SEP sesam version 4.4.3.25 a migration of DIFF/INC R backup may end with warning if one of the referenced save sets was replicated.
+
::: '''Workaround:''' To back up virtual machines that contain independent disks and RDMs, you have to install the SEP sesam Client in the virtual machine and perform an additional file or application backup to back up this data.
:*::: '''Fixed:''' SEP sesam Server version 4.4.3.23. Install SEP sesam Server patch for v. 4.4.3.25 [https://download.sep.de/servicepacks/4.4.3/ 4.4.3 service packs].
+
;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 v. 4.4.3.xx – Throughput for local backups is very low:
 
;SEP sesam v. 4.4.3.xx – 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.   
 
:* 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.   
Line 78: Line 79:
 
:* '''Fixed:''' Service pack is available for Linux 4.4.3.25 at https://download.sep.de/servicepacks/4.4.3/4.4.3.25/linux/, for Windows 4.4.3.25 at https://download.sep.de/servicepacks/4.4.3/windows/x64/4.4.3.25/sesam_ae858a3_x64_win-4.4.3.25.exe. Additionally, you should manually resolve a conflict between the multiple identical labels to prevent the newly written backup data to be overwritten. For details, see [[Checking and Labeling Tape Media]].
 
:* '''Fixed:''' Service pack is available for Linux 4.4.3.25 at https://download.sep.de/servicepacks/4.4.3/4.4.3.25/linux/, for Windows 4.4.3.25 at https://download.sep.de/servicepacks/4.4.3/windows/x64/4.4.3.25/sesam_ae858a3_x64_win-4.4.3.25.exe. Additionally, you should manually resolve a conflict between the multiple identical labels to prevent the newly written backup data to be overwritten. For details, see [[Checking and Labeling Tape Media]].
  
;Reduced retention time (EOL) for a DIFF or INCR save set results in reduced retention time for a complete save set chain:   
+
;Reduced retention time (EOL) for a DIFF or INCR saveset results in reduced retention time for a complete saveset chain:   
:* If the [[SEP_sesam_Glossary#retention_time|retention time]] of a DIFF or INCR save set is changed to an'''''already expired time''''', the whole backup chain is affected and all save sets in this backup chain are set with the same expired [[SEP_sesam_Glossary#EOL|EOL]]. This may result in potential data loss because the FULL save set can also be purged and overwritten.  
+
:* If the [[SEP_sesam_Glossary#retention_time|retention time]] of a DIFF or INCR saveset is changed to an'''''already expired time''''', the whole backup chain is affected and all savesets in this backup chain areset with the same expired [[SEP_sesam_Glossary#EOL|EOL]]. This may result in potential data loss because the FULL saveset can also be purged and overwritten.  
:*::: '''Workaround:''' To avoid data loss and ensure that a FULL save set is retained for the expected retention time, do not change the EOL of a DIFF or INCR save set to already expired time.
+
:*::: '''Workaround:''' To avoid data loss and ensure that a FULL saveset is retained for the expected retention time, do not change the EOL of a DIFF or INCR saveset to already expired time.
  
 
;A new drive cannot be configured for a loader:  
 
;A new drive cannot be configured for a loader:  
Line 104: Line 105:
 
;''SEP sesam version 4.4.3.22'' – When running source-side deduplication, no backup throughput is displayed in the GUI:
 
;''SEP sesam version 4.4.3.22'' – When running source-side deduplication, no backup throughput is displayed in the GUI:
 
:* When source-side deduplication is used, the backup throughput is not shown in the GUI even though the job has finished successfully.
 
:* When source-side deduplication is used, the backup throughput is not shown in the GUI even though the job has finished successfully.
<!-- :*::: '''Workaround:''' To make sure that your backup job has successfully finished, check the state of each particular save set. -->
+
<!-- :*::: '''Workaround:''' To make sure that your backup job has successfully finished, check the state of each particular saveset. -->
  
 
;''SEP sesam version 4.4.3.22'' – Running concurrent restores may fail:
 
;''SEP sesam version 4.4.3.22'' – Running concurrent restores may fail:
:* Running multiple restores in parallel may fail for some configurations, for example for multiple vSphere or Hyper-V restores that are started from the same save set.
+
:* Running multiple restores in parallel may fail for some configurations, for example for multiple vSphere or Hyper-V restores that are started from the same saveset.
 
:*::: '''Workaround:''' Do not run vSphere and Hyper-V restores that are using the same source simultaneously.
 
:*::: '''Workaround:''' Do not run vSphere and Hyper-V restores that are using the same source simultaneously.
  
Line 116: Line 117:
 
;''SEP sesam version 4.4.3.22'' – Replication job state may be incorrect:
 
;''SEP sesam version 4.4.3.22'' – Replication job state may be incorrect:
 
:*SEP sesam erroneously uses the state of the first started child task as a state for the parent replication task too, even though the other tasks might have failed, are queued or still active.
 
:*SEP sesam erroneously uses the state of the first started child task as a state for the parent replication task too, even though the other tasks might have failed, are queued or still active.
:*::: '''Workaround:''' To make sure that your replication job has successfully finished, check the replication state of each particular save set.
+
:*::: '''Workaround:''' To make sure that your replication job has successfully finished, check the replication state of each particular saveset.
  
 
;''Upgrade to SEP sesam version 4.4.3.22'' – Java upgrade to 1.8 not possible if ''SEP sesam BSR Pro for Windows'' is installed:
 
;''Upgrade to SEP sesam version 4.4.3.22'' – Java upgrade to 1.8 not possible if ''SEP sesam BSR Pro for Windows'' is installed:
Line 125: Line 126:
 
:* SEP sesam package for Windows includes  ''Callback File System® (CBFS®) version 6.1.181'' from EldoS Corporation. 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'''.
 
:* SEP sesam package for Windows includes  ''Callback File System® (CBFS®) version 6.1.181'' from EldoS Corporation. 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'''.
 
}}
 
}}
 
 
 
{{Box Hint|Fixed with [https://download.sep.de/ SEP sesam Server version 4.4.3.25]|
 
{{Box Hint|Fixed with [https://download.sep.de/ SEP sesam Server version 4.4.3.25]|
 
;Installation/upgrade does not work with IBM Java included in SLES:
 
;Installation/upgrade does not work with IBM Java included in SLES:
Line 137: Line 136:
 
:* '''Fixed:''' SEP sesam Server version 4.4.3.25. For 4.4.3.22 version, SEP sesam Server/RDS patch  –service pack for <tt>sms</tt> is available at [https://download.sep.de/servicepacks/4.4.3/ 4.4.3 service packs]. This patch prevents the MTF stream check from aborting the backup<!-- while recording the MTF format issues in the STPD log-->.
 
:* '''Fixed:''' SEP sesam Server version 4.4.3.25. For 4.4.3.22 version, SEP sesam Server/RDS patch  –service pack for <tt>sms</tt> is available at [https://download.sep.de/servicepacks/4.4.3/ 4.4.3 service packs]. This patch prevents the MTF stream check from aborting the backup<!-- while recording the MTF format issues in the STPD log-->.
  
;''SEP sesam version 4.4.3.22'' – Removing an Si3 deduplication store used for replication marks the corresponding save sets as deleted:
+
;''SEP sesam version 4.4.3.22'' – Removing an Si3 deduplication store used for replication marks the corresponding savesets as deleted:
:* If an Si3 deduplication store, which is used for replication, is removed, the corresponding save sets from the related Si3 data store are set to partially deleted.
+
:* If an Si3 deduplication store, which is used for replication, is removed, the corresponding savesets from the related Si3 data store are set to partially deleted.
 
:* '''Fixed:''' SEP sesam Server version 4.4.3.25. For previous version, service pack for <tt>sm_arch</tt>is available at [https://download.sep.de/servicepacks/4.4.3/ 4.4.3 service packs].
 
:* '''Fixed:''' SEP sesam Server version 4.4.3.25. For previous version, service pack for <tt>sm_arch</tt>is available at [https://download.sep.de/servicepacks/4.4.3/ 4.4.3 service packs].
  
Line 154: Line 153:
  
 
;SEP sesam version 4.4.3.22 – Misleading/wrong summary in the state of a failed migration task:
 
;SEP sesam version 4.4.3.22 – Misleading/wrong summary in the state of a failed migration task:
:*If a migration event migrates a number of save sets and one of the jobs has failed, the migration state in the GUI shows only the successful migrations, while the failed one is not listed. However, the state of the main migration task is marked as failed even though all migrations except one were successful.
+
:*If a migration event migrates a number of savesets and one of the jobs has failed, the migration state in the GUI shows only the successful migrations, while the failed one is not listed. However, the state of the main migration task is marked as failed even though all migrations except one were successful.
 
:* '''Fixed:''' SEP sesam Server version 4.4.3.25.
 
:* '''Fixed:''' SEP sesam Server version 4.4.3.25.
  
Line 161: Line 160:
 
:* '''Fixed:''' SEP sesam Server version 4.4.3.25.
 
:* '''Fixed:''' SEP sesam Server version 4.4.3.25.
 
}}</onlyinclude>
 
}}</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.
 +
:*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. To 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.}}
  
 
== {{anchor|enhancements}}Enhancements and changes ==
 
== {{anchor|enhancements}}Enhancements and changes ==
Line 186: Line 192:
  
 
===NDMP===
 
===NDMP===
SEP sesam now supports Network Data Management Protocol (NDMP) (from SEP sesam version ≥ 4.4.2.87) with ''NDMP remote configuration'', based on ''version 4 of the NDMP protocol''. For details, see [[NDMP Backup]]. For a list of supported NAS appliances, see the [[SEP_sesam_OS_and_Database_Support_Matrix#NDMP| support matrix]]. With v. 4.4.3 the backup levels FULL, DIFF and INCREMENTAL are supported for NetApp Filers. A complete restore of the NAS appliance volume is supported to the original or different target. For details, see [[NDMP Restore]].
+
SEP sesam now supports Network Data Management Protocol (NDMP) (from SEP sesam version ≥ 4.4.2.87) with ''NDMP remote configuration'', based on ''version 4 of the NDMP protocol''. For details, see [[NDMP Backup]]. For a list of supported NAS appliances, see the [[SEP_sesam_OS_and_Database_Support_Matrix#NDMP| support matrix]]. With v. 4.4.3 the backup levels FULL, DIFF and INCREMENTAL are supported for NetApp Filers. A complete restore of the NAS appliance volume is supported to the original or different target. For details, see [[4_4_3:NDMP_Restore|NDMP Restore]].
  
 
===JIRA backup add-on===
 
===JIRA backup add-on===
Line 220: Line 226:
  
 
===Bare Metal Recovery Windows===
 
===Bare Metal Recovery Windows===
[[SEP_sesam_BSR_for_Windows | Bare Metal Recovery Windows]] has improved restore performance when using ''[[4_4_3:Recovering_Windows_Using_SEP_sesam_BSR_Pro#Recovery_procedure|BSR Pro Quick-Start]]'' recovery option. The writing of the save set data into a temporary file can now be avoided.
+
[[SEP_sesam_BSR_Pro_for_Windows|Bare Metal Recovery Windows]] has improved restore performance when using ''[[4_4_3:Recovering_Windows_Using_SEP_sesam_BSR_Pro#Recovery_procedure|BSR Pro Quick-Start]]'' recovery option. The writing of the saveset data into a temporary file can now be avoided.
  
 
===Bare Metal Recovery Linux===
 
===Bare Metal Recovery Linux===
Line 242: Line 248:
  
 
===''Exchange Recovery Pro'' – email recovery from VMDK===
 
===''Exchange Recovery Pro'' – email recovery from VMDK===
SEP sesam ''Exchange Recovery Pro'' now allows to recover MS Exchange Server emails from a VMware backup. The VMDK disk file is mounted from either COPY or FULL save set and incorporates changes from a chain of consequent DIFF or INCREMENTAL backup save sets (based on Changed Block Tracking (CBT), see [[VMware Backup]] for details).
+
SEP sesam ''Exchange Recovery Pro'' now allows to recover MS Exchange Server emails from a VMware backup. The VMDK disk file is mounted from either COPY or FULL saveset and incorporates changes from a chain of consequent DIFF or INCREMENTAL backup savesets (based on Changed Block Tracking (CBT), see [[VMware Backup]] for details).
  
 
=== GUI enhancements===  
 
=== GUI enhancements===  
 
<!-- Description or list of any changes in GUI -->
 
<!-- Description or list of any changes in GUI -->
 
;Flexible scheduling:Scheduling is enhanced with new options: ''User defined'' option allows you to create a custom calendar according to your country or company specific requirements. For example, you can define a calendar with '''specific days on which you want to perform special job executions''', such as backup and migration. You can also define '''specific dates to be excluded''' from individual schedules, set up a custom calendar of public holiday dates for each year, and '''stop scheduled jobs from running during holidays'''. For details, see [[Creating Custom Calendar]]. <br />The ''Repeat task'' option allows you to specify the '''repetition cycle for the task'''. The task will run, wait for the time interval specified, and then run again. This cycle will continue for as long it is specified by the ''duration time''.<br /> You are also able to '''prevent tasks to be run for too long''' by using the option ''Stop task if runs longer than'' and setting a time limit for the amount of time a task is allowed to run. For details on new scheduling options, see [[Creating_a_Schedule|Creating a schedule]].
 
;Flexible scheduling:Scheduling is enhanced with new options: ''User defined'' option allows you to create a custom calendar according to your country or company specific requirements. For example, you can define a calendar with '''specific days on which you want to perform special job executions''', such as backup and migration. You can also define '''specific dates to be excluded''' from individual schedules, set up a custom calendar of public holiday dates for each year, and '''stop scheduled jobs from running during holidays'''. For details, see [[Creating Custom Calendar]]. <br />The ''Repeat task'' option allows you to specify the '''repetition cycle for the task'''. The task will run, wait for the time interval specified, and then run again. This cycle will continue for as long it is specified by the ''duration time''.<br /> You are also able to '''prevent tasks to be run for too long''' by using the option ''Stop task if runs longer than'' and setting a time limit for the amount of time a task is allowed to run. For details on new scheduling options, see [[Creating_a_Schedule|Creating a schedule]].
;Follow-up events:This handy feature can ease your data protection administration by configuring events that are triggered on the SEP sesam Server once the initial event has completed. You can set up a migration, a save set verify and other actions to be triggered immediately after a backup or other event is completed. For details, see [[Follow-up Events]].
+
;Follow-up events:This handy feature can ease your data protection administration by configuring events that are triggered on the SEP sesam Server once the initial event has completed. You can set up a migration, a saveset verify and other actions to be triggered immediately after a backup or other event is completed. For details, see [[Follow-up Events]].
 
;Overview of all configured events:The ''Schedules'' component of the GUI navigation pane provides a new sub-menu ''Events as List''. This overview shows a '''list of all configured events with details''' for each listed event, including event ID, related task, related schedule, event priority, target media pool, drive number, interface, follow-up events and the time of the next execution. For details, see [[Events_as_list_4.4|Events as list]].
 
;Overview of all configured events:The ''Schedules'' component of the GUI navigation pane provides a new sub-menu ''Events as List''. This overview shows a '''list of all configured events with details''' for each listed event, including event ID, related task, related schedule, event priority, target media pool, drive number, interface, follow-up events and the time of the next execution. For details, see [[Events_as_list_4.4|Events as list]].
  
Line 276: Line 282:
 
== {{anchor|changes}}Major fixes and changes ==
 
== {{anchor|changes}}Major fixes and changes ==
 
For a complete list of GIT change reports, see [http://download.sep.de/changes changes].
 
For a complete list of GIT change reports, see [http://download.sep.de/changes changes].
 +
 +
== See also ==
 +
 +
[[SEP_sesam_Release_Versions|SEP sesam Release Versions]]

Latest revision as of 12:32, 28 June 2018

Copyright © SEP AG 1999-2018. All rights reserved.

Any form of reproduction of the contents or parts of this manual is allowed only with the express written permission from SEP AG. When compiling and designing user documentation SEP AG uses great diligence and attempts to deliver accurate and correct information. However, SEP AG cannot issue a guarantee for the contents of this manual.

Icon archived docs.png This is not the latest version of SEP sesam documentation and, as such, does not provide information on features introduced in the latest release. For more information on SEP sesam releases, see SEP sesam Release Versions. For the latest documentation, check latest Release Notes.


What's new in SEP sesam v. 4.4.3

SEP sesam introduces web dashboard – an easy-to-use online monitoring tool that constantly tracks SEP sesam operations and their state and provides key metrics of your backup environment. Two new modules are introduced: JIRA backup module and SEP sesam Red Hat Virtualization (RHV) backup module.

Enhanced VMware vSphere CBT backup can now use Si3 target deduplication and can be used for different types of restore and recovery. Incremental (INCR) backups are introduced for Hyper-V virtual machines. Fine-tuning Exchange Server DAG backup includes dynamical DAG host selection and selection of the appropriate database copy mode.

A hybrid of both, target-based (Si3T) and newly introduced source-side deduplication (Si3S) is now available. GUI is enhanced with flexible scheduling that may prevent scheduled jobs from running during holidays by using user defined option.

Storage file servers can be efficiently protected by new NDMP backup. Additionally, SEP sesam HSM-aware backup for Windows is included in SEP sesam package. For details on all changes, see Enhancements and Changes.

SEP sesam Server requirements

Java 8
SEP sesam Windows Server and GUI require Java 8 to work properly. Other operating systems require Java 7. For details, see Java Compatibility Matrix.
JavaFX
Additionally, JavaFX is required for the new 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 OS required
SEP sesam Server requires a 64-bit OS.

Installation and upgrades

SEP sesam 4.4.3 was released on September 21st, 2016. Direct upgrade for versions 3.6/4.x to version 4.4.3 is supported. Latest released versions are:

  • SEP sesam 4.4.3.29 Linux Tux.gif – released: April 4th, 2017.
  • SEP sesam 4.4.3.29 Windows Win7.gif – released: April 4th, 2017.
Tux.gif Linux specific

As of SEP sesam version ≥ 4.4.3.25, special service pack executables are available for Linux systems to ease the installation of service packs and patches. For details, see Applying Service Packs on Linux.

Win7.gif Windows specific

The 4.4.3 installation package on Windows also includes:

  • VMware® Virtual Disk Development Kit (VDDK) version 6.0.2 for Windows.
  • New 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 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.

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.

Former 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 known issues:
SEP sesam version ≥ 4.4.3.22 – SEP sesam backup for hypervisors (VMware, Hyper-V, Citrix XEN, KVM, OpenNebula) cannot back up the data on the independent disks or Raw Device Mapping (RDM) disks
  • When backing up via hypervisor and using external disk, SEP sesam cannot back up the data on the independent or RDM disks, because hypervisors are not able to back up such devices. The data of such disks is silently skipped from backup, hence the backup saveset contains no data for the independent or RDM disks while the backup succeeds and no warning about the missing data is issued. If a restore of a VM with independent/RDM disk is performed to the original VM by using the option overwrite, the independent/RDM disk is re-created and all existing data on the restore target is lost.
Workaround: To back up virtual machines that contain independent disks and RDMs, you have to install the SEP sesam Client in the virtual machine and perform an additional file or application backup to back up this data.
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 Creating a migration task.
SEP sesam v. 4.4.3.xx – 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.
    Resolve: Check the local loopback MTU size by using ifconfig lo, set the MTU size to 16K (ifconfig lo mtu 16384), and add or change MTU=16384 in /etc/sysconfig/network/ifcfg-lo for SLES12. For example, see FAQ.
SEP sesam v. 4.4.3.28 – The SEP sesam loader utility (slu) does not recognize tapes in ports
  • In SEP sesam version 4.4.3.28, it may happen that slu does not recognize tapes in ports because it requires the accessible flags for IE and MTE elements.
  • Fixed: Hotfix considers all ports as accessible.
SEP sesam v. 4.4.3.28 – The SEP sesam loader utility (slu) may report incorrect status
License violation due to the changed measurement unit from TiB to TB
  • In previous SEP sesam version 4.4.2, the amount of data was measured in TiB (tebibyte), but the SEP license calculates usage in standard TB, as stated in the labeled capacity of licenses. This means that in version 4.4.2 the actual capacity of the licensed volume was slightly higher from the labeled/allowed amount. In 4.4.3, the amount of data is correctly measured in TB. Because the old license accepted the values that were approximately 10% higher (due to the difference between a tebibyte and a terabyte), a license violation may occur.
    Resolve: To continue using SEP sesam, contact sales@sep.de and order a volume license extension or a replacement license with the correct amount of front-side or storage pool TB. Then install it on SEP sesam Server. For details, see Licensing FAQs. For details on how to calculate front-side capacity, see SEP volume licensing.
Overwriting an EOL-free tape in the single tape drive with the tape label requested by the initialization
Reduced retention time (EOL) for a DIFF or INCR saveset results in reduced retention time for a complete saveset chain
  • If the retention time of a DIFF or INCR saveset is changed to analready expired time, the whole backup chain is affected and all savesets in this backup chain areset with the same expired EOL. This may result in potential data loss because the FULL saveset can also be purged and overwritten.
    Workaround: To avoid data loss and ensure that a FULL saveset is retained for the expected retention time, do not change the EOL of a DIFF or INCR saveset to already expired time.
A new drive cannot be configured for a loader
  • When you attempt to configure a new drive for a loader and only one loader is configured under theLoaders, the loader selection box in the drive dialog/properties only allows to select "No Loader" or "0". The configured loader "1" is missing and consequently a new drive cannot be assigned to it.
    Workaround: Create a dummy loader with dummy values, e.g., loader number 2 with loader namedummy and device dummy. Now the Loaders box will show "No Loader", "1", "2" and you will be able to assign a new drive. For more details on loaders, see Loaders 4.4.
Major update of Windows clients by using local packages (sm_update_client) fails
  • When you attempt to update your Windows clients remotely by using sm_update_client, the update fails in case of a major update, for example from 4.4.2 to 4.4.3. This is a Microsoft Windows Installer ((MSI) error. During update, the operating system is unable to completely remove the previous installation files because SEP sesam CTRLD or SM_SSHD client access programs are still in use. Consequently the update fails.
    Workaround: Perform SEP sesam remote update by using sm_remote_installer.exe on your Windows SEP sesam Server. You will have to provide the username and password. All installation packages must be located in the <SEP_sesam_home>var\work\packages directory. For details, seeRemote installation.
SEP sesam version 4.4.1, 4.4.2 and 4.4.3.xx – The backup task system_recovery does not provide sufficient data for bare system recovery
  • SEP sesam versions from 4.4.1 to 4.4.3.xx provide a misleading backup task type system_recovery. The only supported source system_state backs up data as specified in MS article Backing Up and Restoring System State, but the backed up data does not provide the ability to perform a bare system recovery (BSR).
    Resolve: To prepare for bare system recovery (BSR), use SEP sesam BSR Pro for Windows functionality.
IBM Java 1.8 does not provide Java FX on SLES for GUI calendar and dashboard
  • SEP Sesam 4.4.3. The new GUI features calendar and dashboard are using Java FX which is not included in IBM Java 1.8 on SLES-based distributions, therefore the GUI does not provide neither calendar nor dashboard. Hint: You can access the dashboard by typing the following information in the browser address bar:http://[servername]:11401/sep/ui or https://[servername]:11401/sep/ui. You can create, modify or delete the calendar by using the Calendar Overview. For details, see Modifying a Calendar.
    Resolve: To get access to the new GUI calendar and dashboard features, install OpenJDK-based JRE or Oracle JRE prior to installation or upgrade to 4.4.3.
License violation due to exceeded amount of licensed volume
  • In SEP sesam version 4.4.2 some volume licenses did not check if the licensed volume amount is reached. Now the amount of licensed volumes is checked correctly. If the volume amount allowed by your license has been exceeded, you must acquire a license with larger volume amount.
    Resolve: To continue using SEP sesam, contact sales@sep.de and order a volume license extension or a replacement license with the correct amount of front-side TB. Then install it on SEP sesam Server. For details, see Licensing FAQs. For details on how to calculate front-side capacity, see SEP volume licensing.
SEP sesam version 4.4.3.22 – When running source-side deduplication, no backup throughput is displayed in the GUI
  • When source-side deduplication is used, the backup throughput is not shown in the GUI even though the job has finished successfully.
SEP sesam version 4.4.3.22 – Running concurrent restores may fail
  • Running multiple restores in parallel may fail for some configurations, for example for multiple vSphere or Hyper-V restores that are started from the same saveset.
    Workaround: Do not run vSphere and Hyper-V restores that are using the same source simultaneously.
SEP sesam version 4.4.3.22 – SEP sesam Dashboard shows incorrect chronological order in the Next Events table
  • If the table Next Events is sorted by time (2nd column Starts...), the events are displayed in wrong chronological order. For example, some events that will only be started after a few months are displayed before the events that will be started in the next 60 minutes.
    Workaround: Do not sort the table by time, use sorting by date instead.
SEP sesam version 4.4.3.22 – Replication job state may be incorrect
  • SEP sesam erroneously uses the state of the first started child task as a state for the parent replication task too, even though the other tasks might have failed, are queued or still active.
    Workaround: To make sure that your replication job has successfully finished, check the replication state of each particular saveset.
Upgrade to SEP sesam version 4.4.3.22 – Java upgrade to 1.8 not possible if SEP sesam BSR Pro for Windows is installed
  • If updating from SEP sesam version 4.4.2 with installed SEP sesam BSR Pro, it is not possible to upgrade Java to 1.8.
    Workaround: Uninstall SEP sesam BSR Pro before installing Java 1.8.
Upgrade to SEP sesam version 4.4.3.22 on Windows requires a reboot of your newly installed or updated Windows SEP sesam Server
  • SEP sesam package for Windows includes Callback File System® (CBFS®) version 6.1.181 from EldoS Corporation. 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.
Fixed with SEP sesam Server version 4.4.3.25:
Installation/upgrade does not work with IBM Java included in SLES
  • Installation or upgrade to SEP sesam version 4.4.3 does not work with IBM Java on SLES-based distributions (e.g., SLES12 (1.7.0)). The problem is that IBM Java does not provide the required encryption functionality on SUSE Linux which causes a connection failure between a GUI Client and a SEP sesam Server. Consequently, installing a new version or upgrading from SEP sesam 4.4.2 to 4.4.3 fails.
    Resolve: Upgrade to Oracle Java before installing or upgrading to SEP sesam 4.4.3 -- OR -- after installing or upgrading change the <SEP_sesam_home>bin/gui/sm_ui.jar with the service pack sm_ui.jar.
  • Fixed: SEP sesam Server version 4.4.3.25.
SEP sesam version 4.4.3.22 – Windows Path backup fails with '553 STOR Failed. MTF analyze error [..]'
  • Windows Path backup fails with: Backup finished. Status: ERROR 553 STOR Failed. MTF analyze error [..]. This error occurs when the Sesam Transfer Protocol Server (STPD) checks the Microsoft Tape Format (MTF) stream and encounters MTF format issues. STPD aborts the backup, even though the backed up data is valid and restorable.
  • Fixed: SEP sesam Server version 4.4.3.25. For 4.4.3.22 version, SEP sesam Server/RDS patch –service pack for sms is available at 4.4.3 service packs. This patch prevents the MTF stream check from aborting the backup.
SEP sesam version 4.4.3.22 – Removing an Si3 deduplication store used for replication marks the corresponding savesets as deleted
  • If an Si3 deduplication store, which is used for replication, is removed, the corresponding savesets from the related Si3 data store are set to partially deleted.
  • Fixed: SEP sesam Server version 4.4.3.25. For previous version, service pack for sm_archis available at 4.4.3 service packs.
SEP sesam version 4.4.3.22 – It is not possible to browse RHEV 4.0 VMs
  • Browsing RHEV (RHV) 4.0 VMs is not supported with version 4.4.3.22.
  • Fixed: SEP sesam Server version 4.4.3.25. For previous versions, service pack for RHEL7 data moversbc_proxy is available:sbc_proxy download
SEP sesam version 4.4.3.22 – SEPuler incorrectly calculates the time of the next execution inSchedules
  • In a daily schedule that is configured to be executed every 8 hours, the time of the next execution is incorrectly calculated. For example, the schedule's start time is 3:00, but the time of the next execution is set at 12:00 instead of 11:00.
  • Fixed: SEP sesam Server version 4.4.3.25.
SEP sesam version 4.4.3.22 – Adding a non-existing VM host as a client results in various Java exceptions
  • When selecting an incorrect or non-existing VM host in the process of configuring a virtual machine as a client in the SEP sesam environment, the GUI server and client will throw exceptions every few seconds until the GUI client is terminated.
  • Fixed: SEP sesam Server version 4.4.3.25.
SEP sesam version 4.4.3.22 – Misleading/wrong summary in the state of a failed migration task
  • If a migration event migrates a number of savesets and one of the jobs has failed, the migration state in the GUI shows only the successful migrations, while the failed one is not listed. However, the state of the main migration task is marked as failed even though all migrations except one were successful.
  • Fixed: SEP sesam Server version 4.4.3.25.
SEP sesam version 4.4.3.22 – Loading license overview may take a few minutes
  • License overview may take up to 3 minutes to load due to output of Front side volume per location(MSP license extension)
  • Fixed: SEP sesam Server version 4.4.3.25.

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.

  • In case of VMware, SEP sesam cannot back up the data on the independent or Raw Device Mapping (RDM) disks due to a VMware limitation that does not support including independent/RDM disks in virtual machine snapshots. To 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.
SEP Warning.png 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.

Enhancements and changes

New supported systems

SEP sesam Server 4.4.3 now also supports the following operating systems and applications:

Newly supported operating systems

  • SLES12 on IBM Power Systems (ppc64) and IBM z Systems (Linux Z or LinuxOne)
  • SLES12 (x86-64)
  • SLES12 for SAP (x86-64)
  • SLES11 (ppc64)
  • SLES11 for SAP (x86-64, ppc64)
  • OES 2015 (x86-64) (from SEP sesam version ≥ 4.4.2.81)
  • XenServer 7.0 and XenServer 6.5
  • Debian Jessie (x86-64) (from SEP sesam version ≥ 4.4.2.81)
  • Ubuntu 16.04 LTS
  • Windows 10 (x86) (from SEP sesam version ≥ 4.4.2.87), Windows 10 (x64) (from SEP sesam version ≥ 4.4.2.81)

Newly supported applications

  • vSphere 6.0 (from SEP sesam version ≥ 4.4.2.66)
  • Microsoft Exchange Server 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.

NDMP

SEP sesam now supports Network Data Management Protocol (NDMP) (from SEP sesam version ≥ 4.4.2.87) with NDMP remote configuration, based on version 4 of the NDMP protocol. For details, see NDMP Backup. For a list of supported NAS appliances, see the support matrix. With v. 4.4.3 the backup levels FULL, DIFF and INCREMENTAL are supported for NetApp Filers. A complete restore of the NAS appliance volume is supported to the original or different target. For details, see NDMP Restore.

JIRA backup add-on

SEP sesam Backup for JIRA was developed in cooperation with catWorkX to provide a simple way for backing up and restoring the whole JIRA infrastructure, including all plug-ins and settings. For details on backing up JIRA database configuration, see Jira Backup Module. For details on preparing for a disaster recovery of your JIRA instance, see SEP sesam Extension for Jira.

SEP sesam Dashboard

SEP sesam Dashboard is an easy-to-use online monitoring tool that constantly tracks SEP sesam operations and their state and provides key metrics of your backup environment. You can handily check if all your backups and restores have been completed successfully and review other useful information, such as daily, weekly, monthly or custom statistics on SEP sesam events, on total size of backed up and restored data, and on data store utilization. SEP sesam web dashboard can be accessed either from GUI or at the following address: http://[servername]:11401/sep/ui or https://[servername]:11401/sep/ui. For details, see SEP sesam Dashboard.

Enhanced VMware vSphere CBT (DIFF/INCR) backup for instant recovery and single file restore

SEP sesam now supports single item restore (SF) and instant recovery (IR) based on almost any type of VMware backup, including differential and incremental. Additionally, with version 4.4.3 the restriction that the VMDKs must be saved in RAW format is no longer in effect.

Integrated Si3 target deduplication for VMware backups

Target deduplication can now be performed with VMware backups thus eliminating redundant data blocks and reducing the size of the backed up data. For details, see VMware backup and Deduplication. Both, instant recovery and single item restore can be performed from data stored on Si3 deduplication store.

SEP sesam Red Hat Virtualization (RHV) backup module

Advanced data protection and native backup API support for RHV is based on agentless snapshots and image-level backups of all supported VMs. For details, see RHEV backup. VMs can be restored one at a time to the original or different location, to the same or different single RHV server and to the same or different RHV cluster. Additionally, a simple path restore to a directory is supported. For details, see Restoring RHV Virtual Machines.

Source-side deduplication

A backup administrator can now choose between target- (Si3T) and newly introduced source-side deduplication (Si3S). Both methods require a configured Si3 deduplication store, for which a special license is needed. Source-side deduplication uses the Si3 deduplication engine to transfer only the data portions which are not yet stored on the Si3 deduplication store, thus offering a number of benefits, including reduced bandwidth and storage usage. For details, see Source-side deduplication.

Hyper-V incremental backup

In addition to the COPY backup, Hyper-V backups can now also use the backup level types FULL and INCR which decrease the time required to run backups and reduce storage space.

Enhanced Exchange Server DAG backup

The new concept for Microsoft Exchange Server backup allows to dynamically select the serving Exchange Server node in the DAG group – a dedicated option Execute on any DAG host allows to run database copy backup on any DAG host that has a required database copy. The Database state option is used to select an active or a passive copy for backup.

HSM-aware backup for Windows

HSM-aware backup is included in the SEP sesam package and provides efficient backup of data on Windows systems that is managed by HSM. For details, see HSM-aware Backup for Windows.

Support for NTFS alternate data streams (ADS) for Windows

SEP sesam now provides backup and restore of alternate data streams (ADS) for Windows on NTFS volumes. ADS are backed up by default, but can be excluded from backup by using a special option.
Alternate data streams are a unique data-hiding feature of NTFS file systems. A file in NTFS consists of the unnamed data stream where the data is actually contained, and of alternate data streams that can store additional metadata. Applications may use ADS for storing file attributes. For details, see Support for NTFS alternate data streams (ADS) for Windows.

Bare Metal Recovery Windows

Bare Metal Recovery Windows has improved restore performance when using BSR Pro Quick-Start recovery option. The writing of the saveset data into a temporary file can now be avoided.

Bare Metal Recovery Linux

SEP sesam Bare Metal Recovery Linux Relax-and-Recover (ReaR) integration is enhanced with support for:

  • SLES12
  • Debian 8 (Jessie)
  • UEFI
  • btrfs-based file systems

Replication improvements

By removing limitation on the required same EOL for the source and target pool, SEP sesam now enables more dynamic data replication strategy. For details, see Replication.

Multiple Si3 deduplication stores supported for Linux RDS

The limitation of only one Si3 deduplication store per server is no longer valid for SEP sesam Remote Device Server (RDS) on Linux. Now several Si3 data stores can be set up on one RDS Linux. Note that this is not yet available in the beta release!

MSP license

The new Managed Service Provider license model is available. For more information, contact sales@sep.de.

Exchange Recovery Pro – email recovery from VMDK

SEP sesam Exchange Recovery Pro now allows to recover MS Exchange Server emails from a VMware backup. The VMDK disk file is mounted from either COPY or FULL saveset and incorporates changes from a chain of consequent DIFF or INCREMENTAL backup savesets (based on Changed Block Tracking (CBT), see VMware Backup for details).

GUI enhancements

Flexible scheduling
Scheduling is enhanced with new options: User defined option allows you to create a custom calendar according to your country or company specific requirements. For example, you can define a calendar with specific days on which you want to perform special job executions, such as backup and migration. You can also define specific dates to be excluded from individual schedules, set up a custom calendar of public holiday dates for each year, and stop scheduled jobs from running during holidays. For details, see Creating Custom Calendar.
The Repeat task option allows you to specify the repetition cycle for the task. The task will run, wait for the time interval specified, and then run again. This cycle will continue for as long it is specified by the duration time.
You are also able to prevent tasks to be run for too long by using the option Stop task if runs longer than and setting a time limit for the amount of time a task is allowed to run. For details on new scheduling options, see Creating a schedule.
Follow-up events
This handy feature can ease your data protection administration by configuring events that are triggered on the SEP sesam Server once the initial event has completed. You can set up a migration, a saveset verify and other actions to be triggered immediately after a backup or other event is completed. For details, see Follow-up Events.
Overview of all configured events
The Schedules component of the GUI navigation pane provides a new sub-menu Events as List. This overview shows a list of all configured events with details for each listed event, including event ID, related task, related schedule, event priority, target media pool, drive number, interface, follow-up events and the time of the next execution. For details, see Events as list.

End of maintenance and support

Obsolete SEP sesam Server version

The following versions of SEP sesam are no longer supported:

  • SEP sesam v. 4.2.2
  • SEP sesam v. 4.2.1
  • SEP sesam v. 4.0
  • SEP sesam v. 3.6
  • SEP sesam v. 3.4
  • SEP sesam v. 3.0

Unsupported SEP sesam Server OS

The following operating systems are no longer supported for SEP sesam Server:

  • All 32-bit operating systems
  • Windows Server 2003 Win7.gif
  • SLES 10 Tux.gif
  • SLES 11 SP1 (see Note!) Tux.gif
  • RHEL 5 Tux.gif
  • Debian Lenny Tux.gif
  • Debian Squeeze Tux.gif
Information sign.png Note
SLES 11 SP2/SP3 is still supported. The limitation applies only to SEP sesam Server systems and does not affect SEP sesam Clients. For a complete list of supported SEP sesam Clients, see SEP sesam support matrix.

Major fixes and changes

For a complete list of GIT change reports, see changes.

See also

SEP sesam Release Versions