$Id: readme_win32_srv.txt,v 1.24 2009/05/04 08:15:13 miraculix Exp $ SEPsesam Server V 3.4.X.Y on Windows XP, Windows 2000/2003/2008 - x86 / x64 Installation Guide and Release Notes ==================================== 1. Installation Guidelines ========================== Basic Requirements: - Java Run Time Environment 1.4.2 or later You will find a suitable version of this program package under :\win32\utils - Login with administration privileges. - Supported operating systems: Windows 2000, Service Pack 3, Home, Professional or Server Windows XP Windows Server 2003 (x86/x64) Windows Server 2008 (x86/x64) Install SEP sesam Server using the following steps: 1. Change into the CD directory :\win32 2. Extract the files with a call of sesam-srv-3.4.X.Y.-windows.exe for x86 or a call of sesam-srv-3.4.X.Y.-windows_x64.exe for x64 systems. 3. The installshield will start automatically. Please follow the instructions during installation. Attention: While installing a SEP sesam server a client and a tapeserver will be installed too. Important Note: If you want to use a tape library on Windows 2000/2003/2008 or Windows XP you must deactivate the "Removable Storage Service" on your system! 2. Update Guidelines ==================== Please install the Update kit using the same steps as described under "1. Installation Guidelines". The installshield programm will recognize your installation and an update will be performed. 3. Release Notes ================ See detailed release notes under: http://wiki.sepsoftware.com/wiki/index.php/Release_Notes_3.4 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 is now 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 displayed under GUI->Tasks->by Clients * Actual amount saved by running backup/restore tasks is displayed in job status screen * Aborted 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. * Memorize user specific window positioning and size. Sesam Server Saveset migration * Protocol of every migration saveset copy will be found under Status -> Migration Storage pools * Sesam disk media pool (DISK_HARD) can use more than one partition now. To enable this function Storage pools have been introduced. A storage pool is a directory. 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 feature with '-o noexcl' switch under Task-> Options 1 -> Save Options. Backup client for Windows * During update the SEP Sesam Server service owner account 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 problem that sometimes files could be skipped during restore. * Sesam doesn't use the Archive bit any more for incremental and differential backups. This can be switched on, if needed. * Exclude directories by nosbc file on client side became the default. You can switch off this feature with '-o noexcl' switch under Task-> Options 1 -> Save Options. * With the Volume Shadow Copy Service (VSS) opened files can be consistently backed up under Windows. Windows creates a temporary, non-persistent snapshot (shadow) of the volumes which is then backed up. This behaviour is switched on with '-o vss' switch under Task-> Options 1 -> Save Options. In the saveset the data is stored with original location, e.g. "C:\". The total amount of VSS snaphosts is limited by the operating system: * under XP only one set (with multiple volumes) is allowed, * other oper systems allow up to 64 sets. ATTENTION: If the limit of the total amount of created volumes is exceeded -- the total includes the eventual, permanently created vss spapshot/Shadow Copies -- then a VSS backup will fail. As VSS uses the Copy-on-Write method only, the amount of space for data which is changed during backup is needed as additional space during backup. The non-persistent snapshot disappears after the backup and does not occupy a volume identifier. Differential and incremental backups are processed on the shadow. The restore is unchanged because the saveset has stored original paths. See: * "How Volume Shadow Copy Service Works" http://technet.microsoft.com/en-us/library/cc785914.aspx * "Shadow Copy" http://en.wikipedia.org/wiki/Shadow_Copy * Unicode encoded file names are now fully supported with the backup type 'Path Backup'. * The backup type "win32-unicode" is still supported in Version 3.4 for backward compatibility. * SEP sesam BSR (SBMR) 2.0 for Windows 32 and 64 Bit system Volume backup is supported. Database modules 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. Known issues * Downgrade of SEPsesam version is not possible. * Canceling a restore or migration task sometimes doesn't abort the task correctly.