Archive:Release Notes 3.6

From SEPsesam
Revision as of 14:19, 9 October 2009 by Ee (talk | contribs) (→‎History)

SEP sesam Release 3.6

New Systems Now Supported

  • Windows 2008 R2
  • SuSE Enterprise Server 11
  • Debian Lenny

Withdrawn Sesam Server Support

SEP sesam Server package installation and support is no longer offered on the following systems:

  • SLES 7
  • RHEL 3
  • FreeBSD 5/6
  • all Linux with glibc < 2.1
  • Windows 2000
  • OpenSuSE 10.3 (this was never officially supported)

This does not affect SEP sesam Client packages. For a definitive list of supported SEP sesam Clients please see SEP sesam Support Matrix


End of maintenance announcement for SEP Sesam version 3.0

Maintenance for SEP Sesam version 3.0 will end on 31. Dec 2009. This does not affect SEP sesam client packages for which there are no newer versions available.

End of Support

Support for SEP sesam Server 3.0 will end on 31. Aug 2011. For supported operating systems and client support see the SEP sesam support matrix

Known Issues

  • Attempted interrupts of migrations and restore will not work, they will continue until completion.
  • Saveset Copy and Migration



Attention Saveset Copy and Migration

Functionality of Migration has been enhanced. Existing migration tasks are now entered into new tables during database update. However, it is recommended that you check for all previously entered migration tasks after the update in the GUI.


Included Sesam extensions

The following Sesam extensions are now included in all base installation packages:

  • MySQL
  • Open LDAP
  • Open-Xchange
  • Scalix
  • Zarafa

So there is no need for installing them from the extensions directory.

New features

Backup status

More flexible display of backup results.

  • Select only results of a task or task group
  • Tree table to show only backup group results
  • Hide migrations and media result entries
  • Visible columns can be selected

Command Line Interface

SEP sesam can now be configured completely by command line. Please read the Command Line Interface documentation

Migration

The 'saveset' migration has been completely redesigned. In particular, more selection filters have been added:

  • Task
  • Task group
  • Media label

Migration now uses its own internal database tables and no longer uses those from the restore function.

Enhanced GUI logging

All GUI actions are now logged on SEP Sesam server side

Ingres

New SEP sesam module for online backups of Ingres databases.

Media read check

The new function Media read check allows regular 'read verification' checks of written media.

GUI

  • Online help now links to SEP WIKI.
  • For Novell clients login information can be entered task based. This is useful if eDirectory and filesystem backups require different authorization.
  • Selection of backup source for VCB by GUI is possible.
  • The Client browser can be used to select an MS SQL database as a backup source.
  • The new window Job State - Media Actions allows you to get an overview regarding media related actions, e.g. introduction of a media.
  • All Job State - xxx windows are redesigned to allow individual adaption of visible columns, sizes and filters.
  • The spinners for date time and the underlying calendar function are improved, e.g. usability and only valid entries are accepted.

Other

  • Faster restore from DISK devices
  • Datamover can now be used for Novell backups on Linux, as well. This allows Failover support on clustered Novell Linux Open Enterprise servers.
  • In case of a backup of a task type which does not support DIFF/INCR the level is automatically adjusted to backup level COPY.
  • As sbc for Windows is now fully supporting file names coded with Unicode the special Windows task type win32-unicode with backup command sbc_uc.exe is removed. In case of an update the tasks with type win32-unicode will remain but as soon as Windows clients are updated to version 3.6 the task type in the already defined backup tasks should be changed into 'Path'.
  • If a Windows backup protocol ends with state warning due to open files then the use of VSS Snapshots should be taken into account. In general backups should be configured to end with final state successful and all other states must be avoided.
  • Windows System Tray is fully redesigned and now available on x86 and x64, see http://wiki.sepsoftware.com/wiki/index.php/System_Tray.

Fixed Issues

You will find the complete change report generated by CVS in the download center.

  • Media could be overwritten during migration.
  • Set semaphore before modifying sms.ini file to avoid corruption, if more then one sm_config_drive process is working on it (e.g. Cluster).
  • Restart media init, if tape trailer could not be read. Avoids failed backups because data couldn't be appended on tape.
  • Check for fatal hardware errors from sm_loader and return with error in this case, instead of increasing EOL of medium and requesting next one.
  • Adjust EOL of a backup medium only, if new EOL is after current EOL.
  • Don't remove LIS files of migrated savesets if saveset is already in state 'M'.
  • Speed up display of restore tree in 'Restore Wizard': Call all functions by reference instead of value because copy of input structure requires too much time.
  • For generation restore: Avoid selection of files from generation select file including saveset id in file name.
  • Allocate only real line length of LIS file, instead of maximum line length to avoid out of memory problem during creation of select list.
  • Do not kill init script itself during /etc/init.d/sesam restart on SEP sesam client.
  • Improved transfer of selected file list to RDS. Old transfer of file list was time consuming if a huge amount of files was selected.

System requirements

  • Java Runtime Environment >=1.6 for SEP sesam server and GUI
  • .NET Framework 2.0 Redistributable (x86)/(x64) for SEP sesam server (New system Tray): Microsoft Download: (x86) (x64)
  • min. of 2 GB free disk space

Update

  • Before starting the update of the SEP sesam Server version make sure that SESAM_BACKUP has been executed successfully.
  • Check for a valid update license.
  • JRE 1.6. - Please check the Sesam/JRE support matrix.
  • The communication between Sesam Server and GUI has been changed, therefore the Sesam GUI client must be updated after the server update, as well.
  • Note: The Sesam GUI from 3.6 will no longer connect to a 3.4 server.



Note

SEP sesam GUI Jar file has been divided into two parts. So the JAVA 'Class Path' must be changed:

UNIX

  <SESAM_ROOT>/bin/gui/sm_gui.jar:<SESAM_ROOT>/bin/gui/sm_lib.jar

Windows

<SESAM_ROOT>\bin\gui\sm_gui.jar:<SESAM_ROOT>\bin\gui\sm_lib.jar


History

You will find complete CVS change reports here

v3.6.4.8 (Windows)

BUGFIX: sbc restore with relocation for pathes with > 260 chars

NEW: Support for 'Windows Server 2008 R2' - entry in Sesam Database to show correct OS in GUI.

v3.6.4.7 (Windows)

BUGFIX: Exclude pattern matching did not work properly

BUGFIX: Restore with pathes > 260 chars could fail

BUGFIX: During restore after MTF stream was completely processed the last processed block was checked again and if block started with a 4 letter MTF stream ID then further processing failed.

v3.6.4.6

First released 3.6 Kit.