Archive:Release Notes 4.4.1: Difference between revisions
No edit summary |
|||
Line 2: | Line 2: | ||
== What's new in SEP sesam release 4.4.1 == | == What's new in SEP sesam release 4.4.1 == | ||
<!-- State a paragraph or two (short intro) listing the major features included in this release. As a reference use the "New Features" / "Enhancements" section. --> | <!-- State a paragraph or two (short intro) listing the major features included in this release. As a reference use the "New Features" / "Enhancements" section. --> | ||
SEP sesam provides '''extended support for VMWare vSphere''' that enables '''instant VMware vSphere recovery''' as well as '''single item restore'''. | SEP sesam provides '''extended support for VMWare vSphere''' that enables '''instant VMware vSphere recovery''' as well as '''single item restore'''. Si3 Si3 target deduplication for Linux is introduced. SEP sesam GUI has been enhanced to provide better <!-- additional? more efficient?/more structured/more transparent? --> overview of the configured tasks and clients. Additionally, new options for customizing the GUI are now available. For details, see [[#Enhancements and changes|Enhancements and changes]]. | ||
'''Upgrades and licensing''' | '''Upgrades and licensing''' | ||
Line 30: | Line 30: | ||
<!-- Info about available upgrades including the limitations and restraints, if there are any. --> | <!-- Info about available upgrades including the limitations and restraints, if there are any. --> | ||
== Known | == Known Issues and Limitations == | ||
<!-- Outstanding issues, such as unresolved defects, workarounds, installation issues etc.) --> | <!-- Outstanding issues, such as unresolved defects, workarounds, installation issues etc.) --> | ||
{{Box Hint|Known Issues| | {{Box Hint|Known Issues| | ||
Line 39: | Line 39: | ||
--> | --> | ||
;Windows Update: | ;Windows Update: | ||
:* An Error | :* An Error occurs when trying to update a Windows SEP sesam GUI installation package V4.4.1.14-4.4.1.23 with a GUI installation package >V4.4.1.23: '''Could not load table 'LaunchCondition' in SQL query: SELECT `Condition`, `Description` FROM `LaunchCondition`.''' | ||
:* '''Workaround:''' | :* '''Workaround:''' Uninstall the SEP sesam GUI and re-install a newer version (V4.4.1.25 or higher) of the SEP sesam GUI. | ||
:* Hint: It is not supported to update a Windows SEP sesam client installation package with a | :* Hint: It is not supported to update a Windows SEP sesam client installation package with a GUI or a server installation package. It is not supported to update a Windows SEP sesam GUI installation package with a client or a server installation package. It is not supported to update a Windows SEP sesam server installation package with a client or a GUI installation package. | ||
;Remote Update of Windows Server 2003: | ;Remote Update of Windows Server 2003: | ||
:* In SEP sesam V4.4.1 the command line based remote update (using sm_update_client or sm_remote_installer) of a Windows Server 2003 fails. Windows Server 2003 is not supported for SEP sesam V4.4.1. After the failed update the services of the client are down. | :* In SEP sesam V4.4.1, the command line based remote update (using sm_update_client or sm_remote_installer) of a Windows Server 2003 fails. Windows Server 2003 is not supported for SEP sesam V4.4.1. After the failed update, the services of the client are down. | ||
:* '''Workaround:''' Connect to the Windows Server 2003 and start the services. | :* '''Workaround:''' Connect to the Windows Server 2003 and start the services. | ||
;Side by side error executing Python executables (V4.4.1.22-4.4.1.25): | ;Side by side error executing Python executables (V4.4.1.22-4.4.1.25): | ||
:* Side by side error occurs when trying to execute any python executable if msvcr90.dll with version 9.0.21022.8 was missing. The python27.dll is linked against | :* Side by side error occurs when trying to execute any python executable if msvcr90.dll with version 9.0.21022.8 was missing. The python27.dll is linked against a different msvcr90.dll than the one delivered by SEP. The msi installer installs the missing redistributable during the installation and update process. | ||
:* '''Fixed:''' Version 4.4.1.26: installs the missing redistributable package during install/update | :* '''Fixed:''' Version 4.4.1.26: installs the missing redistributable package during install/update | ||
;If a | ;If a saveset exceeds the maximum file size limit of a file system, the data above the limit is lost during backup/migration on the datastore. The backup/migration is marked as successful even though the saveset is incomplete due to the resulting data loss from the saveset exceeding the datastore's file size limits (e.g. ext3 file system). In ext3, the maximum file size is between 16 GB and 2 TB. In order to guarantee a full backup saveset, those backups must immediately be executed on appropriate media (Data Store with sufficient file system limit or tape drive). | ||
:* '''Fixed:''' Version 4.4.1.25 aborts backups and | :* '''Fixed:''' Version 4.4.1.25 aborts backups and migrations that exceed the specified limits of the file system. To avoid this, file systems with sufficient file sizes, e.g. XFS with 16 EiB, must be used. If the file system is insufficient, the Data Store must be newly set up, on a new system for example, and the existing backup sets must be migrated or copied. | ||
<!-- | <!-- | ||
:* '''Workaround''': Avoid savesets with sizes larger then the file system file limit on | :* '''Workaround''': Avoid savesets with sizes larger then the file system file limit on datastores with limited file sizes (not recommended by SEP). | ||
--> | --> | ||
:* '''Note 1:''' This problem occurs only | :* '''Note 1:''' This problem occurs only with version 4.4.1.14 and newer. In older versions of SEP sesam (3.6/4.0/4.2), storing operations exceeding the file limits will be aborted. | ||
:* '''Note 2:''' Since version 4.4.1.25 SEP sesam provides a [[English_FAQ#Check_consistency_of_a_Data_Store |consistency check for a data store]] | :* '''Note 2:''' Since version 4.4.1.25, SEP sesam provides a [[English_FAQ#Check_consistency_of_a_Data_Store |consistency check for a data store]] | ||
;Path backup option 'VSS' is not selectable for 'Windows Server 2012 R2' clients: | ;Path backup option 'VSS' is not selectable for 'Windows Server 2012 R2' clients: | ||
In SEP sesam V4.4.1.22 the 'VSS' option for 'Windows Server 2012 R2' clients | In SEP sesam V4.4.1.22, the 'VSS' option for 'Windows Server 2012 R2' clients cannot be set. | ||
:* '''Fixed:''' V4.4.1.23. After the update to 4.4.1.23 the 'Path' backup tasks should be set up with 'VSS' option to allow a consistent backup. | :* '''Fixed:''' V4.4.1.23. After the update to 4.4.1.23, the 'Path' backup tasks should be set up with 'VSS' option to allow a consistent backup. | ||
:* '''Workaround''': At the SEP sesam server execute to allow to set the 'VSS' option, after setting the [[English_FAQ#A support staff member told me to set a profile, what does it mean? | SEP sesam environment]] | :* '''Workaround''': At the SEP sesam server execute to allow to set the 'VSS' option, after setting the [[English_FAQ#A support staff member told me to set a profile, what does it mean? | SEP sesam environment]] | ||
<code> sm_db "INSERT INTO syntaxes (os,command,syntax) VALUES ('Windows Server 2012 R2','SNAPSHOT-cmd','vss')"</code> | <code> sm_db "INSERT INTO syntaxes (os,command,syntax) VALUES ('Windows Server 2012 R2','SNAPSHOT-cmd','vss')"</code> | ||
Line 67: | Line 67: | ||
;Update on Debian based system fails due to wrong java version: | ;Update on Debian based system fails due to wrong java version: | ||
To fix update problems on Debian systems: | To fix update problems on Debian systems: | ||
:* Before updating | :* Before updating SEP sesam, install JRE 7 based Java version 7: | ||
<code> apt-get install openjdk-7-jre</code> | <code> apt-get install openjdk-7-jre</code> | ||
:* make this Java version the default: | :* make this Java version the default: | ||
<code> update-alternatives --set java /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java </code> | <code> update-alternatives --set java /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java </code> | ||
:* update your | :* update your SEP sesam installation via "apt-get upgrade" | ||
;Interrupted access to vSphere: | ;Interrupted access to vSphere: | ||
Line 92: | Line 92: | ||
}} | }} | ||
== Enhancements and | == Enhancements and Changes == | ||
<!-- If this is a major release, the title is "New Features", otherwise use the "Enhancements".--> | <!-- If this is a major release, the title is "New Features", otherwise use the "Enhancements".--> | ||
Line 101: | Line 101: | ||
=== <span style="color:darkgreen">New supported systems</span> === <!-- or title System Requirements (if any needed with version numbers or/and dates) --> | === <span style="color:darkgreen">New supported systems</span> === <!-- or title System Requirements (if any needed with version numbers or/and dates) --> | ||
SEP sesam Server 4.4.1 now also supports the following operating systems and applications: | SEP sesam Server 4.4.1 now also supports the following operating systems and applications: | ||
; | ; Newly supported operating systems | ||
: Windows Server 2012 R2 [[File:windows server 2012 r2.jpg]] | : Windows Server 2012 R2 [[File:windows server 2012 r2.jpg]] | ||
: Path Backup and Restore of Windows 2012 Volumes on Storage Spaces (Disaster Recovery of Storage Spaces are not supported) | : Path Backup and Restore of Windows 2012 Volumes on Storage Spaces (Disaster Recovery of Storage Spaces are not supported) | ||
; | ; Newly supported applications: | ||
: Microsoft Exchange Server 2013 Service Pack 1 (SP1) [[File:exchange2010.gif]]. See [http://wiki.sepsoftware.com/wiki/index.php/Exchange SEP sesam Exchange] for further details. | : Microsoft Exchange Server 2013 Service Pack 1 (SP1) [[File:exchange2010.gif]]. See [http://wiki.sepsoftware.com/wiki/index.php/Exchange SEP sesam Exchange] for further details. | ||
: SAP HANA (SEP sesam is [http://global.sap.com/community/ebook/2013_09_adpd/enEN/search.html#recordid=2985 SAP HANA certified] [[File:cert_integration_sap_hana.png]] [[File:cert_integration_sap_netweaver.png]]) [[File:sap_hana.gif]]. See [http://wiki.sepsoftware.com/wiki/index.php/SAP_Hana SEP sesam SAP HANA] for further details. | : SAP HANA (SEP sesam is [http://global.sap.com/community/ebook/2013_09_adpd/enEN/search.html#recordid=2985 SAP HANA certified] [[File:cert_integration_sap_hana.png]] [[File:cert_integration_sap_netweaver.png]]) [[File:sap_hana.gif]]. See [http://wiki.sepsoftware.com/wiki/index.php/SAP_Hana SEP sesam SAP HANA] for further details. | ||
Line 112: | Line 112: | ||
=== <span style="color:darkgreen">GUI Enhancements</span> === | === <span style="color:darkgreen">GUI Enhancements</span> === | ||
'''New Clients and Tasks | '''New Clients and Tasks Overview''' | ||
* In the Components view, a new item '''Clients''' is available as an alternative view to the Components -> Topology. It provides an overview of all configured clients in a form of a list. See '''[http://wiki.sepsoftware.com/wiki/index.php/The_Clients_4.4 Clients table]''' for further details. | * In the Components view, a new item '''Clients''' is available as an alternative view to the Components -> Topology. It provides an overview of all configured clients in a form of a list. See '''[http://wiki.sepsoftware.com/wiki/index.php/The_Clients_4.4 Clients table]''' for further details. | ||
* In the Tasks view, a new item '''as List''' is provided as an alternative view to the Tasks -> by Clients. It shows all configured tasks by clients as a list. Tasks can be edited in the Properties dialog. They can be started immediately by clicking the Immediate Start button. See '''[http://wiki.sepsoftware.com/wiki/index.php/Tasks_As_List_4.4 Tasks As List]''' for further details. | * In the Tasks view, a new item '''as List''' is provided as an alternative view to the Tasks -> by Clients. It shows all configured tasks by clients as a list. Tasks can be edited in the Properties dialog. They can be started immediately by clicking the Immediate Start button. See '''[http://wiki.sepsoftware.com/wiki/index.php/Tasks_As_List_4.4 Tasks As List]''' for further details. | ||
Line 134: | Line 134: | ||
=== <span style="color:darkgreen">Deduplication for Linux</span> [[File:tux.gif]] === | === <span style="color:darkgreen">Deduplication for Linux</span> [[File:tux.gif]] === | ||
<!-- Description or list of backup functionality enhancements--> | <!-- Description or list of backup functionality enhancements--> | ||
SEP sesam introduces Si3 target (Si3T) deduplication for Linux | SEP sesam introduces Si3 target (Si3T) deduplication for Linux, improving your storage efficiency. See '''[[Configuring_an_Si3_Deduplication_Store|Configuring SEP Si3 Deduplication Store]]''' for further details or '''[http://badefix/wiki/index.php/SEP_Si3_Deduplication_Store SEP Si3 Deduplication Store]''' for specialized information. | ||
=== <span style="color:darkgreen">Enhanced recovery for VMWare vSphere</span> === | === <span style="color:darkgreen">Enhanced recovery for VMWare vSphere</span> === | ||
Line 152: | Line 152: | ||
=== <span style="color:darkgreen">Data Store space calculation for space check and license check</span> === | === <span style="color:darkgreen">Data Store space calculation for space check and license check</span> === | ||
The calculation of | The calculation of required disk space has been changed. It is possible to store non-sesam data on the same partition where the data store resides. Now, only the sesam data will be counted. For more information how the calculation works see the '''[[English_FAQ#Capacity_calculation_for_data_store_.28used_for_free_space_calculation_and_license_check.29|FAQ, Capacity calculation for data store]]'''. | ||
=== <span style="color:darkgreen">Granularity check for Microsoft Exchange</span> === | === <span style="color:darkgreen">Granularity check for Microsoft Exchange</span> === | ||
The enhanced granularity backup level for Microsoft Exchange allows to set and check the level of retrieved items during backup (Single Items, Mailboxes, or Databases), which may be used as a | The enhanced granularity backup level for Microsoft Exchange allows you to set and check the level of retrieved items during backup (Single Items, Mailboxes, or Databases), which may be used as a selection criteria during restore. Note that for the Exchange Server 2013, single item restore is not supported. See '''[http://wiki.sepsoftware.com/wiki/index.php/Granularity_Backup_Level_for_Microsoft_Exchange_Server Granularity Backup Level for Microsoft Exchange Server]''' for further details. | ||
=== <span style="color:darkgreen">Microsoft Data Deduplication Enabled Volumes</span> === | === <span style="color:darkgreen">Microsoft Data Deduplication Enabled Volumes</span> === | ||
Data Deduplication enabled volumes are now supported by SEP sesam. The backup of such volumes is done via [http://msdn.microsoft.com/en-us/library/hh769304.aspx#nonoptimized_backup_and_restore Nonoptimized Backup and Restore]. Client side data on | Data Deduplication enabled volumes are now supported by SEP sesam. The backup of such volumes is done via [http://msdn.microsoft.com/en-us/library/hh769304.aspx#nonoptimized_backup_and_restore Nonoptimized Backup and Restore]. Client side data on these volumes are backed up with the native size (without deduplication). | ||
=== <span style="color:darkgreen">HTTPS protocol support</span> === | === <span style="color:darkgreen">HTTPS protocol support</span> === | ||
Line 164: | Line 164: | ||
=== <span style="color:darkgreen">Enhanced Migration Options</span> === | === <span style="color:darkgreen">Enhanced Migration Options</span> === | ||
;Migration of Migration: (Migration Task Dialog) allows to migrate | ;Migration of Migration: (Migration Task Dialog) allows to migrate previously migrated savesets to a different media pool. See '''[http://wiki.sepsoftware.com/wiki/index.php/Migration_Tasks_4.4 Copy migrated savesets again]''' for further details. | ||
;Deletion after successful Migration: (Execution Parameter of Migration Task Event Dialog) triggers the deletion of the original saveset after the migration of the saveset was successful. See '''[http://wiki.sepsoftware.com/wiki/index.php/Schedules_4.4#Execution_Parameter Delete after successful migration]''' for further details. | ;Deletion after successful Migration: (Execution Parameter of Migration Task Event Dialog) triggers the deletion of the original saveset after the migration of the saveset was successful. See '''[http://wiki.sepsoftware.com/wiki/index.php/Schedules_4.4#Execution_Parameter Delete after successful migration]''' for further details. | ||
== End of | == End of Maintenance and Support == | ||
=== <span style="color:darkgreen">Obsolete SEP sesam versions</span> === | === <span style="color:darkgreen">Obsolete SEP sesam versions</span> === | ||
The following product versions are no longer supported: | The following product versions are no longer supported: | ||
Line 179: | Line 179: | ||
=== <span style="color:darkgreen">Unsupported OS</span> === | === <span style="color:darkgreen">Unsupported OS</span> === | ||
The following operating systems are no longer supported: | The following operating systems are no longer supported: | ||
* | * All 32-bit operating systems | ||
* Windows 2003 [[File:win7.gif]] | * Windows 2003 [[File:win7.gif]] | ||
* SLES 10 [[File:tux.gif]] | * SLES 10 [[File:tux.gif]] | ||
Line 186: | Line 186: | ||
* Debian Squeeze [[File:tux.gif]] | * Debian Squeeze [[File:tux.gif]] | ||
'''NOTE''': ''SLES 11 SP2/SP3'' is still supported. The limitation applies only to SEP sesam | '''NOTE''': ''SLES 11 SP2/SP3'' is still supported. The limitation applies only to SEP sesam server systems and does not affect SEP sesam clients. For a complete list of supported SEP sesam clients, see [[SEP_sesam_OS_and_database_support_matrix_4.4| SEP sesam Support Matrix]]. | ||
=== <span style="color:darkgreen">Discontinued extensions</span> === | === <span style="color:darkgreen">Discontinued extensions</span> === | ||
The following extensions are no longer supported and cannot be included in backup: | The following extensions are no longer supported and cannot be included in a backup: | ||
* Ingres | * Ingres | ||
* Marathon Everrun | * Marathon Everrun |
Revision as of 22:09, 28 October 2014
What's new in SEP sesam release 4.4.1
SEP sesam provides extended support for VMWare vSphere that enables instant VMware vSphere recovery as well as single item restore. Si3 Si3 target deduplication for Linux is introduced. SEP sesam GUI has been enhanced to provide better overview of the configured tasks and clients. Additionally, new options for customizing the GUI are now available. For details, see Enhancements and changes.
Upgrades and licensing
Direct upgrade for versions 3.6/4.x to version 4.4.1 is supported. Latest released versions are:
- SEP sesam 4.4.1.26 Windows - Released: August 29th, 2014.
- SEP sesam 4.4.1.25 Linux - Released: August 27th, 2014.
SEP sesam server and client components should be upgraded to the latest version during the regular upgrade process. This ensures the highest possible protection of the SEP sesam clients. Customers with a valid license are eligible for a free SEP sesam upgrade for any new release until the license is valid. See also Automatic Update.
Known Issues and Limitations
Known Issues: |
In SEP sesam V4.4.1.22, the 'VSS' option for 'Windows Server 2012 R2' clients cannot be set.
To fix update problems on Debian systems:
|
Enhancements and Changes
SEP sesam Server requirements
- Java 7 or higher required
- SEP sesam Server and GUI require Java 7 or higher to work properly. Java 6 is not supported.
- 64-bit OS required
- SEP sesam Server requires a 64-bit OS.
New supported systems
SEP sesam Server 4.4.1 now also supports the following operating systems and applications:
- Newly supported operating systems
- Windows Server 2012 R2
- Path Backup and Restore of Windows 2012 Volumes on Storage Spaces (Disaster Recovery of Storage Spaces are not supported)
- Newly supported applications
- Microsoft Exchange Server 2013 Service Pack 1 (SP1) . See SEP sesam Exchange for further details.
- SAP HANA (SEP sesam is SAP HANA certified ) . See SEP sesam SAP HANA for further details.
- Novell GroupWise 2014 . See SEP sesam GroupWise 2012/2014 for further details.
You can download SEP sesam for Windows at download SEP sesam. For a complete list of supported OS and databases, see SEP sesam Support Matrix.
GUI Enhancements
New Clients and Tasks Overview
- In the Components view, a new item Clients is available as an alternative view to the Components -> Topology. It provides an overview of all configured clients in a form of a list. See Clients table for further details.
- In the Tasks view, a new item as List is provided as an alternative view to the Tasks -> by Clients. It shows all configured tasks by clients as a list. Tasks can be edited in the Properties dialog. They can be started immediately by clicking the Immediate Start button. See Tasks As List for further details.
The lists can be sorted, filtered, and printed. Optionally, additional columns can be added to get as much information about the configured Clients and Tasks as possible.
Customized Fonts and Lists
In the menu bar Configuration -> Defaults, a new tab Fonts and Tables is available in the Defaults dialog. You can change the font style, table striping and table row spacing of the entire GUI.
Changed GUI file name
GUI file name has been changed: GUI JAR files sm_gui.jar and sm_lib.jar have been replaced with sm_ui.jar.
Refresh Button in all Task Dialogs (since V4.4.1.25)
The Main Log tab of task/restore task/migration task dialog can now be reloaded using either the F5 button or the Refresh button on the lower left corner.
Deduplication for Linux
SEP sesam introduces Si3 target (Si3T) deduplication for Linux, improving your storage efficiency. See Configuring SEP Si3 Deduplication Store for further details or SEP Si3 Deduplication Store for specialized information.
Enhanced recovery for VMWare vSphere
For VMWare vSphere, single item recovery and instant VM recovery is introduced.
- Single Item Restore
- allows you to restore individual items without having to restore the complete saveset. See Single Item Restore for further details.
- Instant VM Recovery
- allows you to start a VM instantly and move it via vMotion. See Instant VM Recovery for further details.
Soft reset CBT
CBT soft reset is included in the virtual machine task definition of the GUI, providing an option to reset the CBT without shutting down the virtual machine. See Reset CBT for further details.
Included VDDK 5.5.1 for Windows
The new SEP sesam installation package already includes the Virtual Disk Development Kit (VDDK) version 5.5.1 for Windows. The VDDK 5.5.1 is packaged as a compressed archive (.zip) for Windows 64-bit OS. If a VDDK is already present on the system to which the SEP sesam software is going to be installed, the previous VDDK version will be uninstalled and the VDDK 5.5.1, included in the SEP sesam package, will be unpacked. See VDDK 5.5.1 for further details.
Data Store configuration
Optionally, positive values can be used to specify watermarks and data store capacity. Note that for Si3T data store only positive values can be defined, while negative values can still be used for non-Si3T data stores. See data store configuration for further details on how to configure a data store.
Data Store space calculation for space check and license check
The calculation of required disk space has been changed. It is possible to store non-sesam data on the same partition where the data store resides. Now, only the sesam data will be counted. For more information how the calculation works see the FAQ, Capacity calculation for data store.
Granularity check for Microsoft Exchange
The enhanced granularity backup level for Microsoft Exchange allows you to set and check the level of retrieved items during backup (Single Items, Mailboxes, or Databases), which may be used as a selection criteria during restore. Note that for the Exchange Server 2013, single item restore is not supported. See Granularity Backup Level for Microsoft Exchange Server for further details.
Microsoft Data Deduplication Enabled Volumes
Data Deduplication enabled volumes are now supported by SEP sesam. The backup of such volumes is done via Nonoptimized Backup and Restore. Client side data on these volumes are backed up with the native size (without deduplication).
HTTPS protocol support
In addition to the standard FTP protocol (2 ports required), HTTP/HTTPS protocol backup/restore is now supported (1 port required). See How to configure a client for further details.
Enhanced Migration Options
- Migration of Migration
- (Migration Task Dialog) allows to migrate previously migrated savesets to a different media pool. See Copy migrated savesets again for further details.
- Deletion after successful Migration
- (Execution Parameter of Migration Task Event Dialog) triggers the deletion of the original saveset after the migration of the saveset was successful. See Delete after successful migration for further details.
End of Maintenance and Support
Obsolete SEP sesam versions
The following product versions are no longer supported:
- SEP sesam 4.0
- SEP sesam 3.6
- SEP sesam 3.4
- SEP sesam 3.0
The support for the following product versions will end soon
- SEP sesam 4.2.1 (December 31st, 2014)
Unsupported OS
The following operating systems are no longer supported:
NOTE: SLES 11 SP2/SP3 is still supported. The limitation applies only to SEP sesam server systems and does not affect SEP sesam clients. For a complete list of supported SEP sesam clients, see SEP sesam Support Matrix.
Discontinued extensions
The following extensions are no longer supported and cannot be included in a backup:
- Ingres
- Marathon Everrun
Major fixes and changes
- See Changes at SEP sesam 4.4.1