https://wiki.sep.de/wiki/index.php?title=Release_Notes_4.4.3&feed=atom&action=historyRelease Notes 4.4.3 - Revision history2024-03-28T16:05:37ZRevision history for this page on the wikiMediaWiki 1.38.4https://wiki.sep.de/wiki/index.php?title=Release_Notes_4.4.3&diff=179638&oldid=prevSta: Corrected SSDD to Si3S (EE).2021-04-21T08:05:42Z<p>Corrected SSDD to Si3S (EE).</p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 09:05, 21 April 2021</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l55">Line 55:</td>
<td colspan="2" class="diff-lineno">Line 55:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>{{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.}}</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>{{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.}}</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>{{Box Hint Y|4.4.3 known issues|</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>{{Box Hint Y|4.4.3 known issues|</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>;SEP sesam v. 4.4.3-4.4.3.84 – <del style="font-weight: bold; text-decoration: none;">SSDD </del>does not work in case of changed STPD port on the Client </div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>;SEP sesam v. 4.4.3-4.4.3.84 – <ins style="font-weight: bold; text-decoration: none;">Si3S </ins>does not work in case of changed STPD port on the Client </div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>:*[[Special:MyLanguage/SEP_sesam_Glossary#Si3S|SEP Si3 source-side deduplication]] (<del style="font-weight: bold; text-decoration: none;">SSDD</del>) 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.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>:*[[Special:MyLanguage/SEP_sesam_Glossary#Si3S|SEP Si3 source-side deduplication]] (<ins style="font-weight: bold; text-decoration: none;">Si3S</ins>) 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.</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>:::'''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]].</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>:::'''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]].</div></td></tr>
</table>Stahttps://wiki.sep.de/wiki/index.php?title=Release_Notes_4.4.3&diff=177476&oldid=prevSta: Minor correction.2021-03-09T09:27:29Z<p>Minor correction.</p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 10:27, 9 March 2021</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l56">Line 56:</td>
<td colspan="2" class="diff-lineno">Line 56:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>{{Box Hint Y|4.4.3 known issues|</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>{{Box Hint Y|4.4.3 known issues|</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>;SEP sesam v. 4.4.3-4.4.3.84 – SSDD does not work in case of changed STPD port on the Client </div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>;SEP sesam v. 4.4.3-4.4.3.84 – SSDD does not work in case of changed STPD port on the Client </div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>:*[[Special:MyLanguage/SEP_sesam_Glossary#Si3S|SEP Si3 source-side deduplication]] (SSDD) <del style="font-weight: bold; text-decoration: none;">during </del>backup to a SEP <del style="font-weight: bold; text-decoration: none;">sesam </del>Si3 <del style="font-weight: bold; text-decoration: none;">duplication </del>store <del style="font-weight: bold; text-decoration: none;">does </del>not work, if the STPD service TCP port on the <del style="font-weight: bold; text-decoration: none;">Client-</del>side (''client properties'' -> ''Options tab'' -> ''STPD options'') is changed from default.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>:*[[Special:MyLanguage/SEP_sesam_Glossary#Si3S|SEP Si3 source-side deduplication]] (SSDD) backup <ins style="font-weight: bold; text-decoration: none;">of a client </ins>to a SEP Si3 <ins style="font-weight: bold; text-decoration: none;">deduplication </ins>store not work, if the STPD service TCP port on the <ins style="font-weight: bold; text-decoration: none;">client </ins>side (''client properties'' -> ''Options tab'' -> ''STPD options'') is changed from <ins style="font-weight: bold; text-decoration: none;">the </ins>default <ins style="font-weight: bold; text-decoration: none;">port</ins>.</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>:::'''Workaround:''' Make sure <del style="font-weight: bold; text-decoration: none;">to </del>use the default STPD TCP port <del style="font-weight: bold; text-decoration: none;">for your Client</del>. For details, see [[Special:MyLanguage/4_4_3_Tigon:List_of_Ports_Used_by_SEP_sesam|List of Ports Used by SEP sesam]].</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>:::'''Workaround:''' Make sure <ins style="font-weight: bold; text-decoration: none;">that you </ins>use the default STPD TCP port <ins style="font-weight: bold; text-decoration: none;">on the client side</ins>. For details, see [[Special:MyLanguage/4_4_3_Tigon:List_of_Ports_Used_by_SEP_sesam|List of Ports Used by SEP sesam]].</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>;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:</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>;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:</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>:*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.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>:*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.</div></td></tr>
</table>Stahttps://wiki.sep.de/wiki/index.php?title=Release_Notes_4.4.3&diff=177475&oldid=prevSta: Added STPD port known issue (JGE, #28637).2021-03-09T09:05:12Z<p>Added STPD port known issue (JGE, #28637).</p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 10:05, 9 March 2021</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l55">Line 55:</td>
<td colspan="2" class="diff-lineno">Line 55:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>{{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.}}</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>{{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.}}</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>{{Box Hint Y|4.4.3 known issues|</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>{{Box Hint Y|4.4.3 known issues|</div></td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">;SEP sesam v. 4.4.3-4.4.3.84 – SSDD does not work in case of changed STPD port on the Client </ins></div></td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">:*[[Special:MyLanguage/SEP_sesam_Glossary#Si3S|SEP Si3 source-side deduplication]] (SSDD) during backup to a SEP sesam Si3 duplication store does not work, if the STPD service TCP port on the Client-side (''client properties'' -> ''Options tab'' -> ''STPD options'') is changed from default.</ins></div></td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"></ins></div></td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">:::'''Workaround:''' Make sure to use the default STPD TCP port for your Client. For details, see [[Special:MyLanguage/4_4_3_Tigon:List_of_Ports_Used_by_SEP_sesam|List of Ports Used by SEP sesam]].</ins></div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>;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:</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>;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:</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>:*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.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>:*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.</div></td></tr>
</table>Stahttps://wiki.sep.de/wiki/index.php?title=Release_Notes_4.4.3&diff=70718&oldid=prevSta: Added limitations for hypervisors.2018-06-28T11:32:13Z<p>Added limitations for hypervisors.</p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 12:32, 28 June 2018</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l126">Line 126:</td>
<td colspan="2" class="diff-lineno">Line 126:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>:* 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'''.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>:* 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'''.</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>}}</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>}}</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;"></del></div></td><td colspan="2" class="diff-side-added"></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;"></del></div></td><td colspan="2" class="diff-side-added"></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>{{Box Hint|Fixed with [https://download.sep.de/ SEP sesam Server version 4.4.3.25]|</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>{{Box Hint|Fixed with [https://download.sep.de/ SEP sesam Server version 4.4.3.25]|</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>;Installation/upgrade does not work with IBM Java included in SLES:</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>;Installation/upgrade does not work with IBM Java included in SLES:</div></td></tr>
<tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l162">Line 162:</td>
<td colspan="2" class="diff-lineno">Line 160:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>:* '''Fixed:''' SEP sesam Server version 4.4.3.25.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>:* '''Fixed:''' SEP sesam Server version 4.4.3.25.</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>}}</onlyinclude></div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>}}</onlyinclude></div></td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"></ins></div></td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">===Limitations===</ins></div></td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">;SEP sesam backup for hypervisors (VMware, Hyper-V, Citrix Xen, KVM, OpenNebula) cannot back up the data on external disks: </ins></div></td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">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. </ins></div></td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">:*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. </ins></div></td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">:*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. </ins></div></td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">{{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.}}</ins></div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>== {{anchor|enhancements}}Enhancements and changes ==</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>== {{anchor|enhancements}}Enhancements and changes ==</div></td></tr>
</table>Stahttps://wiki.sep.de/wiki/index.php?title=Release_Notes_4.4.3&diff=69125&oldid=prevSta: Fixed links.2018-06-08T10:50:56Z<p>Fixed links.</p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 11:50, 8 June 2018</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l15">Line 15:</td>
<td colspan="2" class="diff-lineno">Line 15:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>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.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>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.</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>Storage file servers can be efficiently protected by new '''[[<del style="font-weight: bold; text-decoration: none;">NDMP Backup</del>|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]].</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>Storage file servers can be efficiently protected by new '''[[<ins style="font-weight: bold; text-decoration: none;">4_4_3:NDMP_Backup</ins>|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]].</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==={{anchor|requirements}}SEP sesam Server requirements===</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==={{anchor|requirements}}SEP sesam Server requirements===</div></td></tr>
<tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l187">Line 187:</td>
<td colspan="2" class="diff-lineno">Line 187:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>===NDMP===</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>===NDMP===</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>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]].</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>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 [[<ins style="font-weight: bold; text-decoration: none;">4_4_3:NDMP_Restore|</ins>NDMP Restore]].</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>===JIRA backup add-on===</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>===JIRA backup add-on===</div></td></tr>
</table>Stahttps://wiki.sep.de/wiki/index.php?title=Release_Notes_4.4.3&diff=68809&oldid=prevSta at 10:07, 7 June 20182018-06-07T10:07:39Z<p></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 11:07, 7 June 2018</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l44">Line 44:</td>
<td colspan="2" class="diff-lineno">Line 44:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>The 4.4.3 '''installation package on Windows''' also includes:</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>The 4.4.3 '''installation package on Windows''' also includes:</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>* ''VMware® Virtual Disk Development Kit (VDDK) version 6.0.2'' for Windows.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>* ''VMware® Virtual Disk Development Kit (VDDK) version 6.0.2'' for Windows.</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>* New ''Callback File System® (CBFS®) version 6.1.181'' from EldoS Corporation, used to create virtual file systems and disks for <del style="font-weight: bold; text-decoration: none;">save sets </del>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.}} </div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>* New ''Callback File System® (CBFS®) version 6.1.181'' from EldoS Corporation, used to create virtual file systems and disks for <ins style="font-weight: bold; text-decoration: none;">savesets </ins>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.}} </div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>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]].</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>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]].</div></td></tr>
<tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l79">Line 79:</td>
<td colspan="2" class="diff-lineno">Line 79:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>:* '''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]].</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>:* '''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]].</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>;Reduced retention time (EOL) for a DIFF or INCR <del style="font-weight: bold; text-decoration: none;">save set </del>results in reduced retention time for a complete <del style="font-weight: bold; text-decoration: none;">save set </del>chain: </div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>;Reduced retention time (EOL) for a DIFF or INCR <ins style="font-weight: bold; text-decoration: none;">saveset </ins>results in reduced retention time for a complete <ins style="font-weight: bold; text-decoration: none;">saveset </ins>chain: </div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>:* If the [[SEP_sesam_Glossary#retention_time|retention time]] of a DIFF or INCR <del style="font-weight: bold; text-decoration: none;">save set </del>is changed to an'''''already expired time''''', the whole backup chain is affected and all <del style="font-weight: bold; text-decoration: none;">save sets </del>in this backup chain <del style="font-weight: bold; text-decoration: none;">are set </del>with the same expired [[SEP_sesam_Glossary#EOL|EOL]]. This may result in potential data loss because the FULL <del style="font-weight: bold; text-decoration: none;">save set </del>can also be purged and overwritten. </div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>:* If the [[SEP_sesam_Glossary#retention_time|retention time]] of a DIFF or INCR <ins style="font-weight: bold; text-decoration: none;">saveset </ins>is changed to an'''''already expired time''''', the whole backup chain is affected and all <ins style="font-weight: bold; text-decoration: none;">savesets </ins>in this backup chain <ins style="font-weight: bold; text-decoration: none;">areset </ins>with the same expired [[SEP_sesam_Glossary#EOL|EOL]]. This may result in potential data loss because the FULL <ins style="font-weight: bold; text-decoration: none;">saveset </ins>can also be purged and overwritten. </div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>:*::: '''Workaround:''' To avoid data loss and ensure that a FULL <del style="font-weight: bold; text-decoration: none;">save set </del>is retained for the expected retention time, do not change the EOL of a DIFF or INCR <del style="font-weight: bold; text-decoration: none;">save set </del>to already expired time.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>:*::: '''Workaround:''' To avoid data loss and ensure that a FULL <ins style="font-weight: bold; text-decoration: none;">saveset </ins>is retained for the expected retention time, do not change the EOL of a DIFF or INCR <ins style="font-weight: bold; text-decoration: none;">saveset </ins>to already expired time.</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>;A new drive cannot be configured for a loader: </div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>;A new drive cannot be configured for a loader: </div></td></tr>
<tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l105">Line 105:</td>
<td colspan="2" class="diff-lineno">Line 105:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>;''SEP sesam version 4.4.3.22'' – When running source-side deduplication, no backup throughput is displayed in the GUI:</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>;''SEP sesam version 4.4.3.22'' – When running source-side deduplication, no backup throughput is displayed in the GUI:</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>:* When source-side deduplication is used, the backup throughput is not shown in the GUI even though the job has finished successfully.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>:* When source-side deduplication is used, the backup throughput is not shown in the GUI even though the job has finished successfully.</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><!-- :*::: '''Workaround:''' To make sure that your backup job has successfully finished, check the state of each particular <del style="font-weight: bold; text-decoration: none;">save set</del>. --></div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><!-- :*::: '''Workaround:''' To make sure that your backup job has successfully finished, check the state of each particular <ins style="font-weight: bold; text-decoration: none;">saveset</ins>. --></div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>;''SEP sesam version 4.4.3.22'' – Running concurrent restores may fail:</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>;''SEP sesam version 4.4.3.22'' – Running concurrent restores may fail:</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>:* 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 <del style="font-weight: bold; text-decoration: none;">save set</del>.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>:* 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 <ins style="font-weight: bold; text-decoration: none;">saveset</ins>.</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>:*::: '''Workaround:''' Do not run vSphere and Hyper-V restores that are using the same source simultaneously.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>:*::: '''Workaround:''' Do not run vSphere and Hyper-V restores that are using the same source simultaneously.</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l117">Line 117:</td>
<td colspan="2" class="diff-lineno">Line 117:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>;''SEP sesam version 4.4.3.22'' – Replication job state may be incorrect:</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>;''SEP sesam version 4.4.3.22'' – Replication job state may be incorrect:</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>:*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.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>:*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.</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>:*::: '''Workaround:''' To make sure that your replication job has successfully finished, check the replication state of each particular <del style="font-weight: bold; text-decoration: none;">save set</del>.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>:*::: '''Workaround:''' To make sure that your replication job has successfully finished, check the replication state of each particular <ins style="font-weight: bold; text-decoration: none;">saveset</ins>.</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>;''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:</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>;''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:</div></td></tr>
<tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l138">Line 138:</td>
<td colspan="2" class="diff-lineno">Line 138:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>:* '''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-->.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>:* '''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-->.</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>;''SEP sesam version 4.4.3.22'' – Removing an Si3 deduplication store used for replication marks the corresponding <del style="font-weight: bold; text-decoration: none;">save sets </del>as deleted:</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>;''SEP sesam version 4.4.3.22'' – Removing an Si3 deduplication store used for replication marks the corresponding <ins style="font-weight: bold; text-decoration: none;">savesets </ins>as deleted:</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>:* If an Si3 deduplication store, which is used for replication, is removed, the corresponding <del style="font-weight: bold; text-decoration: none;">save sets </del>from the related Si3 data store are set to partially deleted.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>:* If an Si3 deduplication store, which is used for replication, is removed, the corresponding <ins style="font-weight: bold; text-decoration: none;">savesets </ins>from the related Si3 data store are set to partially deleted.</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>:* '''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].</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>:* '''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].</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l155">Line 155:</td>
<td colspan="2" class="diff-lineno">Line 155:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>;SEP sesam version 4.4.3.22 – Misleading/wrong summary in the state of a failed migration task:</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>;SEP sesam version 4.4.3.22 – Misleading/wrong summary in the state of a failed migration task:</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>:*If a migration event migrates a number of <del style="font-weight: bold; text-decoration: none;">save sets </del>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.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>:*If a migration event migrates a number of <ins style="font-weight: bold; text-decoration: none;">savesets </ins>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.</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>:* '''Fixed:''' SEP sesam Server version 4.4.3.25.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>:* '''Fixed:''' SEP sesam Server version 4.4.3.25.</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l221">Line 221:</td>
<td colspan="2" class="diff-lineno">Line 221:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>===Bare Metal Recovery Windows===</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>===Bare Metal Recovery Windows===</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>[[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 <del style="font-weight: bold; text-decoration: none;">save set </del>data into a temporary file can now be avoided.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>[[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 <ins style="font-weight: bold; text-decoration: none;">saveset </ins>data into a temporary file can now be avoided.</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>===Bare Metal Recovery Linux===</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>===Bare Metal Recovery Linux===</div></td></tr>
<tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l243">Line 243:</td>
<td colspan="2" class="diff-lineno">Line 243:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>===''Exchange Recovery Pro'' – email recovery from VMDK===</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>===''Exchange Recovery Pro'' – email recovery from VMDK===</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>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 <del style="font-weight: bold; text-decoration: none;">save set </del>and incorporates changes from a chain of consequent DIFF or INCREMENTAL backup <del style="font-weight: bold; text-decoration: none;">save sets </del>(based on Changed Block Tracking (CBT), see [[VMware Backup]] for details).</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>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 <ins style="font-weight: bold; text-decoration: none;">saveset </ins>and incorporates changes from a chain of consequent DIFF or INCREMENTAL backup <ins style="font-weight: bold; text-decoration: none;">savesets </ins>(based on Changed Block Tracking (CBT), see [[VMware Backup]] for details).</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>=== GUI enhancements=== </div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>=== GUI enhancements=== </div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div><!-- Description or list of any changes in GUI --></div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div><!-- Description or list of any changes in GUI --></div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>;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]].</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>;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]].</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>;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 <del style="font-weight: bold; text-decoration: none;">save set </del>verify and other actions to be triggered immediately after a backup or other event is completed. For details, see [[Follow-up Events]].</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>;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 <ins style="font-weight: bold; text-decoration: none;">saveset </ins>verify and other actions to be triggered immediately after a backup or other event is completed. For details, see [[Follow-up Events]].</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>;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]].</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>;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]].</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
</table>Stahttps://wiki.sep.de/wiki/index.php?title=Release_Notes_4.4.3&diff=68801&oldid=prevSta: /* {{anchor|issues}}Known issues and limitations */2018-06-07T09:57:38Z<p><span dir="auto"><span class="autocomment">{{anchor|issues}}Known issues and limitations</span></span></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 10:57, 7 June 2018</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l56">Line 56:</td>
<td colspan="2" class="diff-lineno">Line 56:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>{{Box Hint Y|4.4.3 known issues|</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>{{Box Hint Y|4.4.3 known issues|</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>;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:</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>;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:</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>:*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 <del style="font-weight: bold; text-decoration: none;">save set </del>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.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>:*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 <ins style="font-weight: bold; text-decoration: none;">saveset </ins>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.</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>::: '''Workaround:''' To back up virtual machines that contain <del style="font-weight: bold; text-decoration: none;">independent </del>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.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>::: '''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.</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>;SEP sesam ≤ 4.4.3.45 – Migration ignores client defined by migration schedule/event:</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>;SEP sesam ≤ 4.4.3.45 – Migration ignores client defined by migration schedule/event:</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>:* 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.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>:* 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.</div></td></tr>
</table>Stahttps://wiki.sep.de/wiki/index.php?title=Release_Notes_4.4.3&diff=68799&oldid=prevSta: /* {{anchor|issues}}Known issues and limitations */2018-06-07T09:49:57Z<p><span dir="auto"><span class="autocomment">{{anchor|issues}}Known issues and limitations</span></span></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 10:49, 7 June 2018</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l56">Line 56:</td>
<td colspan="2" class="diff-lineno">Line 56:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>{{Box Hint Y|4.4.3 known issues|</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>{{Box Hint Y|4.4.3 known issues|</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>;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:</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>;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:</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>:*When backing up via hypervisor and using external disk, SEP sesam cannot back up the data on the independent or RDM disks, because <del style="font-weight: bold; text-decoration: none;">virtual machines with </del>such <del style="font-weight: bold; text-decoration: none;">disks cannot use memory or quiesced snapshots</del>. The data of such disks is silently skipped from backup, hence the backup save set contains no data for the independent <del style="font-weight: bold; text-decoration: none;">disk </del>while the backup succeeds and no warning about the missing data is issued. If a restore of a VM with independent disk is performed to the original VM by using the option ''overwrite'', the independent disk is re-created and all existing data on the restore target is lost.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>:*When backing up via hypervisor and using external disk, SEP sesam cannot back up the data on the independent or RDM disks, because <ins style="font-weight: bold; text-decoration: none;">hypervisors are not able to back up </ins>such <ins style="font-weight: bold; text-decoration: none;">devices</ins>. The data of such disks is silently skipped from backup, hence the backup save set contains no data for the independent <ins style="font-weight: bold; text-decoration: none;">or RDM disks </ins>while the backup succeeds and no warning about the missing data is issued. If a restore of a VM with independent<ins style="font-weight: bold; text-decoration: none;">/RDM </ins>disk is performed to the original VM by using the option ''overwrite'', the independent<ins style="font-weight: bold; text-decoration: none;">/RDM </ins>disk is re-created and all existing data on the restore target is lost.</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>::: '''Workaround:''' To back up virtual machines that contain independent 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.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>::: '''Workaround:''' To back up virtual machines that contain independent 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.</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>;SEP sesam ≤ 4.4.3.45 – Migration ignores client defined by migration schedule/event:</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>;SEP sesam ≤ 4.4.3.45 – Migration ignores client defined by migration schedule/event:</div></td></tr>
</table>Stahttps://wiki.sep.de/wiki/index.php?title=Release_Notes_4.4.3&diff=68652&oldid=prevSta: /* {{anchor|issues}}Known issues and limitations */ -> Added SEP sesam backup for hypervisors limitation (proposed by EE)2018-06-06T12:35:05Z<p><span dir="auto"><span class="autocomment">{{anchor|issues}}Known issues and limitations: </span> -> Added SEP sesam backup for hypervisors limitation (proposed by EE)</span></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 13:35, 6 June 2018</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l55">Line 55:</td>
<td colspan="2" class="diff-lineno">Line 55:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>{{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.}}</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>{{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.}}</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>{{Box Hint Y|4.4.3 known issues|</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>{{Box Hint Y|4.4.3 known issues|</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;"><!--</del></div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>;SEP sesam version <ins style="font-weight: bold; text-decoration: none;">≥ </ins>4.4.3.<ins style="font-weight: bold; text-decoration: none;">22 – SEP sesam backup for hypervisors (VMware, Hyper</ins>-<ins style="font-weight: bold; text-decoration: none;">V, Citrix XEN, KVM, OpenNebula) cannot back up the data on the independent disks or Raw Device Mapping (RDM) disks</ins>:</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>;SEP sesam version 4.4.3.<del style="font-weight: bold; text-decoration: none;">25 </del>- <del style="font-weight: bold; text-decoration: none;">Migration of DIFF/INCR backups ends with warning if referenced migrated save set is also replicated</del>:</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>:*<ins style="font-weight: bold; text-decoration: none;">When backing up via hypervisor and using external disk, </ins>SEP sesam <ins style="font-weight: bold; text-decoration: none;">cannot back up the data on the independent or RDM disks, because virtual machines with such disks cannot use memory or quiesced snapshots</ins>. <ins style="font-weight: bold; text-decoration: none;">The data of such disks is silently skipped from backup, hence the backup save set contains no data for the independent disk while the backup succeeds and no warning about the missing data is issued</ins>. <ins style="font-weight: bold; text-decoration: none;">If </ins>a <ins style="font-weight: bold; text-decoration: none;">restore </ins>of <ins style="font-weight: bold; text-decoration: none;">a VM </ins>with <ins style="font-weight: bold; text-decoration: none;">independent disk is performed to the original VM by using the option ''overwrite'', the independent disk is re-created and all existing data on </ins>the <ins style="font-weight: bold; text-decoration: none;">restore target is lost</ins>.</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>:* <del style="font-weight: bold; text-decoration: none;">In </del>SEP sesam <del style="font-weight: bold; text-decoration: none;">version 4</del>.<del style="font-weight: bold; text-decoration: none;">4</del>.<del style="font-weight: bold; text-decoration: none;">3.25 </del>a <del style="font-weight: bold; text-decoration: none;">migration </del>of <del style="font-weight: bold; text-decoration: none;">DIFF/INC R backup may end </del>with <del style="font-weight: bold; text-decoration: none;">warning if one of </del>the <del style="font-weight: bold; text-decoration: none;">referenced save sets was replicated</del>.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>::: '''<ins style="font-weight: bold; text-decoration: none;">Workaround</ins>:''' <ins style="font-weight: bold; text-decoration: none;">To back up virtual machines that contain independent independent disks and RDMs, you have to install the </ins>SEP sesam <ins style="font-weight: bold; text-decoration: none;">Client in the virtual machine and perform an additional file or application backup to back up this data</ins>.</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;">:*</del>::: '''<del style="font-weight: bold; text-decoration: none;">Fixed</del>:''' SEP sesam <del style="font-weight: bold; text-decoration: none;">Server version 4.4.3.23. Install SEP sesam Server patch for v. 4.4.3.25 [https://download.sep.de/servicepacks/4</del>.<del style="font-weight: bold; text-decoration: none;">4.3/ 4.4.3 service packs].</del></div></td><td colspan="2" class="diff-side-added"></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;">--></del></div></td><td colspan="2" class="diff-side-added"></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>;SEP sesam ≤ 4.4.3.45 – Migration ignores client defined by migration schedule/event:</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>;SEP sesam ≤ 4.4.3.45 – Migration ignores client defined by migration schedule/event:</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>:* 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.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>:* 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.</div></td></tr>
</table>Stahttps://wiki.sep.de/wiki/index.php?title=Release_Notes_4.4.3&diff=50071&oldid=prevSta at 17:29, 15 November 20172017-11-15T17:29:25Z<p></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 18:29, 15 November 2017</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l1">Line 1:</td>
<td colspan="2" class="diff-lineno">Line 1:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>{{Copyright SEP AG en}}</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>{{Copyright SEP AG en}}</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div><!-- 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]]}}</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div><!-- 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]]}}</div></td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"></ins></div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>== {{anchor|new}}What's new in SEP sesam v. 4.4.3 ==</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>== {{anchor|new}}What's new in SEP sesam v. 4.4.3 ==</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div><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></div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div><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></div></td></tr>
</table>Sta