============================================================================== Tivoli Storage Manager (TSM) Windows Backup-Archive Client README Version 5 Release 1, Level 6 PTF IP22660 Licensed Materials - Property of IBM (C) Copyright IBM Corporation 1990, 2003. All rights reserved. Welcome to the Tivoli Storage Manager Version 5.1 Windows Backup-Archive Client! ============================================================================== This Readme is divided into the following sections: 1. Before You Install Your Client - Warnings - Client Components - Software Requirements - Hardware Requirements - Application Program Interface (API) - Migration Information - Web Backup Archive Client 2. Installing the Client - Installing the Client - Setup - Uninstalling the Client 3. Late-Breaking News - What's New - Documentation Updates - Known Problems and Limitations 4. Getting Help - Online Help - Platform Specific Documentation - Product Documentation - Technical Support 5. Trademarks 6. APARS resolved --------------------------------- 1. Before You Install Your Client --------------------------------- Warnings -------- - Data that has been backed up or archived from a TSM V5.1 client cannot be restored or retrieved to any previous level client, regardless of the TSM server level. The data must be restored or retrieved by a V5.1.0 or higher level client. - If you use the DES 56-bit encryption feature to encrypt your data during backup or archive, you *must* have the encryption key in order to restore or retrieve the data. If the encryption key is not available on the client machine (via the ENCRYPTKEY option) and you forgot the key, then the data can *not* be restored or retrieved under any circumstances. - If you are migrating from a TSM V4.1.2.0 client, there is a problem with the way file names containing international characters (accents, umlauts, etc.) are stored on the TSM server that was inadvertently introduced in the TSM 4.1.2.0 client for Windows. Please see the Migration Section below to see if you are affected before installing this client. - Note to users running the "File Server for Macintosh" service: Due to differences in how the 4.2 and higher TSM clients store Mac files on the TSM server versus how prior versions stored Mac files on the TSM server, this V5.1 client may not be able to correctly restore backup versions of Mac files that were created with the pre-4.2 client. It is strongly recommended that you rename your existing NTFS file spaces that house Mac files before upgrading to the TSM 5.1 client. If you have already upgraded to the 4.2 client without renaming the existing NTFS file spaces that house Mac files, then it is strongly recommended that you perform a selective (or full) backup against your NTFS Mac volumes. - Note to DBCS users who have encountered problems backing up files with very long file names (more than 83 DBCS chars) using TSM V5.1.0 client: TSM V5.1.5 client will now allow you to back up file names up to 168 DBCS characters. However, once you have backed up files with file names more than 83 DBCS characters using the new TSM V5.1.5 client, you will NOT be able to use a downlevel client (i.e., TSM V5.1.1 or below) to restore any files you have previously backed up. You will run into various protocol errors such as "TCP/IP communications failure." Client Components ----------------- - The following components are included with the TSM Version 5.1.6 Clients for Windows: - Backup-Archive Client (GUI and Command Line Interface) - Administrative Client (Command Line Interface) - Application Programming Interface (API) - Web Client - ODBC Driver (32 bit client only) The ODBC driver is installed via a separate package. Please refer to the README.ODBC.TXT file for installation instructions. This file is avail- able in the Tivoli Storage Manager ODBC Driver install package. Software Requirements --------------------- - What client to install: +---------------------------+--------------+--------------+--------------+ | |Windows 32-bit|Windows 32-bit|Windows 64-bit| | |non-Unicode |Unicode |Unicode | | |run: |run: |run: | | |\tsmcli\win32\|\tsmcli\win32\|\tsmcli\win64\| | |winme\disk1\ |winnt\disk1\ |\disk1\ | | Windows Version: |setup.exe |setup.exe |setup.exe | +---------------------------+--------------+--------------+--------------+ |Me | X | | | +---------------------------+--------------+--------------+--------------+ |NT 4.0 | | X | | +---------------------------+--------------+--------------+--------------+ |2000 Professional, Server | | | | |Advanced Server, Datacenter| | X | | +---------------------------+--------------+--------------+--------------+ |XP Professional 32-bit | | X | | +---------------------------+--------------+--------------+--------------+ |XP Professional 64-bit | | | X | +---------------------------+--------------+--------------+--------------+ |2003 32-bit Server, | | | | |Enterprise Server, Web | | | | |Server, Datacenter | | X | | +---------------------------+--------------+--------------+--------------+ |2003 64-bit Enterprise | | | | |Server, Datacenter | | | X | +---------------------------+--------------+--------------+--------------+ - Summary of supported Windows family functions "as is" indicates that the function is not officially supported by IBM/ Tivoli Systems but may function correctly. Users are cautioned about using this "as is" function in a production environment +------------------------+-------+--------+-------+-----+-------+--------+ | | WinME | NT 4.0 | 2000 | XP | 2003 | 64-bit | +------------------------+-------+--------+-------+-----+-------+--------+ | Journal Based Backup | no | yes | yes | yes | yes | no | +------------------------+-------+--------+-------+-----+-------+--------+ | On-line image backup | no | no | yes | yes | as is | no | | using snapshot | | | | | | | +------------------------+-------+--------+-------+-----+-------+--------+ | System object support | yes(1)| yes(2) | yes | yes | yes | yes | +------------------------+-------+--------+-------+-----+-------+--------+ | LAN-free operations | no | yes | yes | yes | yes | no | +------------------------+-------+--------+-------+-----+-------+--------+ | Server-free operations | no | no | yes | no | no | no | +------------------------+-------+--------+-------+-----+-------+--------+ (1) - WinME system object support is registry and eventlog only (2) - Win NT 4.0 system object support is registry, eventlog and RSM only - HTML Help Viewer Requirements The TSM client package includes electronic versions of the client manual, README files, and other information, viewable through Microsoft's HTML Help Viewer. For Windows NT 4.0 users, if your system does not include the HTML Help Viewer, then it will be installed when you install the client. Windows Me, Windows 2000, Windows XP, and Windows 2003 already have the viewer. - Prerequisites: The HTML Help Viewer requires that Microsoft Internet Explorer version 3.02 or later be set up on the user's computer. It is not required that Internet Explorer be used as the system's default browser, or that the Internet Explorer icon be visible on the user's desktop. To obtain the latest version of Internet Explorer visit: http://www.microsoft.com/windows/ie Note that the TSM installer will not install an old version of the Help Viewer over a newer one. - Table of Contents sub-item selection: For certain entries in the table of contents you may select an item and not notice a change in position for the text displayed. There is a limitation in HTML HELP that requires topics to be in their own file. If more than one topic is contained in a file, then the HTML help viewer will bring you to the right page; but you will have to scroll down or search within that page to get to the topic. - You can also view TSM publications in HTML and PDF formats from the following location: http://www.ibm.com/software/tivoli From there, click the "Library" link, then the "Product manuals" link. - This client is supported on the following Windows versions: - Windows NT 4.0 SP5, SP6, SP6a - Windows 2000 Professional SP2, SP3 - Windows 2000 Server SP2, SP3 - Windows 2000 Advanced Server SP2, SP3 - Windows 2000 Datacenter Server SP2, SP3 - Windows XP Professional (32-bit and 64-bit) - Windows 2003 Server (32-bit) - Windows 2003 Web Server (32-bit) - Windows 2003 Enterprise Server (32-bit and 64-bit) - Windows 2003 Datacenter (32-bit and 64-bit) - Web Backup-Archive Client The Web Backup-Archive client runs in one of the following web browsers: Netscape Navigator 6.0 or higher or Netscape Navigator 4.7 with Java Runtime Environment(JRE) 1.3.1 or higher or Microsoft Internet Explorer 5.0 or higher with JRE 1.3.1_01 or higher Notes: - The Web Client will let you know if your browser does not have the correct level of JRE. For Microsoft Internet Explorer on Windows platforms, Web client will automatically download and install JRE 1.3.1_01. - If you have an older version (1.3.0 or lower) of JRE installed you must observe one of the following: 1. Uninstall any existing JREs before installing the new JRE. 2. Do not install the JRE to the same directory as the existing JRE. Installing the new JRE in the same directory as an existing JRE may cause JRE-related problems or crashes. - On UNIX platforms, the Web Client will tolerate JRE 1.3.0 and will not prompt to install a later version. If you experience problems with Web Client using JRE 1.3.0, please manually install JRE 1.3.1. Hardware Requirements --------------------- -The 32-bit Windows client requires an appropriately configured Pentium processor platform with at least 32MB of memory. The 64-bit Windows client requires an Itanium processor supporting ACPI 2.0 64-bit fixed tables. The disk storage requirements for several installation options are listed below. For the purposes of this list, 1MB is assumed to be 1,000,000 bytes. TSM WINNT\SYSTEM32 INSTALLATION TYPE DIRECTORY DIRECTORY TOTAL ---------------------------------------------------------------------- Full install (all languages) 75.5 MB 1.2 MB 76.7 MB Full install (one language) 27.7 MB 1.2 MB 28.9 MB Complete (Typical) install 26.1 MB 1.2 MB 27.3 MB Application Program Interface (API) ----------------------------------- - See readme file API.TXT. Migration Information --------------------- - Please see the TSM book "Tivoli Storage Manager for (PLATFORM) Backup-Archive Client Installation and User's Guide" Chapter 1 for migration information on: - Terminology changes - Upgrading from earlier version clients - Processing virtual mount points - Client-Server communications methods - Upgrades paths for Clients and Servers - Unicode-enabled Client (Windows) - Web Client The client books are located on the client CDs and in the client packages. They are also available on the World Wide Web at: http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html This link will take you to the Tivoli Storage Manager Technical Support Page from which you can follow "Product Information" link or the "Related Link" of "Library". - The format of the client data header has changed in V5.1 to include new service information. Once files have been backed up or archived by a V5.1 client to any Tivoli Storage Manager server, those files cannot be restored or retrieved by any lower-level client. - The requirements for running the Tivoli Storage Manager Web Client from a Web browser have been changed in V5.1. The Web browser must support Java Swing at JRE (Java Runtime Environment) 1.3.1. To run the Web Client you may need to update your browser. See the Software Requirements section of this readme for more information. - As part of a migration plan from Tivoli Storage Manager V4.2 to Tivoli Storage Manager V5.1, Tivoli Storage Manager clients and servers may be upgraded at different times. V4.2 clients can perform backup, archive, migrate, restore, retrieve, and recall functions to a V5.1 server. V5.1 clients can perform backup, archive, migrate, restore, retrieve, and recall functions to a V4.2 server. See Chapter 1 of the client books for more detailed compatibility information. - Upgrading from TSM Client version 4.x to version 5.x: Due to file name changes, using the TSM Client for the first time following an upgrade from a version 4.x client to a 5.x client initiates a file repair sequence using the installation application (MSI). After a brief installation sequence, the TSM Client is now updated with the changes and available for use. However, if the source installation media is not available locally, the following message will be encountered: "The feature you are trying to use is on a network resource that is unavailable." "Click OK to try again or enter and alternate path to a folder containing the installation package "Tivoli Storage Client.msi" in the box below." To complete a successful migration, use one of the following steps. 1. Uninstall TSM Client version 4.x before installing TSM Client version 5.x. 2. Make the original source media available to the application by either inserting the CD-ROM or extracting the FTP package to the directory in which it was placed before running this installation. 3. Place the original source media for the application on the machine by either inserting the CD-ROM or extracting the FTP package. Then indicate the location as directed by the message dialog. - Note to users running the "File Server for Macintosh" service: Due to differences in how the 4.2 and higher TSM clients store Mac files on the TSM server versus how prior versions stored Mac files on the TSM server, this V5.1 client may not be able to correctly restore backup versions of Mac files that were created with the pre-4.2 client. It is strongly recommended that you rename your existing NTFS drives that house Mac files before upgrading to the TSM 5.1 client. If you have already upgraded to the 4.2 client without renaming the existing NTFS drives that house Mac files, then it is strongly recommended that you perform a selective (or full) backup against your NTFS Mac volumes. - WARNING: If you are migrating from a V4.1.2.0 client to this client: - A problem with the way file names containing international characters (accents, umlauts, etc.) are stored on the TSM server was inadvertently introduced in the TSM 4.1.2.0 client for Windows. The symptoms include many "ANS1304W Active object not found" messages during incremental backup for files with international characters in their names. These symptoms appear after running the version 4.1.2.0 of the client. This problem is documented in APAR IC29552. For further details about this problem, refer to APAR IC29552 or file IP22151_12_TSMCLEAN_README.1ST (see below). A fix for this problem was initially made available at client version 4.1.2.12, and is included in all subsequent versions, including this client. The fix consists of the following components: - Client version 4.1.2.12, which corrects the problem so that new backup versions are stored on the TSM server with correct file names. All TSM client versions following 4.1.2.12 also contain the fix (including this client). - A clean-up utility, TSMCLEAN, which cleans up (expires) backup versions whose file names were stored incorrectly. You will not have this problem or need to run the clean-up utility if any of the following statements are true for your situation: - You are upgrading from an earlier TSM client version but have never used the TSM 4.1.2.0 client. - You are upgrading from TSM 4.1.2.0 but are *not* experiencing the symptoms of this problem. - You are installing TSM for the first time. - You have already experienced the problem, but have since ran the clean-up utility and subsequently used client version 4.1.2.12 (or higher). If you are upgrading from TSM 4.1.2.0 *and* you are experiencing this problem, then you should obtain and run the clean-up utility prior to installing and using this TSM client. The utility is available from the IBM download site as follows: - FTP site: ftp.software.ibm.com - Directory: storage/ tivoli-storage-management/ patches/ client/ v4r1/ Windows/ v412 - Files: IP22151_12_TSMCLEAN.EXE IP22151_12_TSMCLEAN_README.1ST IP22151_12_TSMCLEAN_README.FTP Be sure to *carefully* read and understand the information in the README.1ST and README.FTP files before attempting to use the utility. After you have successfully cleaned up the problem backup versions, you can install and use this TSM client version. - Prior to installing this package, you MUST shut down any existing TSM applications that may be running. This includes (but is not limited to) the following: - TSM Scheduler - TSM Client Acceptor - TSM Remote Client Agent - TSM Journal Service - The restore of system objects backed up from 32-bit Windows environments to 64-bit Windows environments (and vice versa) is not supported. - The restore of DFS links backed up from 32-bit Windows environments to 64-bit Windows environments (and vice versa)is not supported. - When migrating from 32-bit Windows environments to 64-bit Windows environments we recommend you use different TSM node names for each environment. - Currently there is no supported Java Runtime Environment (JRE) for 64-bit Windows so the TSM WebClient cannot be run in a 64-bit web browser. However, the WebClient can be run in a 32-bit web browser on a 64-bit Windows environment with the appropriate 32-bit JRE 1.3.1 installed. - The TSM WebClient requires a web browser that supports JRE 1.3.1. You may need to upgrade your web browser in order to use this client. Web Backup Archive Client ------------------------- [NONE] ------------------------ 2. Installing the Client ------------------------ Installing the Client --------------------- - If you are installing from the CD-ROM and you have autorun enabled, the installation dialog should start when the Windows client CD is loaded. If autorun is not enabled, change to the "tsmcli\win32\winnt\baclient" ("tsmcli\win32\win9x\baclient" for Windows Me) sub-directory of the CD-ROM, type "setup", and follow the directions in the dialog. - If you are installing from an electronic image downloaded from the anonymous FTP server, the single file will self-extract to your hard drive. It is recommended that you extract files to a clean directory. The default is to expand to the "c:\tsm_images" path, but you may change the target extract location in the first dialog, before the dialog starts the install. The extraction requires 78-80 MB of disk space. The install process does not remove the expanded tree from the "c:\tsm_images" path or the user-specified location on your hard disk. - Installation of TSM requires MSI version 2.0 or higher. To determine which version of MSI is on your system, right click on the file "msiexec.exe" and select the "version" tab in the following directory: Windows ME: \WINDOWS\System Windows NT\2000 (SP2 or lower): \WINNT\System32 Windows 2000 (SP3)\XP\.Net: Ships with MSI 2.0 no upgrade necessary. - When installing TSM using GUI: MSI is upgraded when the TSM installation is launched and the version of MSI is NOT 2.0 or higher. A reboot is likely required. TSM installation continues upon rebooting the machine. - When installing TSM silently: Manual upgrade of MSI is necessary prior to silent installation. The MSI upgrade package has been provided with this version of TSM. The filename is "InstMsiW.exe". Run "InstMsiW /?" at the command prompt for a list of available parameters. The msiexec REBOOT option can specify one of the following values: - "Force" Always prompts user for reboot at installation conclusion. System automatically reboots if no user interface exists. - "Suppress" Suppresses prompt for a reboot at installation conclusion. Also, all "ForceReboot" actions encountered during installation will prompt for a reboot. The system automatically reboots at each ForceReboot encounter. - "ReallySuppress" Suppresses all reboots and reboot prompts initiated by ForceReboot during the installation. - Installing a predefined (custom) DSM.OPT file: - Users who would like to install a predefined DSM.OPT file should place a copy of the DSM.OPT file in the ...\CONFIG directory located within the install image, i.e.: tsm_images\TSM_BA_Client\baclient\Program Files\Tivoli\TSM\config. The file must be named DSM.OPT. - The install program will copy the predefined DSM.OPT file to the ..\BACLIENT directory when BOTH of the following conditions are met: - DSM.OPT does NOT exist in the ..\BACLIENT directory. The install program will not copy over an existing DSM.OPT file. - DSM.OPT exists in the install image's ..\CONFIG directory, as described above. - Install troubleshooting: - If you receive a message during setup indicating that you do not have enough free space to install on a drive that you know you have plenty of free space on you may be able to proceed by updating an entry in the setup.ini file that is included with the package. If your package is on CD you'll have to copy the entire package to a hard drive so that you can edit setup.ini. Once setup.ini is available on your hard drive you can edit it and change the line: DiskSpace=8000 ;DiskSpace requirement in KB to DiskSpace=0000 ;DiskSpace requirement in KB - If you do not see any TSM icons on the desktop after an install you should be able to click on an empty area of the desktop and press F5 to refresh the desktop display. - If near the end of the installation process, a Warning Message Box titled 'HTML 1.31 Update' displays with the text "This computer already has a newer version of HTML Help", just click on the OK button and continue. Setup ----- [NONE] Uninstalling the Client ----------------------- - IMPORTANT: It is recommended that all TSM related services be stopped before uninstalling the Tivoli Storage Manager Client. While this is not mandatory, uninstall with TSM services in operation will result in the following: - A dialog box asking the user for a reboot. - The TSM services will be stopped. However, they will remain in the services menu, but will be unavailable for use. NOTE: Uninstalling the TSM Client WILL NOT remove TSM Services. To remove TSM Services, please use the "Utilities -> Setup Wizard" menu item or "dsmcutil.exe" to remove any TSM services prior to uninstalling the client. - Open the Control Panel and double click on the Add/Remove Programs icon. In the Add/Remove Program Properties window, in the Install/Uninstall tabbed pane, choose or highlight the "Tivoli Storage Manager Client" entry in the list box and then click on the Add/Remove button. Follow the dialog instructions. (On the second panel you should click on the Remove item and then click on the Next button.) --------------------- 3. Late-Breaking News --------------------- What's New ---------- - This TSM Version 5.1.6 client contains only maintenance (APAR fixes) - The Tivoli Storage Manager Version 5.1.5 Clients contained the following new features: - AUTOMOUNT support for OS/390 - DOMAIN option enhancements - EXCLUDE.SYSTEMOBJECT option for Windows 2000 Backup-Archive Client - GPFS support for Linux x86 Backup-Archive Client - JFS user exit support for AIX Hierarchical Storage Manager Client - LAN-free support for Linux x86 Backup-Archive Client - Linux ia64 and PowerPC API support - Macintosh OS X support for long file names - Macintosh OS X support for hard links - Novell Cluster Services support - NWEXITNLMPROMPT option for NetWare Backup-Archive Client - PRESERVELASTACCESSDATE option for Windows and UNIX Backup-Archive Clients - QUERY BACKUP enhancements - Server-free commands MONITOR PROCESS and CANCEL PROCESS - Server-free data byte statistics added - Windows 2003 support Starting with version 5.1.6, Windows 2003 is supported. Refer to the "Summary of supported Windows family functions" bullet in the "Software Requirements" section of this README file for information on supported features. Note: TSM 5.2 uses a different mechanism for backing up and restoring Windows 2003 system objects. System objects backed up with the TSM 5.1 client can not be restored by the 5.2 client. Similarly, system objects backed up by the 5.2 client can not be restored by the 5.1 client. - Microsoft Dfs on XP systems TSM 5.1 supports multiple Dfs roots on a local machine - WINDOWS 2000 IMAGE BACKUP AND RESTORE - This feature is supported for Windows 2000 only. - The account running the TSM Backup/Archive Client *must* have administrator authority in order to successfully perform any type of Image Backup or Restore. - Local volumes on fixed drives with a drive letter mapping or a mount point mapping are supported. - The Windows 2000 Tivoli Storage Manager client now supports backup and restore of an entire volume as one object. This includes support for NTFS, FAT32, FAT and RAW volumes. In order to take advantage of the image backup feature the client machine must have installed the image plugin dll (piimg.dll) in the plugins directory which is located in the TSM Backup Archive client install directory. The image plugin dll is automatically installed as part of the TSM Backup/Archive client component. - TSM supports two types of Image backups: - Offline Image Backup (Image backup) (static) The volume being backed up is taken offline and is not available to any other application (system or user) except for the TSM client process. This includes applications like the Windows Explorer, cmd shells, etc. During an offline image backup the TSM client locks, backs up, and unlocks the volume. To perform offline image backups the client only needs the piimg.dll in the plugins directory. - Online Image Backup (Snapshot image backup) (snapshot) The volume being backed up remains available to other applications (system or others) during backup. In order to take advantage of online image backups the client machine must have installed and configured the Logical Volume Snapshot Agent (LVSA) plugin dll and volume filter driver. The LVSA plugin dll (pilvsa.dll) is by default installed as part of the TSM Backup/Archive client component. It is placed in the same plugins directory which contains the image plugin dll (piimg.dll). The LVSA volume filter driver must be configured via the TSM Backup/Archive client GUI Setup Wizard after the TSM Backup/Archive client has been installed and configured for general use. The LVSA allows the TSM Backup/Archive client to backup a point in time snapshot of an online (available for read and write operations) volume. While the backup is in progress, if there are changes to the volume, the LVSA copies the original data to the SNAPSHOTCACHELocation before allowing the changes to be written to the volume. After the client finishes backing up the volume, it then backs up the data copied in the SNAPSHOTCACHELocation. During restore the TSM Backup/Archive client restores the backed up volume first, then restores the data backed up from the SNAPSHOTCACHELocation resulting in a restored volume which looks the same as it did when the snapshot started. By default the TSM Backup/Archive client will use online image snapshot as its type for image backup. - Restore of an Image Backup The TSM Backup/Archive client requires an exclusive lock to destination volume being restored. The client will lock, restore, unlock, unmount, and mount the volume during a restore operation. During the restore process the destination volume will not be available to other applications. - New Options for Customizing Image Backups Name Available ========================================================== IMAGEType cmd line, gui, include.image IMAGEGapsize cmd line, include.image, dsm.opt SNAPSHOTCACHELocation cmd line, include.image, dsm.opt SNAPSHOTCACHESize cmd line, include.image, dsm.opt PRESNAPSHOTCMD cmd line, include.image, dsm.opt POSTSNAPSHOTCMD cmd line, include.image, dsm.opt SNAPSHOTFSIDLEWait cmd line, include.image, dsm.opt SNAPSHOTFSIDLERetries cmd line, include.image, dsm.opt MODE cmd line, gui For complete information on these options please refer to our client help publications. Please refer to the Product Documentation section within this readme file to learn how to access our publications. - Command Line Client (LVSA is installed) CMD Type Used ======================================================== dsmc backup image x: online dsmc backup image x: -imagetype=snapshot online dsmc backup image x: -imagetype=static offline - GUI Native and Web (LVSA is installed) Backup type Type Used ======================================================== Snapshot image backup online Image backup offline - Customizing type used by volume The INCLUDE.IMAGE option in the dsm.opt can be used to assign a management class as well as set options specific to a volume. INCLUDE.IMAGE x: imagetype=static INCLUDE.IMAGE y: imagetype=snapshot INCLUDE.IMAGE z: MGMTCLASSNAME imagetype=static INCLUDE.IMAGE c:\mnt\fs1 MGMTCLASSNAME imagetype=snapshot - Server-free data movement Image backup or image restore is capable of transferring the data over a SAN using Server-free data movement. Server-free data movement is available on a limited availability basis to customers. For hardware and software requirements or if interested in participating in the limited availability program contact your marketing or sales representative. - For complete and detailed information on Windows 2000 Image Backup and Restores please refer to our client publications. To find out how to access our client pubs please refer to the Product Documentation section within this readme file. - Journal Based Backup - Problems which have been fixed since 4.2: - Windows 2000 Mountpoints not correctly supported for journaling in all client interfaces. - Access Denied errors in the Journal Service to restricted access NTFS objects which change on journaled file systems. - Excessive output written to logs (both NT Eventlog and TSM jbberror). - Excessive memory utilization by the Journal Service process. - Journal Service can't run without at least one journaled file system online. - Journal Filesystems can't be brought online/offline via editing the config file without stopping and restarting the journal service. - New/Enhanced Journaled File System Configuration Settings: - PreserveDBOnExit A value of 1 indicates that the journaled file system journal database will not be deleted when the journal file system goes offline and will remain valid when the journal file system comes back online. This value should be used with caution as any file system change activity which occurs while the journaled file system is offline will not be reflected in the journal database. Note the journal will only be preserved when a journaled file system comes offline normally or is brought offline when the resource is no longer available and the deferFsMonStart setting is specified. If a file system comes offline due to an error such as a notification buffer overrun the journal is not preserved. The default setting is 0 (delete journal db on exit). Example configuration stanza: [JournaledFileSystemSettings.D:\] ; ; Don't delete the journal when D:\ goes offline ; PreserveDbOnExit=1 - JournalDir Directory where journal database files are stored and written. Default is the Journal Service install directory. By default this setting applies to all journaled file systems but may be overridden via an override stanza for each journal file system. If the default value is a fully qualified path (for example c:\tsmjournal) all journal db files will be written to the specified directory. If the default value does not specify a drive letter (for example \tsmjournal) the journal db files for each journal file system will be written to the specified directory on each journal file system. Example configuration stanza: [JournalSettings] ; ; Store all resources in one location unless overridden ; by an override stanza ; JournalDir=c:\tsmjournal ; ; [JournaledFileSystemSettings.D:\] ; ; Journal for d: only will be in location specified below ; JournalDir=d:\tsmjournal - deferFSMonStart Defers bringing a journaled file system online until the specified journaled filesystem is valid/available and the specified journal directory can be can be created/accessed. Also will monitor online journaled filesystems for availability and will bring the filesystem offline if it becomes unavailable. Resources are checked at the interval specified by the deferRetryInterval setting. This setting is most commonly used in a cluster environment where shared resources may move to different machines in the cluster. A value of 1 indicates the setting is on, a value of 0 indicates it is off. The default value is off. - deferRetryInterval The value in seconds journaled filesystems with the deferFsMonStart setting enabled will be checked for availability. The default value is 60 seconds. - logFSErrors Indicates if errors encountered accessing a journaled filesystem or journal directory should be logged (both to the jbb error log and the NT eventlog). Usually used in conjunction with deferFsMonStarts setting to eliminate excessive File System unavailable messages from being written to the logs when bringing a journaled filesystem online is deferred. a value of 1 indicates the settings is on, a value of 0 indicates it is off. Example Configuration Stanzas: [JournalSettings] ; ; place journal files in dir on each journaled fs ; journalDir=\tsmjournal [JournaledFileSystemSettings] ; ; journal c:, d:, and f: ; JournaledFileSystems=c: d: d:\mountpoint f: ; ; override stanza to defer starting journaling for f:\ ; until it is a valid FS; [JournalFileSystemSettings.f:\] ; ; keep db valid if fs goes offline ; PreserveDBOnExit=1 ; ; defer journaling until fs/journal dir are valid ; deferFSMonStart=1 ; ; attempt to start journaling every 120 seconds when deferred ; deferRetryInterval=120 ; ; Don't log excessive resource unavailable messages ; logFsErrors=0 Documentation Updates --------------------- - The URL listed in the Related Publications section for the location of softcopy TSM publications is incorrect and should be as follows: http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html - The default value of the NAMEDPIPENAME option is now set to "\\.\pipe\Server1". - Support for CDP Persistent Storage Manager (PSM) PSM is the snapshot technology that is included with a number of Microsoft Server Appliance Kit based NAS boxes including the IBM TotalStorage NAS 200, 300, and 300G. Starting with TSM 4.2.1 and 5.1.1 the TSM backup archive client can be used to backup the persistent images (PI) of a volume produced by PSM. The best approach to follow when using TSM to backup PSM PI's of a volume is to first ensure that the volume has a label. Then, use PSM to schedule or create a persistent image with a specific image name (ex: snapshot.daily) and to set the number of images to save to 1. PSM will overwrite the PI as needed and TSM can be used to incrementally backup the PI. In this case TSM will only backup the files that have changed between snapshots. One advantage of backing up a PSM PI rather than the actual volume is that there are no open files in the PI. Note that by default a PSM schedule will use a variable name (snapshot.%i) and keep a number of images. It is not recommended that TSM be used with PSM in this way because TSM will see each image as unique and will make a complete copy of each. TSM requires that the volume used to make the PI has a label. If the volume does not have a label you will not be able to backup its PI with TSM. Also, the TSM image backup function available starting with TSM 5.1 cannot be used to backup the persistent image. TSM's image backup can be used to backup the original volume. Note that TSM's image backup and PSM snapshots perform different functions and are complementary to each other. To avoid backing up unnecessary files when using TSM to backup PSM the following entries should be included in the TSM client option file (dsm.opt): exclude.dir "Persistent Storage Manager State" exclude.file "*.psm" exclude.file "*.otm" IC34851 - Microsoft Internet Explorer 3.0 or higher is required for the TSM command line and native GUI. This also affects TSM 4.2 Windows clients as well. This will be reflected in the next edition of the IBM Tivoli Storage Manager for Windows Backup-Archive Clients Installation and User's Guide, if appropriate. Known Problems and Limitations ------------------------------ - When using the Web Client, if you click on "Expand Entire Branch" and then click on "Collapse Entire Branch" through the View menu item in the backup or restore tree window, this may cause the browser to crash due to resource limitations. - If the administrative client is running in a different locale from that of the server, messages may contain some number of unintelligible characters. For best results, make sure the administrative client and the server are running in compatible locales. - The Tivoli Storage Manager server and clients can work across a firewall in most cases. Please see the 'Tivoli Storage Manager Firewall' subsection of the Getting Started chapter in the Tivoli Storage Manager for Unix Backup-Archive Installation and User's Guide. Currently the following operations are known to have problems when a firewall is in place: - The client scheduler operating in prompted mode does not work when the server is across a firewall. The client scheduler does work when operating in polling mode. - The server cannot log events to a Tivoli Enterprise Console (T/EC) server across a firewall. - Backup/Archive Web Client - If you get a Security Exception error when running the Web Client in your browser due to the Web Client trying to open a TCP/IP socket to a socks server, disable the proxy server via your browser settings or Java Plugin control panel. See the "Starting a Web Client Session" section in Chapter 3 "Getting Started" of the TSM B/A Installation and User's Guide for more information. - To view the non-English online help from the Web Client applet, you must install the language versions of the help files on the agent, the machine where the Tivoli Storage Manager Backup-Archive client was installed. If the language versions are not installed or are not available, the online help will be displayed in English. - Many operating systems allow non-English characters (e.g., Japanese or Russian) to be used in creating a directory or file name. In order to display these characters correctly on the Web Client applet, the machine that is running the Web browser must have the proper support (fonts) and be configured correctly to render these characters. - For browsers running on AIX, the browser machine must have the WorldType fonts (available as package X11.fnt.ucs.ttf - AIXwindows Unicode True Type Fonts on the AIX distribution media) installed. - For browsers running on Windows, the browser machine must have the Arial Unicode MS font (available for download at: - http://office.microsoft.com/downloads/2000/aruniupd.aspx) installed. - When viewing the Web Client double-byte character set online help using Netscape Communicator, re-sizing the left navigation frame in the Help browser window may cause the text in the navigation frame to become garbled. Click the 'Reload' button in your Web browser to refresh the text. - To display the Web Client in a language other than the default language on an AIX browser, change the language at login time (Options->Language). For double-byte languages (Japanese, Chinese, Korean) in particular, the browser will not work properly if the locale is changed after login. - On AIX browsers, if you have problems with the Web client when using JRE 1.3.1, check the readme on the following AIX JRE download site for information about AIX fixes you may need: - http://www.ibm.com/developerworks/java/jdk/aix/index.html - Due to Java Plug-in and/or JRE limitations, the Web client does not run on browsers on 64b-bit Windows and 64-bit AIX platforms. The Web Client does run on browsers on 32-bit Windows and 32-bit AIX platforms. - Error message "ANS1005E TCP/IP read error on socket = 10, errno = 73, reason: 'Connection reset by peer'." will be written to the error log each time when the backup/restore/archive/restore button is pressed in the Web GUI. This occurs every time on Internet Explorer browser on Windows connecting to a dsmcad running on an AIX machine. This problem does not occur with Netscape browsers. The Web Client will function correctly despite this message. - Backupsets cannot be restored via the Storage Agent at this time. When ENABLELanfree YES is specified, any backupset restores will come via the LAN path from the server. - The Tivoli Space Manager Client operations are not currently supported via the LANFree path. - On Solaris, the only supported LANFREECommmethod is TCPip (Loopback). - During a LANFree operation, CTRL-C may cause the client to hang or coredump. Do not use CTRL-C to abort a LANFree operation, instead use the 'Q' key to quit. - No Query Restore (NQR) LANFree of a small number of files/directories from a file space in which many files/directories have been backed up is currently not as fast as doing the same query with classic restore. This is because the Storage Agent has to do a search over the network of a large volume to find the few matching files within that volume. Work is being done to alleviate this performance issue in a future Storage Agent deliverable. In order to force the client to use classic restore: NQR: - dsmc rest /ssaraid5/hometest/rand/* /ssaraid5/rest1/ -sub=yes TO FORCE CLASSIC: - dsmc rest /ssaraid5/hometest/rand/?* /ssaraid5/rest1/ -sub=yes Using "?*" in the source spec. rather than "*" forces classic restore to be used, which does not have the performance problem. - When LAN Free sessions are used as part of a restartable restore, additional or unexpected prompts may appear to allow overwriting files which were restored previously; A fix will be provided via APAR to eliminate superfluous prompts. Until then, you may reply to skip files which already exist. Alternatively, you may select options to allow overwriting without prompting. Before restarting any restore, ensure that the restore is in the 'Restartable' state by issuing a Query Restore in an administrative session. Any attempt to restart a restore session that is still in the 'Active' state may not have the desired results. - When performing image backup and restore operations using LANFree, the final statistics may show that the "LanFree data bytes" are slightly higher than the "Total number of bytes transferred". This is because the LANFree bytes transferred in this case include the extra bytes required for the communication protocol between client and server. - Euro symbol (€) support - The euro symbol does not display correctly in the Command Line client. This is a Microsoft Windows limitation since the OS does not officially have a euro symbol-compatibe code page (e.g., cp858). In order to enable this support, you will need to first contact Microsoft for the cp858 file (c_858.nls) and install it under c:\WINNT\System32\ (or where ever your Windows directory is located). Then you need to modify the registry. IMPORTANT: The registry editor is not very forgiving of mistakes. If you are not accustomed to editing the registry, ask your NT administrator to make this change for you. To enable support for the 858 code page, do the following: 1) Start the registry editor. 2) Navigate to the following registry key: HKEY_LOCAL_MACHINE\ SYSTEM\ CurrentControlSet\ Control\ Nls\ CodePage 3) In the right-hand pane of the registry editor, locate the name "850". Change the value of the "850" name to the following: c_858.nls 4) close the registry editor. Reboot Windows. The TSM CMD Line should now display the euro symbol correctly. NOTE: Make sure you console is using a euro-capable font (e.g., Lucida Console). - Users running on systems that are neither Latin 1 (English, German, etc.), nor Far East (Japanese, Korean, etc.) may see that the TSM GUI menu names are question marks (??????). This is probably because support for the Latin 1 code page is not enabled. In order to enable this support, you will need to modify the registry. IMPORTANT: The registry editor is not very forgiving of mistakes. If you are not accustomed to editing the registry, ask your NT administrator to make this change for you. To enable support for the Latin 1 code page, do the following: 1) Start the registry editor. 2) Navigate to the following registry key: HKEY_LOCAL_MACHINE\ SYSTEM\ CurrentControlSet\ Control\ Nls\ CodePage 3) In the right-hand pane of the registry editor, locate the name "850". It should have a null (empty) value. Change the value of the "850" name to the following: c_850.nls 4) close the registry editor. The TSM GUI should now display the menus correctly. - When doing incremental using a UNC name, if you use wildcard "*" at the end, TSM does not backup the root directory. Always use only the full path without the tailing wildcard "*" while performing an incremental backup with a UNC name. - Local directory shares are displayed in the Backup Archive GUI and Web Client as network drives. - Restoring from a backupset from a 3570 tape library attached to the client system is not supported. - Korean fonts in boldface do not appear in bold in the WebClient. This is a known JDK 1.3 defect (see Java Bug #4341627 at http://java.sun.com). To fix the problem locally, you need to edit the font.properties.ko file where your JRE is installed. E.g. C:\Program Files\JavaSoft\JRE\1.3.1_01\lib\font.properties.ko Edit the lines: dialog.bold.0=Arial Bold,ANSI_CHARSET dialog.bold.1=\uad74\ub9bc,HANGEUL_CHARSET . . . sansserif.bold.0=Arial Bold,ANSI_CHARSET sansserif.bold.1=\uad74\ub9bc,HANGEUL_CHARSET to: dialog.bold.0=\uad74\ub9bc,HANGEUL_CHARSET dialog.bold.1=Arial Bold,ANSI_CHARSET . . . sansserif.bold.0=\uad74\ub9bc,HANGEUL_CHARSET sansserif.bold.1=Arial Bold,ANSI_CHARSET Restart your browser. - The Web Client applet runs as a snap-in on Microsoft Management Console when the Web Client agent is installed on Windows platforms only. The Web Client applet does not work in Microsoft Management Console for Web Client agents installed on non-Windows machines. - When running the TSM Web client in Internet Explorer, Asian Language characters from locales that differ from the system locale, do not display correctly. - WINDOWS 2000 REMOVABLE STORAGE MANAGEMENT (RSM) - WINDOWS 2000 REMOTE STORAGE SERVICES (RSS) - Due to a Windows 2000 issue, Tivoli Storage Manager requires the Windows 2000 server to be rebooted in order to restore the RSM database. - The -restart option for the RESTORE RSM command does not function; the administrator must restart the RSM server manually in order for the changes to take effect after restoring the RSM database files. - WINDOWS 2000 NAMED STREAMS - Tivoli Storage Manager backs up and restores named streams on a file basis only. Directories in Windows 2000 can contain named streams. Named streams attached to a directory will always be overwritten (regardless of the value of the Tivoli Storage Manager prompt option) during Tivoli Storage Manager restore or retrieve. - Backup of a named stream containing sparse file data is not supported. - Restore of a file containing a named stream to a non-NTFS5 (pre-Windows 2000 NTFS) file system will only restore the unnamed portion of the file. The named portions of the file will not be restored. - WINDOWS 2000 SYSTEM OBJECTS - The format of the data stored for the backup of the Active Directory and Certificate Server system objects has changed in TSM V5.1.5. Backups of these objects taken by a TSM V5.1.5 client cannot be restored by a previous version of the client. Backups taken by previous version of the client can still be restored by the TSM V.1.5 client. - Windows 2000 System Objects cannot be restored to alternate locations. - Backup and restore of all Windows 2000 System Objects, except the Windows 2000 Registry, require that the user have Administrator privileges. Backup and restore of the Windows 2000 Registry can be performed by a member of the Backup Operators group. - The TSM Web Client must run with an Administrator account in order to correctly backup and restore Windows 2000 system objects; the Local System account does not have the proper authority to backup and restore all of the system objects correctly. - Logical file grouping overrides the transaction limits set for both client and server. The backup of system objects which contain a large number of files, for example BACKUP SYSFILES, can place additional demands on server log file size. - Active Directory and File Replication Services perform a non-authoritative restore only. To perform an authoritative restore of the Active Directory, the Microsoft Windows Directory Service Utilities, %SystemRoot%\system32\ntdsutil.exe, may be used in conjunction with the TSM client. Please consult Microsoft for more information about using this utility. - If the Certificate Server is restored in Directory Service Restore mode and is restored via the TSM Web client, the certificate service may not start on re-boot. This does not apply if the restore is executed in the TSM client GUI. - Currently if you restore a backupset containing the COM+ DB system object from the TSM Web client, an error message will be logged to the TSM error log and displayed to the user: ANS4005E Error processing '\\stack\c$\adsm.sys\COMPDB\COMPDBFILE': file not found This message can be ignored. COM+ DB is restored correctly. - When restoring the Registry from the TSM Web client, there is an intermittent error message logged in the TSM error log: Error opening input file ???????????????????????????A??? This message can be ignored. The Registry is restored correctly. - Inactive/Point in Time restore of System Objects is only supported on Windows 2000. - JOURNAL BASED BACKUP: - A TSM V4.2 or higher server is required to execute journal based backups - Initiating a journal based backup can sometime result in "traditional" backups on directories. - The Windows NT/2000 command interpreter: Certain applications may generate delete notifications for "long" file/directory names with the compressed, short 8.3 names. Of particular concern are any legacy 16-bit Windows or DOS applications, and the Windows NT/2000 command interpreter (cmd.exe). Any files/directories deleted from a command prompt fall under this category. This compressed name does not logically identify a unique object. This can be handled by setting the "incrthreshold" option which can (when doing full file space incremental) result in such a "traditional" incremental. - After renaming a directory, both the old directory and the new directory are backed up using the "traditional" incremental. - When you move a directory, using Windows Explorer, to the recycle bin, the filesystem API reports only a delete of this one object. The files and subdirectories under this directory are not expired. If you restore from the recycle bin, this subdirectory is not backed up again. - Restoring files causes the journal to record the change activity. If the restore is using the active backup copy, the change record is deleted from the journal. When restoring with a backupset, it is not possible (without querying the server) to know if the copy of the file is the active backup copy. The net result is that if the next incremental is done using the journal, these files will be backed up again. This can be avoided by performing an incremental with the -NOJOURNAL option. - If you update the TSM Journal Service settings using either the TSM Journal Engine setup wizard or by directly editing the TSM Journal Service configuration file (tsmjbbd.ini), the TSM Journal Service must be restarted before the changes take effect. Restarting the Journal Service invalidates the current journal database and a traditional full incremental backup must be performed to re-validate it. - Backing up Windows 2000 mounted file systems does not work in the Native and Web GUI Interfaces Backing up Windows 2000 mountpoints from the native or Web GUI interfaces will always revert to traditional full incremental backup regardless of whether the mounted filesystem being backed up is being journaled by the TSM journal based backup service. Mounted file systems are correctly backed up via Journal Based Backup in the command line interface. TSM Development is aware of this problem and a fix will be made available as soon as possible. - The domain backup operation in the Backup Archive GUI and the Web client do not take advantage of the journal. A traditional incremental backup is performed instead. - Known problems with anti-virus software Some anti-virus software may incorrectly generate change notifications to the TSM Journal Service which will cause files which don't appear to have been changed to be incorrectly backed up when using Journal Based Backup. Development is currently working with virus protection vendors to fix these problems and customers should contact the virus protection software vendor and/or IBM support to report problems/vendors not mentioned below. Symantec Norton Anti-Virus (Nav) ================================ Symantec has implemented an interim fix which eliminates most incorrect change notifications generated during Nav scan processing. This interim fix is incorporated into Nav CE version 7.51 and must be obtained from Symantec technical support. Customers should refer to Knowledge Base article 4011082926 and the CRT STS number (Defect 362082, Incident 421919). Note that the initial interim fix still has generates some incorrect notifications for attribute (read-only, archive, etc) bitmask changes and requires a registry setting for Nav and a Journal Based Backup ini file setting. Note that this fix will prevent Nav from preserving the last access timestamp on any scanned objects. The Journal Based Backup service must also be configured to not generate change notifications for last accessed timestamp changes and for attribute bitmask changes. Symantec development is currently working on a complete fix to this problem which will also eliminate incorrect attribute notifications and they are hoping to have this fix available in Nav CE version 8.0. After obtaining the interim Nav CE 7.51 fix the following settings should be made: The following DWORD registry value should be set: HKLM\Software\Intel\LANDesk\VirusProtect6\CurrentVersion NoFileMod = 1 This setting prevents Nav from caching and restoring timestamps and security information during scan processing. The following Journal Based Backup ini file setting (tsmjbbd.ini) should be made: [JournaledFileSystemSettings] NotifyFilter=0x15b This setting will generate change notifications for the following type of change activity: name changes (creations, deletions, and renames) size changes modification timestamp changes security (acl) changes It will not generate notification for last access timestamp changes nor attribute bitmask changes. - Online help for Use Active Directory Lookup communication method - If you select the Use Active Directory Lookup communication method in the Communication tab of the Preferences window in the GUI, and you click the Help button, an error message is displayed. To display help for the Use Active Directory Lookup communication method, position the cursor on the Use Active Directory Lookup item in the Communication Method drop-down list, and press F1. Scroll down the help window until the description for the Use Active Directory Lookup item is displayed. - Restoring data with multiple TSM encryption keys - When restoring a group of files that have been encrypted by TSM and the user needs to input more then one encrypt key for the group, files may not be restored with an error in the dsmerror.log ANS4014E Error processing '\\spike\c$\want\dollar': unknown system error (150) encountered. Program ending. The restore will continue but the file will not be restored. The user can re-submit the restore request for the individual file to restore the file. This condition is not common. - Lower-cased characters whose upper-cased counterpart is shared with other letters should not be used in file and/or directory names. An example of such character pair are the Greek characters GREEK SMALL LETTER FINAL SIGMA (Unicode value 03C2) and GREEK SMALL LETTER SIGMA (Unicode value 03C3), both of which have the same upper-cased character, GREEK CAPITAL LETTER SIGMA (Unicode value 03A3). - After migrating from a non-unicode TSM Client to a unicode-enabled TSM Client (e.g., from TSM 4.1.2 to TSM 4.2.1), if you restore files/folders containing Double-byte characters mixed with Single-byte characters the names will be restored in mixed casing. This is only a display issue. - When starting/installing the TSM Scheduler Service, you will get an error message in the dsierror.log that states: sessOpen: error 137 from signon authentication This message can be ignored. - Microsoft Dfs limitations - Dfs does not restore root of Dfs. To recreate the Dfs tree, first manually create the root of Dfs and then start restore to recreate the links - TSM can backup Dfs tree (both domain based Dfs and stand alone Dfs) hosted on local machine only. This means you can not backup Dfs if the Dfs host server is some other machine in your domain and not your local machine. - TSM can not recreate shared folders on restore. Example: If you delete the junction and also the shared folder the junction points to then restore of Dfs root will recreate the Dfs junction but restore of a junction will create a local folder instead of creating the original backed up shared network folder. - If a Dfs link is created with replica and the replica share is on a different server, then TSM does not display the replica data. - WINDOWS 64 bit limitations - The TSM 32 bit Windows backup-archive client is not supported on 64 bit versions of Windows. The 64 bit Windows client should be used on 64 bit machines. - TSM 64 bit windows client does not support SSL - TSM 64 bit windows client does not support the TSM ODBC driver - TSM WebClient does not run in a 64-bit web browser. However, the WebClient can be run in a 32-bit web browser on a 64-bit Windows environment with the appropriate 32-bit JRE 1.3.1 installed. - WINDOWS 32-BIT AND 64-BIT INTEROPERABILITY: Windows 32-bit applications have a different HKEY_LOCAL_MACHINE\SOFTWARE registry tree from 64-bit applications. This means that the 32-bit and 64-bit TSM API are mutually exclusive and their passwords will be stored in different locations in the registry tree. So, the 32-bit API will not be able to access the password entries generated by the 64-bit API. As an example: The 64-bit BA client package will only install a 64-bit scheduler. But, another application could be using the 32-bit API. If the scheduler and application share the same node name, then the generated passwords stored in the registry in encrypted form could become out of sync. If the application changes the password, the 32-bit portion of the registry will be updated with the new password, but the 64 bit portion of the registry will not reflect this change. Therefore, to alleviate password synchronization issues between 32-bit and 64-bit Windows clients we recommend that a separate node name be used for each client. - WINDOWS 2000 IMAGE BACKUP AND RESTORE - The account running the TSM Backup/Archive Client *must* have administrator authority in order to successfully perform any type of Image Backup or Restore. - Since we require an exclusive lock during restore the TSM client can not restore an image to the system volume. Also the TSM client can not restore an image to the volume containing the TSM client installation. For these reasons it is recommended (but not mandatory) that the TSM client is installed on the system drive when possible. - The TSM client can backup a consistent snapshot of a volume, but it can not guarantee consistency of applications which store data on multiple (different) volumes. For example the TSM client can image backup drive F: but if Application A keeps its main data files on drive F:, but it's log files are on drive G:, when the TSM client restores drive F: the data files might not be in sync with what ever changes might have gone into the log files on drive G: since the image backup of drive F:. - When performing image backup and restore operations using LANFree (supported only on Windows 2000, AIX, HP and Solaris), the final statistics may show that the " LanFree data bytes" are slightly higher than the "Total number of bytes transferred". This is because the LANFree bytes transferred in this case include the extra bytes required for communication protocol between client and server. - Bad Sectors on a drive - If part of the volume resides on an area of the drive with bad sectors TSM will be skipping those sectors while sending image data to the server, displaying the warning message ANS2026W. In some rare cases an attempt to read data from bad sectors may lead to device read failure with image backup failing. If this is the case the possible workarounds are: a) If the volume is formatted (not raw) use full incremental backup instead of image backup. b) If the volume resides on an IDE drive, try moving the data to a SCSI drive. SCSI drives are more robust in terms of bad sector recovery. - Preference Editor Exclude Domain limitation (Native Gui) - In the "Backup" tab of the preference editor, domain exclusion is only supported for "Incremental" backup types. Domain exclusion is not supported on NAS or Image. It will add the option to the options file, but the option will not be honored. --------------- 4. Getting Help --------------- Online Help ----------- - Context-sensitive help is not supported for Wizards. Help is only provided for the Help button. Platform Specific Documentation ------------------------------- [NONE] Product Documentation --------------------- - Tivoli Storage Manager publications are available in softcopy Adobe Acrobat Reader format (.pdf) and HTML (.htm) format on the Tivoli Storage Manager Publications CD and at the following Web page: http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html This link will take you to the Tivoli Storage Manager Technical Support Page from which you can follow "Product Information" link or the "Related Link" of "Library". Technical Support ----------------- - To receive technical support for Tivoli Storage Manager: - Contact your Tivoli Storage Manager administrator. This should be your first step when having problems. - Your administrator will know how to contact IBM for Technical Support on your behalf. - For additional information about Tivoli Storage Manager technical support visit the technical support web site. The URL is: http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html - To participate in user discussions of Tivoli Storage Manager you can subscribe to the ADSM-L list server. This is a user forum maintained by Marist College. While not officially supported by IBM, Tivoli Storage Manager developers and other IBM support staff also participate on an informal, best-effort basis. Because this is not an official IBM support channel, you should contact IBM Technical Support if you require a response specifically from IBM. You can subscribe by sending a note to the following e-mail address: listserv@vm.marist.edu The body of the message must contain the following: SUBSCRIBE ADSM-L yourfirstname yourlastname The list server will send you a response asking you to confirm the subscription request. Once you confirm your subscription request, the list server will send you further instructions. You will then be able to post messages to the list server by sending e-mail to: ADSM-L@vm.marist.edu If at a later time you wish to unsubscribe from ADSM-L, you can send a note to the following e-mail address: listserv@vm.marist.edu The body of the message must contain the following: SIGNOFF ADSM-L You can also read and search the ADSM-L archives at the following URL: http://www.adsm.org - Anonymous FTP server IBM supports an anonymous FTP server where you can find PTF maintenance and other Tivoli Storage Manager-related materials. Three other anonymous servers are unofficially maintained by non-IBM volunteers. These servers are: - ftp.software.ibm.com/storage (primary - IBM) - ftp.rz.uni-karlsruhe.de (mirror - Germany) - ftp.wu-wien.ac.at (mirror - Austria) - ftp.cac.psu.edu (mirror - Pennsylvania) - For the latest information about Tivoli Storage Manager, visit the home page on the World Wide Web. The URL is: http://www.ibm.com/software/tivoli/products/storage-mgr/index.html ------------- 5. Trademarks ------------- - The following terms are trademarks of the IBM Corporation in the United States or other countries or both: - AIX - Application System/400 - AS/400 - Client Access/400 - DYNIX/ptx - IBM - IBMLink - NUMA-Q - Operating System/400 - z/OS - OS/390 - OS/400 - PTX - RACF - RISC System/6000 - RS/6000 - Scalable POWERparallel - SP2 - S/390 - System/390 - VisualAge - UNIX is a registered trademark of The Open Group in the United States and other countries. - Microsoft, Windows, Windows NT, Windows 2000, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. - Jaz and Zip are trademarks or registered trademarks of Iomega Corporation in the United States, other countries, or both. - Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. - Tivoli is a trademark of Tivoli Systems Inc. in the United States, or other countries, or both. - Other company, product, and service names may be trademarks or service marks of others. ----------------- 6. APARS resolved ----------------- APARs fixed in Version 5, Release 1, Level 6.0 ----------------------------------------------- IC33958 - FILESPACE TYPE "*NT5CSC" (MAPPED NETWORK DRIVE IN OFFLINE MODE ON XP) WILL SHOW UP AS "?XNT5CSC" ON THE SERVER (Q FIL F=D). IC34287 - TSM CLIENT HANGS DURING A MULTI-SESSION BACKUP. IC34295 - NON-ADMIN WINDOWS USERS CAN NOT SEE LOCAL DISKS. IC34308 - TSM PRODUCES ERROR "UNABLE TO DETERMINE CURRENT COMPRESSION STATE OF XXX DEVICEIOCONTROL: WIN32 RC=1" ON NAS MAPPED DRIVE. IC34385 - DURING BACKUP OF ACTIVE DIRECTORY, A BACKUP OPERATION MAY FAIL WITH THE FOLLOWING MESSAGE: "ANS1028S INTERNAL PROGRAM ERROR. PLEASE SEE YOUR SERVICE REPRESENTATIVE." IC34387 - TSM BACKUP-ARCHIVE CLIENT MAY CRASH WHEN PERFORMING LANFREE BACKUP. IC34415 - TSM V5.1.5 WINDOWS CLIENT PREFERENCES EDITOR FILE BROWSE BUTTON DOES NOT WORK FOR INCLUDE.IMAGE BACKUPS - MUST ENTER MANUALLY. IC34460 - ANS1183E AN UNKNOWN ERROR OCCURRED WHILE PROCESSING SYSTEM OBJECT 'WINDOWS NT DIRECTORY SERVICES'. IC34473 - DSMCUTIL RECEIVES ANS1036S IF COMMMETHOD PARAMETER IS SPECIFIED. IC34478 - TSM GUI CLIENT ANS1865E RC: -190 INVALID HANDLE SETUP WIZARD DOES NOT PROPERLY SETUP NAMEDPIPE. IC34512 - TSM CLIENT STOPS WHEN TRYING TO BACKUP SYSVOL ON WINDOWS 2000. NO ERROR LOGGED IN DSMERROR.LOG. IC34558 - GUI CRASHES IF 'PASSWORD' OPTION IS USED IN THE OPTIONS FILE AND THE SPECIFIED PASWORD IS WRONG. IC34566 - CLIENT BACKUP HANGS AND SESSION TERMINATED FROM SERVER WITH ERROR MESSAGE ANR0480W. IC34619 - WINDOWS SCHEDULER SERVICE FAILS ON STARTUP WITH EVENT LOG ENTRIES 7022 AND/OR 7031. IC34630 - 5.1 WINDOWS TSM CLIENT SCHEDULER SERVICE OCCASSIONALLY HANGS AFTER REBOOTING THE MACHINE (EVENT ID: 7022 & 7031). IC34632 - DSMERRORLOG IS FILLING UP WITH GetDfsInfo() MESSAGES WITH A RETURN CODE OF RC=1722 CAN CAUSE THE FILESPACE TO REACH A HUNDRED PERCENTAGE UTILIZATION. IC34639 - ACCESS VIOLATION DUE TO INVALID EXCLUDE SYNTAX USING UNC NAMING CONVENTION WITH 5 CHARACTER MACHINE NAME C0000005 DR. WATSON. IC34657 - ANS1341E MESSAGE INCORRECTLY DOCUMENTED IN THE TSM MESSAGES MANUAL (DELTA FILE ALREADY EXISTS ON CLIENT CACHE). IC34693 - SOME NODE INFORMATION IS NOT UPDATED AFTER A SCHEDULED BACKUP OR IF A SESSION IS LOST AND REOPENED, AFFECTING THE SUMMARY TABLE STATISTICS ON THE SERVER. NOTE: THIS CLIENT FIX REQUIRES THE CORRESPONDING SERVER FIX IC33840. IC34716 - TSM WINDOWS CLIENT INSTALLATION MAY FAIL WITH INSTALLSHIELD ERROR MESSAGE 'FAILED TO EXTRACT FILE DLL.INI FROM THE BINARY TABLE.' IC34733 - TSM JOURNAL BACKUP OF CHANGED DIRECTORY MAY BACKUP DOS 8.3 SHORT NAME INSTEAD OF LONGNAME. UNABLE TO RESTORE DIR VIA TSM BA GUI. IC34791 - TSM OSX GUI CLIENT DURING INSTALLATION WILL PLACE 'COMPRESSION OPTION' IN 'USER PREFERENCES FILE NOT SYSTEM PREFERENCE FILE. IC34806 - TRACING TO STDERR INCOMPLETE, SOME DATA STILL GOES TO STDOUT. IC34810 - TSM WINDOWS WEB CLIENT BACKUP MAY TERMINATE: ADD FIX FOR IC33280 WEB CLIENT. IC34813 - TSM WINDOWS CLIENT STOPS WITH ANS1028S. DSMERROR.LOG SHOWS "ATTEMPT TO FREE POINTER TO A FREE BLOCK." IC34833 - THE OUTPUT FROM A SCHEDULED BACKUP, 'BACKUP ACTIVEDIR' OR BACKUP SYSTEMOBJECT' DOES NOT SHOW THE NTDS.DIT FILE BEING SENT. IC34853 - TSM BACKUP OF WIN 2000 ACTIVE DIRECTORY SYSTEM OBJECT CAN REPORT SUCCESS DESPITE FAILURE DURING BACKUP ATTEMPT. IC34964 - TSM AIX CLIENT YIELD() CALLS CAUSE HIGH CPU UTILIZATION. IC34974 - ANS1305S MESSAGE IN DSIERROR.LOG DURING SCHEDULER SERVICE INITIALIZATION. IC34982 - ANS1005E ANS1809W ANR0443W ANR0529W ANR0105E ARCHIVE DESCRIPTION LENGTH LIMITATION. IC34996 - TSM BACKUP/ARCHIVE CLIENT GENERATES ANS1074I ** USER ABORT ** ERRONEOUSLY DURING SCHEDULED BACKUP. IC35051 - WINNT 5.1.X.X CLIENT IS UNABLE TO SEE THE CLUSTER DRIVES IN THE LOCAL GUI. IC35080 - IN THE PREFERENCES EDITOR OF THE B/A CLIENT GUI, INCLUDE/EXCLUDE TAB>CATEGORY: BACKUP>TYPE: THE INCLUDE.SYSTEMOBJECT IS MISSING. IC35086 - SCROLL- AND STATUSBARS FOR DELETE, RESTORE, ARCHIVE, RETRIEVE AND ARCHIVE DELETE WINDOWS ARE NOT SHOWN UNLESS YOU RESIZE. IC35087 - TSM V5.1 LANFREE CLIENT CAN COREDUMP IF HIGH RESOURCEUTILIZATION AND MANY THREADS START AT ONCE. TIMING PROBLEM AND VERY RARE. IC35099 - THE WINDOWS SYSVOL RESTORES ARE BEING RESTORED AUTHORITATIVE INSTEAD OF NON-AUTHORITATIVE. IC35148 - ARCHIVE LANFREE DOES NOT REPORT CORRECT STATISTICS. IC35157 - WINDOWS 5.1 SCHEDULER SERVICE IS SET TO A STARTUP TYPE OF MANUAL ALTHOUGH YOU SPECIFY AUTOMATIC. IC35190 - TSM CLIENT ON WINDOWS CZECH NT 4.0 CRASHES WITH ACCESS VIOLATION ON STARTUP C0000005 FCLOSEALL. IC35203 - TSM CLIENT SCHEDULED "COMMAND" EVENT SHOWS "COMPLETED" EVEN THOUGH THE COMMAND FAILED WITH NON-ZERO RETURN CODE. IC35224 - A BLANK PASSWORD IS NOT ALLOWED WHEN USING "/NTACCOUNT:" AND "/NTPASSWORD:" IN A DSMCUTIL INSTALL COMMAND. IC35252 - TSM 5.1 CLIENT DR. WATSON DURING SYSTEM OBJECT BACKUP IF MGMTCLASS FOR SYSTEM OBJECT DOES NOT HAVE A BACKUP COPYGROUP. IC35271 - API CAN ABEND AFTER FIX FOR IC34619 IN FIXTEST 5.1.5.4. IC35292 - TSM SCHEDULE SESSIONS CANCELLED VIA "CANCEL SESSION XXX" ADMIN COMMAND REPORT SCHEDULE STATUS OF COMPLETED, NOT FAILED. IC35333 - TSM WINDOWS CLIENT FIXTESTS 5.1.5.4 AND 5.1.5.6 CAN CAUSE INCORRECT ONLINE LAN IMAGE BACKUPS, CORRUPTING RESTORES. IC35376 - CORE DUMP DURING IMAGE BACKUP ON AIX CLIENT. IC35394 - 5.1.X.X WINDOWS JOURNAL DB WILL DR WATSON WHEN ATTEMPTING TO ADD MORE THAN 15 DRIVES TO BE JOURNALED. IC35417 - AN IDLE CLIENT SESSION REMAINS AFTER 5.1.5.7 CLIENT SCHEDULER SERVICE QUERIES FOR NEXT SCHEDULED EVENT. IC35555 - IMAGE BACKUP DEADLOCK HANG PRODUCER CONSUMER THREAD SWAPPED OUT WAITING ON EACH OTHER TO FILL/EMPTY BUFFERS. IC35558 - ENDING STATS OF BACKUPS SHOWS THE "TOTAL NUMBER OF BYTES TRANSFERRED:" SHIFTED TO THE LEFT. IC35561 - RESTORE FAILS W/ANR0444W WHICH STATES "OUT-OF-SEQUENCE VERB (TYPE ENDTXNRESP) RECEIVED." IC35570 - TRACING IS NOT POSSIBLE IN THE TSM ADMIN COMMAND LINE STARTING WITH 5.1.0.0 VERSION OF DSMADMC. IC35578 - JOURNAL DAEMON FAILS TO EXPIRE FILES WHERE THE DEFAULT MGMTCLASS DOES NOT HAVE AN ACTIVE COPYGROUP. IC35612 - TSM WEB CLIENT REPORTS A RETRIEVE OPERATION AS ARCHIVE IN THE TSM SERVER ACTLOG AND SUMMARY TABLE. IC35635 - IMAGE RESTORE CAN HANG WHEN CLIENT RECEIVES EXTRA UNEXPECTED DATA FROM TSM SERVER. IC35689 - AE IC34619 FIX COMPLETION EVENT ID 7022 ON SCHEDULER START UP THE TSM SCHEDULER SERVICE HUNG ON STARTING. IC35748 - TSM WIN 5.1.5.0 CLT. WITH LANG GERMAN: THE DETAILED STATUS REPORT OF THE B/A GUI SHOWS AN EMPTY AGGREGATE TRANSF. RATE (KB/s). IC35763 - ANS1448E ERROR RETURNED INSTEAD OF ANS4987E MESSAGE FOR IN USE FILE AFTER UPGRADING TSM CLIENT TO 5.1.5.9 RC 12 INSTEAD OF 4. IC35788 - TSM ODBC DRIVER'S IMPLEMATION OF SQLSTATISTICS<> IS IMPLEMENTED INCORRECTLY FOR THE CRYSTAL RPTS 9. IC35804 - INTERMITTENT CORRUPTION OF ADMIN COMMANDS ISSUED THROUGH TSM ADMIN COMMAND LINE. IC35812 - CHANGED WRONG SAMPLE SYNTAX FOR SCHEDlog OPTION IN DSMCUTIL.TXT TO CORRECT SYNTAX. IC35902 - RESTORE OF EMPTY DIRECTORY CAUSES TSM CLIENT 5.1.5.0 TO RETURN "NO OBJECTS ON SERVER MATCH QUERY" ERROR. IC35933 - MULTIPLE SESSION RESTORE CAN HANG IF ONE SESSION EXITS ABNORMALLY WHEN USING GUI OR WEB GUI. IC35940 - THE VALUE 'CLUSTERDB' FOR CLIENT OPTION EXCLUDE.SYSTEMOBJECT DOES NOT WORK. IC35943 - THE WINDOWS EXCLUDES/INCLUDES IN THE DSM.SMP FILE NEEDS TO BE CHANGED. IC35964 - WHEN UPGRADING FORM TSM CLIENT VERSION 5.1.5.8 TO VERSION 5.1.5.15, MAINTENANCE DIALGO IS DISPLAYED PROMPTING THE USER TO MODIFY, REPAIR, OR REMOVE THE EXISTING TSM CLIENT. IC35997 - DURING THE RESTORE OF A BACKUPSET THE TSM CLIENT COREDUMPS. IC36003 - TSM W2K 5.1.5.X CLIENT: MISSING DSCDEU.TXT IN API DIRECTORY LEADS TO ANS0101E when installing the TSM scheduler IC36107 - "DRIVER WAS UNABLE TO ALLOCATE MEMORY REQUIRED TO SUPPORT EXECUTION" MSG IS RECEIVED FROM THE TSM ODBC DRIVER.