Archive:Release Notes 3.4: Difference between revisions

From SEPsesam
Line 60: Line 60:


== Backup client for OES Linux and OES Netware ==
== Backup client for OES Linux and OES Netware ==
* Novell OES2 provides a TSA for ''eDirectory'' backup. So SEP sesam can use this TSA as for '''NetWare''' now. The workaround using '''ndsbackup''' utility is not necessary any more.
* Novell OES2 provides a TSA for ''eDirectory'' backup. So SEP sesam can use this TSA as for '''NetWare''' now. The workaround using the '''ndsbackup''' utility is no longer necessary.


== Sesam extensions ==
== Sesam extensions ==

Revision as of 06:36, 23 September 2008

Important hint

Attention: Sesam doesn't use Archive bit on Windows

Sesam uses now an internal timestamp to decide which files to save during incremental and differential backups

Installation

  • Support of OpenSuSE 10.3 as Sesam Server.
  • Tru64 and FreeBSD 4 are no longer supported as Sesam Server platforms
  • IBM Java Runtime can be used instead of SUN JRE
  • With the Release of Sesam Kit 3.4.x.x-windows_x64 (64-Bit binaries) some extra requirements arise:
  1. Requires x64 architecture-based computer with Intel processor that supports Intel 64 architecture (formerly known as Intel EM64T) or AMD processor that supports the AMD64 platform
  2. Update on Windows x64 with an existing Sesam x86 (32-Bit) installation is not possible. Please de-install the 32-Bit Sesam installation before installing the 64bit release.
  3. Installation of Sesam Server on Windows x64 requires Java 1.6 x64 (Java x86 (32-Bit) will not be recognized!)
  4. Backing up native MS SQL Server 2005 on x64 requires x64 Sesam Client.
  5. Backing up MS Exchange Server 2007 requires installation of the Exchange Server Management Tools (32-Bit) on a computer that has a 32-Bit processor.

Update

  • Before starting update of Sesam Server make sure, that SESAM_BACKUP has been executed successfully.
  • The communication between Sesam Server and GUI has been changed, therefore the Sesam GUI client must be updated after the server update, as well.
  • Also Sesam GUI from 3.4 will no longer connect to a 3.0 server.
  • Verify that you have a valid update license or current Update Support Services from SEP.

GUI

  • New communication protocol between Sesam RMI GUI Server and GUI Client (see https://cajo.dev.java.net/)
  • Only one TCP port is used for communication, so ssh tunnel and firewall setup become much easier
  • One GUI Client can connect to several Sesam Servers using different databases
  • Last backup status of a task and of all tasks of one client are visualized under GUI->Tasks->by Clients
  • Actual amount saved by running backup/restore tasks is displayed in job status screen
  • Broken backups can be restored, without making changes in Sesam Database
  • Throughput of drives on a Remote Device Server is displayed
  • All GUI actions are logged on Sesam Server into sm_gui_server.lgc
  • Backup of a task from Sesam client locked for backups doesn't result in an error. (this was an user decsion)

Sesam Server

Saveset migration

  • Protocol of every saveset copy will be found under Status -> Migration

Storage pools

Sesam disk media pool (DISK_HARD) can now use more than one partition. To enable this function a new directory type Storage pools has been introduced. A media pool can be spread over multiple Storage Pools.

  • Saveset and media sizes are correct for data amount > 2TB

Backup client for UNIX

  • exclude directories by .nosbc file on client side became the default. You can switch off this behaviour by entering -o noexcl switch under Task-> Options -> Backup Options

Backup client for Windows

  • During update, owner of service SEP Sesam Server is no longer changed. Fixes problem regarding insufficient user rights that caused MS-Exchange backups to fail after update.
  • Support of 64 bit Windows
  • Fixed the problem that sometimes skipped files during restore.
  • Unicode backup client is the default now (expected in version 3.4.1.31)
  • Sesam doesn't use Archive bit any more for incremental and differential backups. This can be switched, if necessary. The use of archive bit may be reset with
sql "update defaults set value='yes' where key='with_archive_bit'"

See also the English FAQ.

See also the erman FAQ.

Backup client for OES Linux and OES Netware

  • Novell OES2 provides a TSA for eDirectory backup. So SEP sesam can use this TSA as for NetWare now. The workaround using the ndsbackup utility is no longer necessary.

Sesam extensions

Zarafa Groupware Server

Sesam can make online backups from Zarafa Groupware Server. In case of restore, single mails or complete user mailboxes can be recovered.


VMWare ESX Server

Sesam can save guest computers from VMWare ESX Server.


VMWare Consolidated Backup

Sesam can save guest computers from VI3 over VMWare Consolidated Backup

Known issues

Downgrade of SEP sesam version is not possible
FIX: Is not available, downgrade is not supported!
WORKAROUND: Do a full Sesam backup (bin, skel and var directories) before update. Restore this backup.
Cancel of restore and migration tasks doesn't work correctly
WORKAROUND: Stop Sesam, e.g. with 'sm_shutdown'
Remote Device Licenses aren't counted correctly
FIXED in 3.4.1.26.
ACLs from encrypted savesets are not restored correctly on LINUX
FIXED in 3.4.1.26
Task status screen hangs if total data amount saved at one Sesam day is larger then 2TB
FIX: Update sm_rmigui.jar from http://download.sep.de/servicepacks/3.4/gui
FIXED in 3.4.1.28.
New installation LINUX on X86_64 will fail because group sesam is created to late
WORKAROUND: Create group sesam by groupadd -r sesam before starting RPM installation.
FIXED in 3.4.1.28.
GUI update function in GUI itself doesn't work
WORKAROUND: Copy sm_rmigui.jar on OS level from server to GUI client.
Missing dependency for mt-st package in RedHat RPMS but mt command is needed by Sesam Server and RDS
FIX: Install mt-st package manually.
FIXED in 3.4.1.29.
In the Drives->New drive dialog the FQDN hostname can be selected for Device Server even if this name is not used as client name
WORKAROUND: Select the correct Sesam server name.
In the Archive Adjustment dialog you couldn't select a valid drive, because Sesam offers the internal loader drive number instead of Sesam drive number
WORKAROUND: Leave the drive selection empty. Sesam will then select correct drive itself.
'Standard' Edition > Problem in Queue_Manager with restriction to 5 global streams
APPEARED: in 3.4.1.26
FIX: sm_config_drives patch revision 1.142 or higher
FIXED in 3.4.1.30.
Full restore of ESX-Server doesn't work correctly
WORKAROUND: Select toplevel directory in restore wizzard instead

History

You will find complete CVS change reports here

v3.4.1.41

BUGFIX: Backups of clients in a task group behind a client, which is locked for backups are started correctly. In Sesam 3.4.1.39 they were silently ignored

BUGFIX: License order is corrected. Because of a missing license check Open-Xchange backup needed a Scalix license.

BUGFIX: Fix core dump during End-of-Media, if more then 10 parallel backups are running.

NEW: The default backup interface can be saved in GUI

v3.4.1.39

BUGFIX: FQDN name couldn't be entered for client name, because filtering invalid characters doesn't accept '.' any more.

NEW: Easy to use template file for sm_disaster interface.

CHANGE: Better log function in SMS. Former log function in Sesam SMS module could cause a slow down in backup speed, especially on Solaris.

CHANGE: Message invalid path specification from sbc for Windows will be interpreted as an error instead of warning.

BUGFIX: Fix core dump during exit of sm_data_server. On Windows sm_data_server sometimes cores during exit log log function.

BUGFIX: Sesam UNIX installation with tar-ball: Because of a change in sm_setup for support of whitespaces in temporary path on Windows, installation on UNIX/Linux failed. Installation by RPM wasn't affected.

BUGFIX: Backups a Windows client from an UNIX Server failed with message SBC logging without final state message, if single port connection was used.

BUGFIX: Avoid deadlock in sm_ctrlc. Sometimes remote access by sm_ctrlc didn't finish properly, causing failed backups.

BUGFIX: Adjust EOL of a medium after saveset copy affected EOL of source pool: The EOL of source medium was set to EOL of target pool. Now EOL of source medium isn't changed any more.

BUGFIX: Media pool could be deleted, even if it was still referenced from a task event: Now reference is checked before.

CHANGE: All database DELETE statements are checked for a valid WHERE clause, to avoid deletion of database records from GUI.

CHANGE: SPARE pools aren't offered as target for backups any more, because they shouldn't be used for regular backups.

BUGFIX: All Sesam clients can be selected as Remote Device Server in Loader Properties: Before only Sesam server could be selected

BUGFIX: Performance data was read to often from a RDS, causing error E001-WATCH Performance data with invalid format. Underlaying problem was ERROR: CTRLD reply: 2008-08-14 19:46:09: scm-1133: Error: Denying service. Maximum active connection reached.

v3.4.1.31

BUGFIX: In GUI->Tasks->Properties: Saving an existing task under a new name and deleting it at once could cause deletion of all tasks not referenced in Sesam database elsewhere.

BUGFIX: New entry in build_host in sm.ini could result in a syntax error during source of sm.ini from shell. This caused failure of some Sesam scripts like sm_os_startup and sm_notify

v3.4.1.30

NEW: OES-Linux can use tsafs to backup eDirectory

CHANGE: Incremental and differential backups of Windows clients using internal timestamp instead of archive bit

NEW: Backup source for Zarafa mail server can be selected by client browser

BUGFIX: A different port for CTRL access can be set in Clients->Properties->Access options again

BUGFIX: Avoid race condition during EOM, which could block all media change operations

BUGFIX: Check stpd listen port for empty or NULL value. Before an empty value wasn't recognized and backup failed because of missing stpd port specification

v3.4.1.29

BUGFIX: Automatic load of tape failed, if no tape was in drive.

BUGFIX: Add package mt-st (including the mt command) as dependency of SEPsesam RHEL RPMs.

BUGFIX: Change '*' and '/' in Zarafa mail subject lines, so GUI can show them correctly

BUGFIX: GUI update function in GUI itself doesn't work

NEW: File system browser creates correct exclude list for NetWare clients

v3.4.1.28

BUGFIX: Create OS group sesam before OS user sesam, because user should become member of group. Only relevant for Sesam server with PostgreSQL as Sesam DB.

CHANGE: write exlude list of SESAM_BACKUP as regular expression for UNIX servers. Avoids that sbc_find walking into work and tmp directory, which can causing errors during SESAM_BACKUP

BUGFIX: GUI Update function works correctly again

BUGFIX: Edit of Sesam interfaces doesn't include trace messages

BUGFIX: Task status screen hangs, if total data amount saved at one Sesam day is larger then 2TB

BUGFIX: Arguments of Command Events are transfered correctly to Sesam client

v3.4.1.27

BUGFIX: Sesam Server on some i386 Linux platforms (RHEL 4, SLES 8...) were linked with shared sqlite library. This causes problems, if no sqlite package was installed on the server too. Now library is linked statically.