============================================================================== IBM Tivoli Storage Manager README Windows Backup-Archive Client Version 5 Release 3, Level 0 Licensed Materials - Property of IBM (C) Copyright IBM Corporation 1990, 2004. All rights reserved. Welcome to the IBM Tivoli Storage Manager Version 5.3 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 -------- See Late-Breaking News -- "What's new" for major revisions to log handling during startup. - Migration - If you do not follow the migration instructions properly, you might have two file spaces, such as Unicode and non-Unicode, with different file space identifiers (fsID) for the same client volume. In this case, the TSM client uses the non-Unicode file space as the default file space for backup and restore operations. - Open File Support (OFS) and Online Image Backup New defaults for cache locations are on the target instead of system drive (C:\ drive). See manual for further details. - Open File Support/Image upgrade issue - Due to a problem in the TSM BA Client version 5.2.0 installation program, upgrading the features "Open File Support" and/or "Image Backup" from TSM BA Client version 5.2.0 will not succeed. The only current workaround is to uninstall version 5.2.0 and install version 5.3.0 NOTE: This workaround only applies to those machines with the TSM Backup-Archive client version 5.2.0 installed with features "Open File Support" or "Image Backup" selected. These features are not included in a "typical" installation. To determine if these features have been previously installed at 5.2.0, you can look at the "Custom Setup" panel (select "Custom" setup type) feature list. If the features "Open File Support" or "Image Backup" have an 'X' by their name, they have not been previously installed. - 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.3 client may not be able to correctly restore backup versions of Mac files that were created with client versions below 4.2. It is strongly recommended that you rename your existing NTFS filespaces that house Mac files before upgrading to the TSM 5.3 client. If you have already upgraded to the 5.3 client without renaming the existing NTFS filespaces that house Mac files, then it is strongly recommended that you perform a selective (or full) backup against your NTFS Mac volumes. - Windows Image Backup not working with shared memory protocol. To use the SHAREDMEM (shared memory) communications method, the TSM server and client must be executed by the same user. If the server and client are started by different accounts, then they will not be able to establish a connection with each other. Client Components ----------------- [NONE] Software Requirements --------------------- - What client to install: +---------------------------+--------------------+--------------------+ | |Windows 32-bit |Windows 64-bit | | |run: |run: | | |\tsmcli\win32\client|\tsmcli\win64\client| | Windows Version: |\disk1\setup.exe |disk1\setup.exe | +---------------------------+--------------------+--------------------+ |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, Storage| | | |Server | X | | +---------------------------+--------------------+--------------------+ |2003 64-bit Enterprise | | | |Server, Datacenter | | X | +---------------------------+--------------------+--------------------+ +--------------------------+------+-------|-------+--------+--------+ | | 2000 | XP | XP | 2003 | 2003 | | | |32-bit |64-bit | 32-bit | 64-bit | +--------------------------+------+-------+-------+--------+--------+ | Journal Based Backup | yes | yes | no | yes | no | +--------------------------+------+-------+-------+--------+--------+ | On-line image backup | yes | yes | no | yes | no | | using snapshot | | | | | | +--------------------------+------+-------+-------+--------+--------+ | Off-line image backup | yes | yes | yes | yes | yes | +--------------------------+------+-------+-------+--------+--------+ | System object support | yes | yes | yes | n/a | n/a | | via legacy APIs | | | | | | +--------------------------+------+-------+-------+--------+--------+ | System State and System | n/a | n/a | n/a | yes * | yes * | | Service support via | | | | | | | Volume Shadowcopy | | | | | | | Services (VSS) | | | | | | +--------------------------+------+-------+-------+--------+--------+ | LAN-free operations | yes | yes | yes | yes | yes | +--------------------------+------+-------+-------+--------+--------+ | Server-free operations | yes | no | no | no | no | +--------------------------+------+-------+-------+--------+--------+ | Automated System | n/a | yes | yes | yes | yes | | Recovery (ASR) | | | | | | +--------------------------+------+-------+-------+--------+--------+ | Open File Support | yes | yes | no | no | no | +--------------------------+------+-------+-------+--------+--------+ * - the TSM client must be connected to a Tivoli Storage Manager version 5.2.0 or higher server. - HTML Help Viewer - 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 2000 Professional SP2 and up - Windows 2000 Server SP2 and up - Windows 2000 Advanced Server SP2 and up - Windows 2000 Datacenter Server SP2 and up - Windows XP Professional (32-bit) SP 1 and up - Windows 2003 Server - Windows 2003 Web Server - Windows 2003 Enterprise Server (32-bit) - Windows 2003 Datacenter (32-bit) - Windows 2003 Storage Server - In addition to the browsers listed in the client manual, Mozilla Firefox 1.0 is also supported. 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) 200 MB 10 MB 210 MB Full install (one language) 55 MB 10 MB 65 MB Complete (Typical) install 27 MB 10 MB 37 MB Application Program Interface (API) ----------------------------------- - See readme file API.TXT. Migration Information --------------------- - Migration information in the documentation Please see the TSM book "Tivoli Storage Manager for (PLATFORM) Backup-Archive Client Installation and User's Guide" Chapter 1 for migration information. The client books are located on the Publications CD and in the client packages. They are also available on the World Wide Web, as described in the 4. Getting Help, Product Documentation section below. - Migration compatibility As part of a migration plan from Tivoli Storage Manager V5.2 to Tivoli Storage Manager V5.3, Tivoli Storage Manager clients and servers may be upgraded at different times. In general, V5.2 clients can perform backup, archive, migrate, restore, retrieve, and recall functions to a V5.3 server. V5.3 clients can perform backup, archive, migrate, restore, retrieve, and recall functions to a V5.2 server. See Chapter 1 of the client books for more detailed compatibility information. - about DOMAIN option By definition, the DOMAIN option specifies the file systems that a user wants to include for incremental backup. Previous TSM clients incorrectly allowed directories in the domain option, and that caused problems during domain backup. Now the client checks whether a domain name is valid. If the domain name is not a file system, the TSM client will issue the message: "ANS1071E Invalid domain name entered: xxx". - 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 to 64-bit Windows, it is recommended that you avoid backing up the 64-bit system object or system state data into the same file spaces containing the 32-bit system object or system state data. This is because you would not want to inadvertently restore the 32-bit data which is incompatible with 64-bit Windows. To avoid commingling the data, you can do either of the following before migrating to 64-bit Windows: - Ask your TSM administrator to rename the existing file spaces. Once the migration is complete and you have backups of the 64-bit system object or system state data, your TSM administrator can delete the renamed file spaces. Since the 32-bit system object or system state data must not be restored to 64-bit Windows, there is little reason to retain the data. File spaces to rename include one or more of the following: SYSTEM OBJECT SYSTEM STATE SYSTEM SERVICES ASR - Ask your TSM administrator to delete the existing file spaces (listed above) for your node. Web Backup Archive Client ------------------------- [NONE] ------------------------ 2. Installing the Client ------------------------ Installing the Client --------------------- NOTE: It is recommended that all instances of the TSM client (services, interactive clients, etc.) be stopped before performing the install. If any instance of the client is running during the install, you will need to reboot the system after the install. - If you are installing from a file downloaded from the anonymous FTP server, then the installation involves two phases: 1. Extract the install image to your hard drive. 2. Install the client from the install image. During the first phase (extract the install image), you will be able to choose the directory to which the install image is extracted. The default is "c:\tsm_images". It is recommended that the install image be extracted to an empty directory. The extraction requires about 80 MB of disk space. After the second phase (install the client) is complete, the install image will remain on your hard drive. You can delete the install image if you want. - Installation of TSM requires MSI version 2.0 or higher. Windows 2000 SP 3 and higher, Windows XP, and Windows 2003 already include MSI 2.0. Windows 2000 SP 2 or lower might require an upgrade to MSI 2.0. If you are running Windows 2000 SP 2 or lower, you can determine the version of MSI on your system as follows: 1. Use Windows Explorer to navigate to the \WINNT\system32 directory. 2. Locate file msiexec.exe. 3. Right click on the file, then click "Properties" in the pop-up menu. 4. Click on the "Version" tab. - When installing TSM from the 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 client 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 for reboot at installation conclusion. The 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: - If you want to install a predefined DSM.OPT file, place a copy of the DSM.OPT file in the ...\config directory located within the install image, i.e.: c:\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 already 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 are upgrading from a previous version of TSM and there are TSM services running (Client Acceptor, Scheduler, etc) the following error might be encountered during install: Error 1303. The installer has insufficient privileges to access this directory: (Install Drive):\Program Files\Tivoli\TSM\baclient\plugins. The installation cannot continue. Log on as an administrator or contact your system administrator. Once this error occurs, you must quit the install. After quitting the install, the previous version is no longer installed. Stop the running TSM service(s) and retry the installation. - Online Image Support and Open File Support Removal on upgrade. If you currently have Online Images Support and Open File support installed and wish to remove either or both when upgrading to the latest TSM Client, you will need to go to the "Utilities -> Setup Wizard" and remove them using the "Help me configure...." options. - If you receive a message during setup indicating that you do not have enough free space to install on a drive that is known to have sufficient free space, you might be able to proceed by updating an entry in the setup.ini file that is included with the install package. If your package is on CD, you will need 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, open it up in your favorite text editor and change the line: DiskSpace=8000 ;DiskSpace requirement in KB to DiskSpace=0000 ;DiskSpace requirement in KB - 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\client" sub-directory of the CD-ROM, type "setup", and follow the directions in the dialog. Setup ----- - The Backup-Archive GUI will detect whether a TSM options file exists. If the options file can not be found (for example, if you are a first-time user), the client will launch a configuration wizard to assist you in configuring an options file. For more information on configuring an options file, refer to the "IBM Tivoli Storage Manager for Windows Backup-Archive Clients Installation and User's Guide" for further information. Uninstalling the Client ----------------------- - IMPORTANT: It is recommended that all TSM related services and interactive clients be stopped, and that TSM services be removed BEFORE uninstalling client. Otherwise uninstalling the client will result in the following: - A dialog box asking the user for a reboot. - The TSM services will be stopped, but not removed from Windows. Thus they will still appear in the Services applet, but will be unavailable for use. To remove TSM services, use the TSM GUI and select the "Utilities/Setup Wizard" menu item. You can also use the dsmcutil.exe command line utility to remove TSM services before uninstalling the client. - Open the Control Panel and double click on the "Add/Remove Programs" icon. In the "Add/Remove Programs" "Properties" window, in the "Install/ Uninstall" tabbed pane, highlight the "Tivoli Storage Manager Client" entry in the list box. Click on the "Add/Remove" button, then follow the dialog instructions. --------------------- 3. Late-Breaking News --------------------- What's New ---------- - What's new in the IBM Tivoli Storage Manager Version 5.3.0 Clients: - Initialization of the client and its various components has been significantly revised. In particular, if you are using scripts to accomplish certain tasks, you will notice: 1. The client application (dsmc, dsmadmc) will not run without a writable error log. If a log is not present, one will be opened under the uid of the user that invokes the application and with that user's default permissions. This may mean that another user may not have write permission and the client will not run. 2. There must always be an error log. If it is created new for each run and there are no errors, it will be empty at process termination. 3. If the error log exists and is writable by the invoking user, it will be preserved along with all permissions and ACLs if they exist. It is strongly recommended that you create any required logs in a directory and with proper permissions to allow all users write access. - New links from the backup-archive client GUI to the TSM and Tivoli Home Pages - A file named client_message.chg containing a composite list of all new, changed, and deleted message numbers will be found in the installation directory. - New options, Errorlogmax and Schedlogmax, and DSM_LOG environment variable changes - Errorlogmax and Schedlogmax are new options for controlling log size. - DSM_LOG environment variable changes have been made to prevent security or data integrity problems. - AES 128-bit data encryption support was added for all clients except Netware, z/OS and OS/400. - Shared memory protocol support extended to Windows and Linux platforms - Journal based backup enhancements to allow multiple journal based backup sessions are now available. - Include-exclude enhancements - Preview function and ability to include or exclude files from the TSM Client GUI directory tree. - Enhancements to query schedule command in support of new schedule definition changes. - Ability to enable client tracing while client is running - Multiple nodes can backup, archive, restore and retrieve objects under a single node - Java GUI and Web client enhancements to allow file search and filter. - Support for deleting individual files from the TSM server - Open File Support (OFS) enhancements 1. Support for single drive environments added 2. Support for logging of messages to the Windows event log - Many option defaults have been optimized for today's environments - Tivoli Storage Manager backup-archive client for HP-UX Itanium 2 [this section intentionally left blank] - As of TSM client version 5.3, the SNAPSHOTCACHELocation can be located on the same drive that is being backed up with image backup or OFS, or archived with OFS. The default value for the SNAPSHOTCACHELocation option is now the same drive that is being backed up or archived. Note the following restrictions: - SNAPSHOTCACHELocation can not point to a remote drive - SNAPSHOTCACHELocation can not point to an RAW volume Documentation Updates --------------------- The TCPCADADDRESS option specifies a TCP/IP address for dsmcad. Normally, this option is not needed. Use this option only if your client node has more than one TCP/IP address or if TCP/IP is not the default communication method (see commmethod option). Supported Clients This option is valid for all clients. The Tivoli Storage Manager client API does not support this option. Options File (unix & mac) Place this option in the dsm.sys file within a server stanza. (windows & netware) Place this option in the dsm.opt file. Syntax >>-TCPCADAddress- cad_address---------------------------->< Parameters cad_address Specify a TCP/IP Internet domain name or a dotted address. Examples Options file: tcpcada dsmclnt.sanjose.ibm.com Command line: -tcpcadaddress=128.33.10.249 or -tcpcadaddress=khoyt.mycompany.mydomain.com  This option is valid only on the initial command line. It is not valid in interactive mode. - The CASESENSITIVEAWARE option is not documented in the client manual: The CASESENSITIVEAWARE option specifies whether the Windows Backup- Archive client should filter out file and directory objects which have names conflicting in case only, e.g., a set of objects called 'MyWork.xls', 'MYWORK.xls', and 'mywork.xls'. NTFS volumes are case sensitive and allow case sensitive file names to be stored. Although the Windows operating system is not case sensitive, applications such as Windows Services for UNIX (SFU) exploit POSIX and allow case sensitive file names. SFU is typically included with Windows operating systems such as Windows Powered OS and Windows Storage Server 2003. These operating systems are typically deployed on hardware (for example, NAS hardware) which is acting as a dedicated file server in a heterogeneous environment. If there are UNIX clients storing files on NTFS volumes in these Windows file server environments, it is highly recommended to use the CASESENSITIVEAWARE option. If this option is not used in these environments unpredictable results will occur during backup and archive operations if case sensitive file name conflicts are encountered. For homogeneous Windows file server environments the CASESENSITIVEAWARE option is not necessary. Because the Windows operating system is not case sensitive applications cannot distinguish between two objects named 'mywork.xls' and 'MyWork.xls'. For this reason, the Tivoli Storage Manager Windows Backup-Archive client cannot guarantee the restore integrity of such objects. When a name casing conflict arises, the Tivoli Storage Manager Backup-Archive client can only guarantee the restore integrity of the first file in an alphabetical sort. On an ASCII-based operating system such as Windows, this means that capital letters come first alphabetically before their lower-case counterparts, so 'MySwork.xls' would alphabetically precede 'mywork.xls'. In this example, if the CASESENSITIVEAWARE option is used, only 'MyWork.xls' would be processed. An error message will be issued for 'mywork.xls' and it will be skipped. If 'mywork.xls' is a directory, then the directory subtree 'mywork.xls' would be skipped. In all cases, messages will be written to both the local error log and to the Tivoli Storage Manager server console to indicate the exact file names of the objects being skipped. Syntax |- No -| >>-- CASESENSITIVEAware --|-------|---------------------------------->< |- Yes -| Parameters Yes Specifies that the Tivoli Storage Manager should attempt to identify object names which differ in casing only and filter out objects which have casing conflicts and cannot be guaranteed to be restored properly. No Specifies that the Tivoli Storage Manager should not attempt to identify object names which differ in casing only. This is the default. - a new option, LANFREETCPSERVERADDRESS, has been added to the product The LANFREETCPSERVERADDRESS option specifies the TCP/IP address for a Tivoli Storage Manager Storage Agent. Use this option when you specify LANFREECommmethod=TCPip for communication between the Tivoli Storage Manager client and Storage Agent. Overriding the default for this option is useful when configuring LANfree in an environment where the client and storage agent are running on different systems. You can obtain this Storage Agent address from your administrator. Supported Clients: This option is valid for all Windows clients, except the 64-bit Windows Server 2003. Options File: Place this option in the client options file (dsm.opt). Syntax: >>-LANFREETCPServeraddress- stagent_address---------------------->< Parameters: stagent_address - Specifies a 1 to 64 character TCP/IP address for a server. Specify a TCP/IP domain name or a dot address. Default value is 127.0.0.1 (localhost). Examples: Options file: LANFREETCPServeraddress stagent.bayamon.ibm.com LANFREETCPServeraddress 192.168.1.50 [ This section intentionally blank.] Known Problems and Limitations ------------------------------ - Interrupt with CTRL-C During a backup or archive operation, CTRL-C may cause the client to coredump or unexpected behaviour. Do not use CTRL-C to abort a backup/archive operation, instead use the 'Q' key to quit. - Search/Filter (Web/Java GUI) The Search/Filter function may appear unresponsive when searching through very large filesystems. This is caused by JVM running out of memory. You should see a "java.lang.OutOfMemoryError" in the Java console. Data Protection for Lotus Domino and Data Protection for WAS objects are not supported. - Disable browser's proxy server if Web Client produces Security Exception 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 "IBM Tivoli Storage Manager for : Backup-Archive Clients Installation and User's Guide" for more information. - Web Client concurrent restore and tree expansion issues Running more than one restore or retrieve operation at the same time when using the Web Client may cause the browser to hang when destination or message windows from the different restore/retrieve processes appear on the screen at the same time. If you observe such behavior, wait until one restore/retrieve operation is finished before starting another. 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. - Fonts required to display non-English characters in directory or file names with the Web Client are as follows: - 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 installed. This font is available with MS Word 2002 and MS Office XP. See Microsoft's KB article 287247 for installation instructions. If you require this font, contact your Microsoft representative. - ERRORLOGMAX and SCHEDLOGMAX behavior in out-of-space conditions: - If the specified maximum error log file size is greater than the available free space on the specified file system and the log is being transitioned from a non-wrapped log to a wrapped log, the following error message will be issued: ANS1521E Failure writing to a Tivoli Storage Manager log or log-related file: dsmerlog.pru, errno = 28, There is not enough space in the file system" This is correct behavior. However, the log header record may be incomplete or there may be no "END OF DATA" text marker at the end of the error log. After space has been made available, the TSM client will subsequently treat the log as unwrapped because a valid header record is not found. A new log will be created and this partial log will be written to the prune file. - If there is insufficient space in the file system to append an entry to the log, the TSM client will continue running, but the error message will not be logged. - If client encryption is being used and you choose to abort a command line backup or archive operation when prompted for an encryption key, the entire operation will immediately end with return code (RC) 12, even if there are other files eligible for backup that do not require encryption. - LANFree Known Problems and Limitations: - 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. - On Solaris, the only supported LANFREECommmethod is TCPip (Loopback). - No Query Restore (NQR) LANFree of a small number of files/directories from a filespace 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 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 the storage agent. - 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. - The node setting for MAXNUMMP is not honored properly when performing a multi-session No Query Restore over LANFREE. The value must be set one higher than expected in order to achieve the desired number of simultaneous mount points. Restore of same data via the LAN produces the expected behavior. The following table illustrates the problem with respect to restoring data which is stored on three different tape volumes: MAXNUMMP | LANFREE mounts | LAN mounts ------------------------------------------- 2 | 1 | 2 3 | 2 | 3 4 | 3 | 3 - Windows Server 2003 - backup/restore system objects The DHCP service will fail to start if restoring the inactive version of this system object without restoring the inactive version of the system state. Ensure the corresponding inactive version of the system state is also restored. - VSS Native GUI/Web GUI When multiple inactive System State objects are chosen, only the first one queued by the client will be restored. All other requests to restore other versions of System State objects will be ignored. When restoring inactive System State objects, please only select one version to ensure that the desired version is restored. - The client manual documents -CON as being the minimum abbreviation for the -CONSOLE option (used with QUERY SYSTEMINFO). However, the client recognizes -CONS as the minimum abbreviation. The client will be corrected in a future release to recognize -CON as the minimum abbreviation. - 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-compatible 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 your 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. - Restoring from a backupset from a 3570 tape library attached to the client system is not supported. - 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 installing TSM Scheduler Service using the Setup Wizard or dsmcutil while the TSM server is down or unreachable, the node password will not get stored on the client machine. As a result, the scheduler service may not be able to authenticate to the server when the server becomes available. To fix this, one must manually run TSM client (CLC or GUI) again and enter the correct password when prompted. The above problem might take place when setting up a scheduler running through a firewall using the server-initiated sessions. If this is the case, start the scheduler from the command line (dsmc schedule) and enter the node's password when prompted. After the password is updated, stop the command line scheduler (press the 'q' key twice), then restart the scheduler service. - MAKE SURE BACKUP ACCOUNT HAS APPROPRIATE RIGHTS TO DRIVES When DOMAIN ALL-LOCAL is used and the account used to perform the backup does not have the necessary rights to the root of a drive, that drive will be skipped without warning. That is, the incremental backup will appear to have completed successfully even though an entire file system was skipped. It is therefore important to ensure that the account used to perform the backup have the necessary rights to the root of the drives you wish to back up. When the individual drives are listed in the DOMAIN statement, then an error message will be logged indicating that the drive was not backed up. This problem is described in APAR IC35953. It is our current intent to address this problem in a future release. - WINDOWS XP AUTOMATED SYSTEM RECOVERY (ASR) ASR recovery restores the system to the point of latest backup. There is no explicit support for point in time or inactive system state recovery. Point in time recovery could be accomplished by generating a backupset at the desired operating system state for later use. In rare occcurrences, the TSM ASR restore process proceeds before the TSM Client installation has completed. This issue has only exhibited itself on Windows 2003 systems using a minimal hardware configuration. The following work-around can be used to complete the process: 1. On the ASR floppy disk, uncomment the "pause" command after the waitforevent command in the tsmasr.cmd file: Change statement "REM pause" to "pause" 2. Save the changes to the floppy. 3. Restart the ASR restore procedure using the modified floppy. 4. When the pause statement is reached, the console will display "Press any key to continue...", wait 3-5 minutes for the installation of the client to finish. Alternatively, you can use the second command-line window to monitor the creation of the %SystemRoot%\temp\~tsmasr\baclient folder. 6. Press any key to continue the ASR restore procedures. - WINDOWS 2000 NAMED STREAMS - 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 as of TSM V5.1.5. Backups of these objects taken by a TSM V5.1.5 (or higher) client cannot be restored by a previous version of the client. Backups taken by previous versions of the client can still be restored by TSM V.1.5 (or higher) clients. - 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. Consult with Microsoft for more information about using this utility. - Windows Server 2003 backup/restore system objects - Restore DHCP system object The DHCP service will fail to start if restoring the inactive version of this system object without restoring the inactive version of the system state. Ensure the corresponding inactive version of the system state is also restored. - VSS Native GUI/Web GUI: When multiple inactive System State objects are chosen, only the first one queued by the client will be restored. All other requests to restore other versions of System State objects will be ignored. When restoring inactive System State objects, select only one version to ensure that the desired version is restored. - JOURNAL BASED BACKUP: - The new journal database implemented in this release requires performing a full (non-journal) incremental backup in order to create a new valid journal database. Note that older journal databases are left intact and may be deleted. - Deleting files from a Windows Command Prompt might result in files not being expired during journal based backup. In some cases, the Windows command interpreter uses 8.3 file names instead of long file names during delete operations. The TSM backup- archive client tries to resolve these 8.3 names to the original names backed up on the TSM server, which might require forcing a normal (non- journal based) incremental backup of the parent directory of the deleted file to ensure that it is properly expired. Propagation of this problem can be avoided by turning off NTFS 8.3 file name creation, after which 8.3 file names will not be generated for new long file names. To disable 8.3 file name creation, perform the following steps: CAUTION: The following steps use the Windows regedit utility to modify the system registry. Errors in editing the registry can result in an unstable, and possibly unbootable system. Contact your system admini- strator if you are not comfortable editing the registry. 1. Start regedit.exe and locate the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem 2. Examine the "NtfsDisable8dot3NameCreation" entry. A value of 0 indicates that 8.3 name creation is enabled. A value of 1 indicates that 8.3 name creation is disabled. If the value is already 1, then close regedit since you do not need to do anything further. 3. Double-click the "NtfsDisable8dot3NameCreation" entry. This will bring up a dialog that allows you to change its value. Change the value to 1, then click "OK" to close the dialog. Close regedit. 4. Reboot the system. Note that the change does not take effect until you reboot. Notes: - 16-bit Windows and DOS applications will not be able to access files with long names that are created after 8.3 file name generation is disabled. - This change affects all NTFS partitions. It does not apply to FAT or FAT32 partitions. - Moving a directory from Windows Explorer using cut and paste may result in the old and new directories not being properly backed up or expired during a journal based backup under certain circumstances. A directory move operation may be done from a command prompt with the move or rename command, or from Windows Explorer using drag and drop or cut and paste. The TSM Journal daemon assumes that a "move directory" operation has occurred when a delete directory operation is followed immediately by a create directory operation. If a delete directory operation is not followed by a create directory operation (for the same directory), the delete operation is assumed to be for a single directory object and not as the result of a move operation. For a move operation, journal based backup must force a normal incremental backup of both directories in order to ensure that all files in the deleted directory are expired correctly, and that all files in the destination directory are backed up correctly. For a single directory delete operation, only the directory itself is expired on the TSM server. Since it is possible to perform other operations between the time a Windows Explorer directory cut operation is performed and when the follow-on paste operation is perfomed, the TSM Journal daemon may not correctly identify the operation as a directory "move". - 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. - Known problems with anti-virus software Some anti-virus software may incorrectly generate change notifications to the TSM Journal Service. This might cause files that don't appear to have changed to be incorrectly backed up when using Journal Based Backup. Development is currently working with virus protection vendors to fix these problems. If you see these problems with virus protection vendors not listed below, report the problem to your virus protection software vendor or IBM support. Symantec Norton Anti-Virus Corporate Edition (Nav) ================================================== Symantec has implemented an interim fix which eliminates most incorrect change notifications generated during Nav scan processing. This interim fix was incorporated into Nav CE version 7.51 and must be obtained from Symantec technical support. The complete fix is included in Norton Anti-Virus Corporate Edition 8.0. Customers should refer to Knowledge Base article 4011082926 and the CRT STS number (Defect 362082, Incident 421919). Note that the initial interim fix still 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 attribute bitmask changes. Two changes must be made to enable this fix: - Set the following DWORD registry value: HKLM\Software\Intel\LANDesk\VirusProtect6\CurrentVersion NoFileMod = 1 This setting prevents Nav from caching and restoring timestamps and security information during scan processing. - Include the following in the Based Backup .ini file (tsmjbbd.ini): [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 or attribute bitmask changes. - Restoring data with multiple TSM encryption keys - When restoring a group of files that have been encrypted by TSM and you need to input more then one encrypt key for the group, files might not be restored. The error log will show an error in 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. - After migrating from a non-Unicode TSM Client to a Unicode-enabled TSM Client (e.g., from TSM 4.1.2 to TSM 5.3.0), then if you restore files or folders containing double-byte characters mixed with single-byte characters, the names will be restored in mixed casing. This is only a display issue. - 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. Thus the 32-bit API will not be able to access the password entries generated by the 64-bit API. For 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. To alleviate password synchronization issues between 32-bit and 64-bit Windows clients, use a separate node name for each client. - WINDOWS IMAGE BACKUP AND RESTORE - 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: and its log files are on drive G:, then when the TSM client restores drive F: the data files might not be in sync with whatever changes might have gone into the log files on drive G: since the image backup of drive F:. - If an unrecoverable read failure occurs during image backup, the following message is displayed: ANS0322E (RC4161) no text available for this return code. The return code 4161 means device read error. - 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. - On Windows XP Only - When restoring an NTFS image over a FAT volume or vice versa Windows Explorer, in some cases, will not reflect the change in new volume type (NTFS or FAT) right away when viewing the volume properties from Windows Explorer. After rebooting Windows Explorer will show the correct volume type. Note that you can see the changed type right away from the Computer Management (MMC) -> Disk Management console. - Preference Editor Include-Exclude limitation (Native GUI) - In the "Include-Exclude" tab of the preference editor, file exclusion is only supported for "Incremental" backup types. File exclusion is not supported for NAS or Image. It will add the option to the options file, but the option will not be honored. - The 'dsmc help' command does not provide information for the Data Protection for Lotus Domino Plugin option, DOMNODE. Please refer to the Data Protection for Lotus Domino User's Guide for a description. - Open File Support for Windows 2000 and Windows XP Terminal Services ================= Open File Support is not supported via a Terminal Services session. This is due to a limitation within Terminal Services where a new volume is not visible to the current session unless the user logs off and logs back in again. The Web GUI B/A Client can be used for remote OFS operations. LVSA and Setup Wizard ===================== If the temporary installation directory (i.e., \tsm_images) is removed or there is no installation media present, the Setup Wizard will fail operations which require files from the installation media or temporary installation directory with the following error message: ANS3010E The Logical Volume Snapshot Agent wizard operation failed. To bypass this error please point the Setup Wizard to the correct temporary installation directory or the installation media. - If the client is installed in a path that contains DBCS characters, the QUERY SYSTEMINFO command does not correctly display the install path in the REGISTRY section of the output. --------------- 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 --------------------- - IBM Tivoli Storage Manager publications are available in softcopy Adobe Acrobat Reader format (.pdf) and HTML (.htm) format on the IBM 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.htl - 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 (fix pack) 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 ------------- Missing from books: - Application System/400 - Client Access/400 - i5/OS - Operating System/400 - Tivoli is a trademark of Tivoli Systems Inc. in the United States, or other countries, or both. Currently in books: AIX AS/400 DB2 FlashCopy IBM IBMLink iSeries Lotus Lotus Approach Magstar OS/390 OS/400 PowerPC pSeries RACF Redbooks RISC System/6000 RS/6000 Scalable POWERparallel Systems SP2 S/390 System/390 Tivoli Tivoli Enterprise Console TME TotalStorage VisualAge WebSphere xSeries z/OS zSeries UNIX is a registered trademark of The Open Group in the United States and other countries. Microsoft, Windows, Windows 2000, Windows XP, and Windows Server 2003, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Intel and Pentium are trademarks of Intel 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. Unicode is a trademark of Unicode, Inc. Linux is a trademark of Linus Torvalds in the United States, 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 3, Level 0.0 ----------------------------------------------- The client APARs fixed in V5.3.0 can be found on the Tivoli Storage Manager technical support webpage (see Getting Help for URL), under Other Resources, Version Release Information, TSM 5.3, Show V5.3 Fixed Client APARs. They can also be found searching the Technotes (FAQs) on the main TSM support webpage.