============================================================================== IBM Tivoli Storage Manager README Windows Backup-Archive Client Version 5 Release 2, Level 2 PTF IP22739 Licensed Materials - Property of IBM (C) Copyright IBM Corporation 1990, 2003. All rights reserved. Welcome to the IBM Tivoli Storage Manager Version 5.2 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 -------- Client Components ----------------- - The following components are included with the TSM Version 5.2.2 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. Refer to the README.ODBC.TXT file for installation instructions. This file is available in the Tivoli Storage Manager ODBC Driver install package. 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 | 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 | +--------------------------+------+-------+-------+--------+--------+ - 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 XP Professional (64-bit) - Windows 2003 Enterprise Server (64-bit) - Windows 2003 Datacenter (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 - Netscape Navigator 4.7 with Java Runtime Environment(JRE) 1.3.1 or higher - 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. Hardware Requirements --------------------- [NONE] Application Program Interface (API) ----------------------------------- [NONE] 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 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 and Mac) - Web Client The client books are located on the Publications CD and in the client packages. They are also available on the World Wide Web at: http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.htm l 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". - Migration compatibility As part of a migration plan from Tivoli Storage Manager V5.1 to Tivoli Storage Manager V5.2, Tivoli Storage Manager clients and servers may be upgraded at different times. V5.1 clients can perform backup, archive, migrate, restore, retrieve, and recall functions to a V5.2 server. V5.2 clients can perform backup, archive, migrate, restore, retrieve, and recall functions to a V5.1 server. See Chapter 1 of the client books for more detailed compatibility information. Web Backup Archive Client ------------------------- [NONE] ------------------------ 2. Installing the Client ------------------------ Installing the Client --------------------- NOTE: It is recommended that all TSM services be stopped when upgrading The TSM Client. - 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 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 are upgrading from a previous version of TSM to version 5.2.2 and there are TSM services running (Client Acceptor, Scheduler, etc) the following error may 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, the installation must be quit. After quitting the previous version is no longer installed. Stop the running TSM service(s) and retry the 5.2.0 installation. - 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 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\win64\client" sub-directory of the CD-ROM, type "setup", and follow the directions in the dialog. - Current Installation limitations: - The ability to install a predefined (custom) DSM.OPT file is not yet available. - These capabilities will be provided in a future TSM Client package. Setup ----- - If you are a first time user the Backup Archive GUI or the Backup Client shortcuts will detect if there is not an options file there and launch a configuration Wizard to assist you. For more information please see the "IBM Tivoli Storage Manager for Windows Backup-Archive Clients Installation and User’s Guide" book in the Online Information - Books folder. Uninstalling the Client ----------------------- [NONE] --------------------- 3. Late-Breaking News --------------------- What's New ---------- - What's new in the IBM Tivoli Storage Manager Version 5.2.2 Clients: - AIX GPFS 2.2 HSM partial-file recall - AIX GPFS 2.2 LAN-free data movement for HSM migrate and recall - Backup-Archive command-line client operand limit extension - Data protection retention for archive objects through API applications - Deletion hold/release through API applications - Event-based retention policy through API applications - HP-UX HSM support for HP-UX 11i and VERITAS File System 3.5 - HSM JAVA GUI (unsupported preview) - IBM TotalStorage SAN File System support - Language support expanded to include Russian, Hungarian, Czech, and Polish - Linux on Intel x86 HSM support for GPFS 2.2 file system - Linux on Intel Itanium Backup-Archive client - Macintosh OS X boot-time scheduler support - Macintosh OS X command-line Administrative client interface - Macintosh OS X command-line Backup-Archive client interface - Macintosh OS X support for non-administrator users on Mac OS 10.2 and Mac OS 10.3 only. - Mozilla 1.4 browser support on AIX platforms - Multi-session backup enhancements - NetWare 6.5 Backup-Archive client support - Symbolic link exclusion support - VERITAS Cluster Server support for Windows - VERITAS File System support for AIX 5.2 - What's new in the IBM Tivoli Storage Manager Version 5.2.0 Clients: - AIX support for VxFS file systems and Veritas Volume Manager - AUTOMOUNT support for Linux - federated file backup - firewall support for scheduled client operations - GPFS HSM support for pSeries in AIX HACMP/ES cluster - Java GUI for UNIX Backup-Archive clients - HSM LAN-free toleration - HSM non-root user support for HSM clients - Language pack support for Windows Backup-Archive clients - Language support improved for HP-UX, Solaris, and Linux/390 clients - Macintosh OS X Unicode support - NDMP file-level restore - NDS backup automation for NetWare - QUERY FILESPACE enhancement - QUERY IMAGE enhancement - QUERY INCLEXCL enhancement - QUERY OPTIONS - QUERY SYSTEMINFO - Snapshot support for external snapshot mechanisms - Solaris 9 Backup-Archive client and 64-bit HSM client - Sparse file handling improvements for UNIX Backup-Archive clients - Streaming mode for HSM on file recall - SuSE Linux Version8 Backup-Archive client for pSeries and iSeries hardware - TRACESEGSIZE option to split trace files - Web client functional enhancments - Web client sticky apps support - Websphere 5.0 support - Windows First failure data capture for program exceptions - Windows Server 2003 Backup-Archive and API client - Windows Automated System Recovery (ASR) for XP and Windows Server 2003 - Windows Server 2003 support for System State using VSS - Windows on-line image backup for XP - Windows Open File Support for Windows 2000 / XP - Windows RESETARCHIVEATTRIBUTE option - Open File Support (OFS) The IBM Tivoli Storage Manager Client for Windows 2000 and Windows XP now support the backup and archive or files that are in-use or locked at the time of the backup or archive operation. OFS uses the Logical Snapshot Volume Agent technology first introduced in TSM 5.1.0 for On-line Image Backup. INSTALLING AND ENABLING OPEN FILE SUPPORT Method 1 ======== OFS support is not enabled by default. It must be selected at install-time via the Install Shield program by selecting the 'Custom' setup type and then marking the 'Open File Support' feature for installation. Method 2 ======== Once the client is installed via a 'Typical' installation or a 'Custom' installation that did not install the 'Open File Support' feature you can use the Setup Wizard within the ITSM Backup/Archive Client GUI to install and enable 'Open File Support'. ***Regardless of which method is used the machine will require a reboot after installing, updating or removing OFS support from your machine*** USING OPEN FILE SUPPORT Once Open File Support is enabled it is used on all the volumes/files that are candidates for backup or archive. You can customize which volumes/files use Open File Support by using the new option INCLUDE.FS in your dsm.opt file or from the a client option set. Example: * you can use dynamic to tell the client to not use open file support INCLUDE.FS C: fileleveltype=dynamic * once OFS is enabled fileleveltype defaults to snapshot. you can * use the INCLUDE.FS option to customize any of the snapshot options * per volume (SNAPSHOTCACHELocation, SNAPSHOTCACHESize, SNAPSHOTFSIDLEWait, * SNAPSHOTFSIDLERetries, PRESNAPSHOTCMD and POSTSNAPSHOTCMD). INCLUDE.FS E: fileleveltype=snapshot SNAPSHOTCACHELocation=c:\ For complete information on OFS options please refer to the ITSM 5.2.0 Backup and Archive Client for Windows: Installation and User's Guide. - SNAPSHOTFSIDLEWait Option Changes for TSM Client for Windows 5.2.2 This option change applies to both Open File Support and On-line Image Backup operations. The SNAPSHOTFSIDLEWait option now has the following syntax: SNAPSHOTFSIDLEWait Max[Unit][,Min[Unit]] The Max value is the maximum amount of time to wait between writes before taking the snapshot of the selected volume. The Min value is the minimum amount of time to wait before taking the snapshot of the selected volume. This option change will allow the LVSA to try the higher values first and during each retry decrease the value until the minimum is reached. This will allow the LVSA to be more flexible and successfully take a snapshot of a volume during periods of high I/O write activity. Example: SNAPSHOTFSIDLEWait 6s,1s SNAPSHOTFSIDLERetries 5 1st try 6 seconds 1st retry 5 seconds (checks for 5 seconds of inactivity since last write) 2nd retry 4 seconds (checks for 4 seconds of inactivity since last write) 3rd retry 3 seconds (checks for 3 seconds of inactivity since last write) 4th retry 2 seconds (checks for 2 seconds of inactivity since last write) 5th retry 1 seconds (checks for 1 second of inactivity since last write) Notes: - a max or min of 0 can be specified but it is not recommended by IBM - specifying a min value is optional (thus pre 5.2.2 clients will not need to change their current SNAPSHOTFSIDLEWait setting) For full details on this option change please refer to the TSM Client for Windows User's Guide (under the SNAPSHOTFSIDLEWait option). Documentation Updates --------------------- - A new option, Clusterdisksonly, has been added to the product. The clusterdisksonly option specifies whether the Tivoli Storage Manager Backup-Archive client will allow the backup of only clustered disks when running in a Microsoft Cluster Server (MSCS) or VERITAS Cluster Server (VCS) environment and using the clusternode=yes processing option. The Tivoli Storage Manager Backup-Archive client previously only allowed backup of clustered drives which were associated with a drive letter. It is becoming more prevalent to define clustered drives as volume mount points. The Windows 2003 Server and products such as IBM Tivoli SANergy allow the user to surpass the 26-drive-letter limitation by allowing volume mount points to be defined on a clustered server. Note that when the clusterdisksonly option is specified as yes, the Tivoli Storage Management Backup-Archive client will continue to segregate local drives from cluster drives when evaluating the ALL-LOCAL domain option. When the clusterdisksonly option is specified as no, the user will have to explicitly define the backup domains. Syntax |- Yes -| >>-- CLUSTERDISKSOnly --|-------|-------------------------------------->< |- No -| Parameters Yes Specifies that the Tivoli Storage Manager should only allow the processing of cluster drives which have a drive letter. This is the default. No Specifies that the Tivoli Storage Manager should allow the processing of any disk when the clusternode option is set to yes. Recommended usages The following are a list of scenarios of scenarios which describe recommended option settings based on the type of volumes which are being processed. Each example lists the optimal settings for the clusternode and clusterdisksonly options and includes a sample domain option setting and exclude option to demonstrate how to code these options so that they can be customized for the proper environment. Scenario 1: Backup a node which manages the local (non-clustered) drives and the system state information. This is the node that is basically dedicated to the restoration of the physical machine should there be a hardware failure. There are no clustered drives which appear as volume mount points (i.e., a product like IBM Tivoli SANergy is not being exploited). CLUSTERNODE NO (default) CLUSTERDISKSONLY YES (default) DOMAIN ALL-LOCAL (default) EXCLUDE c:\...\file.txt Scenario 2: Backup a node which manages the local (non-clustered) drives and the system state information in a clustered environment using volume mount points as cluster resources. This is the node that is basically dedicated to the restoration of the physical machine should there be a hardware failure. There are clustered drives which appear as volume mount points in this environment (e.g., IBM Tivoli SANergy, Windows 2003 server ...). In this environment the user must take care to remove any volume mount points from the incremental processing domain. For example, the user has a volume mount point on a clustered drive (x:\mnt) and a non-clustered drive (c:\mnt): CLUSTERNODE NO (default) CLUSTERDISKSONLY YES (default) DOMAIN ALL-LOCAL -c:\mnt -x:\mnt EXCLUDE c:\...\file.txt Scenario 3: Backup a node which manages the clustered drives within a cluster resource group. In this scenario, it is assumed that the node is responsible for backing up a cluster resource groups that has two drives, 'f:' and 'g:'. There are no clustered drives which appear as volume mount points (i.e., a product like IBM Tivoli SANergy is not being exploited). In this environment the user must take care to define the incremental processing domain as only the volumes within a cluster resource group (if there are multiple cluster resource groups it is recommended that a unique TSM node be assigned to manage each cluster resource group). CLUSTERNODE YES CLUSTERDISKSONLY YES (default) DOMAIN f: g: EXCLUDE f:\...\file.txt Scenario 4: Backup a node which manages the clustered drives within a cluster resource group using volume mount points as cluster resources. In this scenario, it is assumed that the node is responsible for backing up a cluster resource groups that has two drives, 'f:' and 'f:\mnt'. There are clustered drives which appear as volume mount points (e.g., IBM Tivoli SANergy, Windows 2003 server ...). In this environment the user must take care to define the incremental processing domain as only the volumes within a cluster resource group (if there are multiple cluster resource groups it is recommended that a unique TSM node be assigned to manage each cluster resource group). CLUSTERNODE YES CLUSTERDISKSONLY NO DOMAIN f: f:\mnt EXCLUDE f:\mnt\...\file.txt - A new option FRSPRIMARYRESTORE has been added to allow primary restoration of the SYSVOL if all replication partners have been lost, i.e., in a disaster recovery situation when all machines containing the SYSVOL are lost it is necessary to restore the first SYSVOL in this manner. This can be done by adding the option FRSPRIMARYRESTORE YES into the option file, dsm.opt. If you are restoring a single machine into an existing active directory tree, this option is not necessary. - In the client manual, Chapter 9 "Using processing options", section "Exclude options", subsection "Parameters", there is a line that reads as follows: The valid values for the exclude.systemobject option are ACTIVEDIRECTORY, CERTSERVERDB, CLUSTERDR, COMPLUSDB, EVENTLOG, FRS, REGISTRY, RSM, SYSFILES, SYSVOL, and WMI. The value "CLUSTERDR" is incorrect, and should be "CLUSTERDB". - A new option, Casesensitiveaware, has been added to the product. The casesensitiveaware option specifies whether the Windows Backup-Archive client archive 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. - The following items are available for the QUERY SYSTEMINFO command in addition to those items already documented in the client manual: FILESNOTTOBACKUP Enumeration of registry key HKEY_LOCAL_MACHINE\ SYSTEM\ CurrentControlSet\ BackupRestore\ FilesNotToBackup This key specifies those files that backup products should not back up. QUERY INCLEXCL will indicate that these files are excluded per the operating system. KEYSNOTTORESTORE Enumeration of registry key HKEY_LOCAL_MACHINE\ SYSTEM\ ControlSet001\ BackupRestore\ KeysNotToRestore This key specifies those registry keys that backup products should not restore. SFP Dumps the list of files protected by Windows System File Protection, and for each file, indicates whether that file exists. These are files that are backed up as part of the SYSFILES system object. SFP= Indicates whether the specified file, , is protected by Windows System File Protection. Example: SFP=C:\WINNT\SYSTEM32\MSVCRT.DLL SCHEDLOG Dumps the contents of the schedule log (usually dsmsched.log). It should be noted that the QUERY SYSTEMINFO information is primarily intended as an aid for IBM support to assist in diagnosing problems, although users familiar with the concepts addressed by this information may also find it useful. - About improper use of wildcards. Because a drive specification can consist of one letter only, you should not use more then one wildcard or a combination of a wildcard with a letter to designate a drive specification. So, the following patterns are not allowed and, once specified in the options file, will result in immediate termination of the client on its start and an error message in the error log: ?*:\test.txt *?:\...\pagefile.sys H*:\test.* *H:\test.txt myvolume*:\ myvolume?*:\ In the case of UNC names you should correctly specify a shared drive. So following the patterns are invalid: \\remote\*:\...\*.* \\remote\?:\...\*.* \\remote\*:\...\pagefile.sys Instead, you should write \\remote\*$\...\*.* \\remote\?$\...\*.* \\remote\*$\...\pagefile.sys - Online Image Backup for Windows 2000 and Windows XP The way to install and enable Online Image Backup for Windows has changed in 5.2.0. This support can now be installed via the Install Shield during install-time. Method 1 ======== Online Image Backup support is not enabled by default. It must be selected at install-time via the Install Shield program by selecting the 'Custom' setup type and then marking the 'Image Backup' feature for installation. Method 2 ======== Once the client is installed via a 'Typical' installation or a 'Custom' installation that did not install the 'Image Backup' feature you can use the Setup Wizard within the ITSM Backup/Archive Client GUI to install and enable Online Image Backup. ***Regardless of which method is used the machine will require a reboot after installing, updating or removing Online Image Backup support from your machine*** - Table 51. System services components and corresponding keywords New component WINS Data base, keyword WINSDB, was added to the table. - The restore backup set command was modified to support restoring of Windows Server 2003 system objects. To restore only the system state or system services from the backupset, use the new keywords "SYSTEMSTate" and "SYSTEMSErvices" instead of "SYSTEMObject". You cannot restore individual system objects from the backup set. Syntax >>-REStore BACKUPSET--+---------+--+- backupsetname-+-----------> '-options-' '- filename------' >--+- sourcefilespec----------------+---------------------------> +- {filespacename}sourcefilespec-+ +-SYSTEMObject-------------------+ +-SYSTEMSTate--------------------+ '-SYSTEMSErvices-----------------' >--+----------------------+------------------------------------>< '- destinationfilespec-' Known Problems and Limitations ------------------------------ - Web Client JRE 1.4 issue When using the Web Client with JRE 1.4 and above, these error message will be logged in the dsmerror.log on the machine where the TSM Client Acceptor resides when push buttons on the applet are pressed: Error -50 sending ht request Error writing to http socket ANS1005E TCP/IP read error on socket = X, errno = Y, reason : 'Connection reset by peer' or 'Connection aborted by host machine' ANS1006E TCP/IP write error on socket = X, errno = Y, reason : 'Connection reset by peer' or 'Connection aborted by host machine' This could potentially fill up your dsmerror.log with these messages. In order to prevent these messages from appearing in the error log, please disable caching in the JRE. This can be done through the "Java Plug-in Control Panel" under the "Cache" tab. Once this has been disabled, these error message should no longer appear. If you are using JRE 1.3.1_XX, this will not be a problem. If you are experiencing hangs with the web client using JRE 1.4 and above, disabling caching on the Java Plug-in will usually resolve this issue as well. - Node access list window (Web/Java GUI) When the change button is clicked in the Node Access List dialog on the Web Client and Java GUI, the currently selected rule's path will not be highlighted in the tree displayed in the Change Access Rule dialog. This will be fixed in a future release. - Access another node (Web/Java GUI) When accessing another node in the Web/Java GUI, the restore tree does not display images to which the other node has given you access. Use the access another node utility in the native GUI or the set access function in the command line client to restore images of another node to which you you have access. - 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 TSM B/A 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. - Canceling restore when using the Backup/Archive GUI, Web GUI, and Java GUI If the user cancels a restore by choosing cancel from the GUI or aborts the restore, there will not be a restartable session available at the server. - Changing the language of the Web Client on an AIX browser 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. - Web Client online help language issues 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 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. - 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. - Garbled characters in Administrative Client GUI due to locale 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 error message: can be displayed to the screen and to the dsmerror.log file for clustered drives if no DOMAIN statement (or DOMAIN ALL-LOCAL) is specified in the options file dsm.opt. This is an expected error condidition and can be ignored. - 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-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 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. - 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 bolded 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 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, please execute scheduler from the command line (dsmc schedule) and enter the node's password when prompted. After password is updated, the scheduler service needs to be restarted - 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. SNAPSHOTCACHELocation ===================== The SNAPSHOTCACHELocation can not be located on the same drive that is being backed up or archived via OFS. The SNAPSHOTCACHELocation can not be located on a remote drive. - Windows XP 64 bit TSM Backup Archive GUI On Windows XP 64 bit with SP1 applied, the TSM Backup Archive GUI (dsm.exe) will fail to launch, issuing a message "ordinal 6880 could not be located in dynamic link library mfc42u.dll". This is due to a problem with the Microsoft Foundation Class libraries shipped in SP1. Refer to Microsoft Knowledge Base article 814415 for details on this problem and instructions on how to obtain and install the fixed level of mfc42u.dll. This problem is not present in Windows 2003 Server 64 bit. - Windows Automated System Recovery Windows Automated System Recovery cannot be performed on 64 bit Windows due to an operating system problem in which ASR format of the system drive is attempted and fails in an infinite loop. There is no known workaround. - 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. --------------- 4. Getting Help --------------- Online Help ----------- - Context-sensitive help is not supported for Wizards. Help is only provided for the Help button. - The Windows Server 2003 operating system is referenced in the online help as "Windows .NET" or "Windows .NET Server 2003". 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.htm l 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.htm l - 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 ------------- - 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 2, Level 2.0 ----------------------------------------------- IC35332 - TSM WINDOWS B/A CLIENT ALLOWS BACKUP OF FILES UNDER THE \WINNT\SSVOL\SYSVOL\ JUNCTION. IC35822 - "INTERNAL SYSTEM ERROR" MESSAGE NEEDS MORE DETAIL ON ERROR WHEN TSM BACKUP OF A NETWORK DRIVE EXPERIENCES A NETWORK DISCONNECT. IC35895 - ROOT DIRECTORY OF A VOLUME NOT ALWAYS BACKED UP DURING FULL INCR BACKUPS EVEN IF COPY MODE ABSOLUTE SET ON TSM SERVER. IC36019 - TSM CLIENT COMMAND LINE "DSMC INCREMENTAL SYSTEMOBJECT" ATTEMPTS SYSTEM OBJECT BACKUP, EVEN THOUGH SYNTAX IS INCORRECT. IC36088 - THE OPTION "ALLOW SERVICE TO INTERACT WITH THE DESKTOP" SHOULD NOT BE TURNED ON BY DEFAULT WHEN CREATING A SCHEDULER SERVICE. IC36091 - WHEN FILESPACE NULL IS RETURNED FROM parseBackOperand IN IC36295 - TSM BACKUP OF AD SYSTEMOBJECT SHOWS PROPER SIZE, BUT QUERY OF THE AD SYSTEMOBJECT SHOWS IRREGULARLY LARGE VALUE INSTEAD. IC36454 - TSM CLIENT CRASHES DURING BACKUP. IC36467 - TSM CLIENT INCLUDE ANS1036S INVALID OPTION 'INCLUDE' FOUND IN OPTION FILE SHARE INVALID ENTRY : 'INCLUDE \\REMOTE\TEST$\*' IC36489 - USING THE TSM WINDOWS WIZARD, IF USER SELECTS BOTH WEB CLIENT AND SCHED SERVICE, THE CUSTOM LOG FILE OPTION DOES NOT WORK. IC36493 - BACKUP OF ACTIVE DIRECTORY CAUSES ANR0444W 'OUT OF SEQUENCE' VERB (GROUP HANDLER) IN SERVER ACTIVITY LOG. IC36543 - TSM CLIENT NQR (NO QUERY RESTORE) CAN TERMINATE IMPROPERLY IF THE RESTORE IS INTERRUPTED BY A DISK FULL/QUOTA CONDITION. IC36552 - RESTORE BASE DELTA FILES FAILED MSGANS1371E. IC36559 - DSM.SYS POSTSCHEDULE NOT CORRECTLY EXECUTED AFTER SCHEDULE WITH SERVER - POSTS OPTION. IC36567 - CLIENT "QUIET" OPTION, ANS1311E AND ANS1183E. WINDOWS ACTIVE DIRECTORY SERVICE IS LEFT IN LOCKED STATE. IC36582 - TSM V5.2.0.0 WINDOWS CLIENT ASR SUPPORT CAN WAIT UP TO 10 MINUTES AFTER CLIENT SILENT INSTALL BEFORE CONTINUING WITH SYS RESTORE. IC36583 - TSM V5.2.0.0 WINDOWS CLIENT ONLINE IMAGE UPGRADE INSTALLATION: 1) NO PROMPT FOR REBOOT 2) ONLINE IMAGE NOT REGISTERED CORRECTLY. IC36665 - TSM CLIENT FAILS WITH INTERNAL SYSTEM ERROR WHEN BACKING UP ENCRYPTED FILES ON A CALERRA NAS BOX. IC36700 - V5.2.0 WINDOWS CLIENT SILENT INSTALL CAN FAIL WITH ERROR MESSAGE DUE TO INCORRECT FEATURE NAME. PACKAGE ISSUE ONLY. IC36719 - BACKING UP A JUNCTION POINT WITH NAMES STREAM, W2K TSM ISSUES: openName Stream C:\\:$MountMgrRemoteDatabase': RC-935. IC36906 - SOME W2K TSM CLIENT GUI WINDOWS ARE TOO LARGE TO FIT ON THE 800x600 SCREENS, AND THE BUTTONS ARE NOT ACCESSIBLE. IC36931 - ANS1803E ON ARCHIVE OF AN EMPTY DIRECTORY. IC36932 - TSM 5.1.X.X CLIENT FAILS WITH INTERNAL PROGRAM ERROR IF RC 21 IS RECIEVED. IC36960 - SOME OPTIONS SET IN THE SERVER SCHEDULE ARE NOT HONORED BY THE CLIENT. IC37040 - JOURNAL SERVICE HANGS AFTER THE JOURNAL DB SIZE REACHES THE 2GB SIZE LIMIT. IC37259 - BACKUP CLIENT GUI DR. WATSONS IF THE ARCHIVE/RETRIEVE BUTTON IS DOUBLE CLICKED FAST. IC37277 - PreserveLastAccessDate DOES NOT WORK CORRECTLY WITH READ-ONLY FILES. IC37292 - V5.2 WINDOWS 2003 CLIENT SYSTEM SERVICE DOMAIN BACKUPS CAN FAIL IF THE RESOURCEUTILIZATION OPTION IS SET TO 4 OR HIGHER. IC37331 - TSM V5.2 WINDOWS DBCS CLIENT WILL NOT START IF USING DBCS USERID AND GUI. GET 'ASSERTION FAILED' MESSAGE. IC37395 - TSM CLIENT IMAGE BACKUP RETURNS INCORRECT MESSAGE, ANS1004W INSTEAD OF ANS1312E WHEN A MEDIA MOUNT IS NOT POSSIBLE. IC37411 - THE IMAGE RESTORE - INCREMENTAL UTILIZES 3.5 TIMES MORE MEMORY DURING THE RESTORE THAN A REGULAR CLASSIC RESTORE. IC37413 - DSMC CAN CORE WHEN ISSUING QUERY NODE COMMAND. IC37421 - BACKUP FAILS WITH ERROR MESSAGE ANS1074I *** USER ABORT *** . IC37440 - CUSTOMIZED DSM.OPT FILE IS NOT COPIED OVER DURING AN INSTALL. IC37480 - BACKING UP THE REGISTRY CAN FAIL WITH ANS4023E ERROR PROCESSING '\\BECKS\C$': FILE INPUT/OUTPUT ERROR. IC37523 - SCHEDULER ERRONEOUSLY REPORTS "COMPLETED SUCCESSFULLY" WHEN EVENT IS MISSED WITH ANS1351E MESSAGE. IC37539 - WIN 2003 CLUSTER DRIVE MOUNT POINTS - TSM SHOULD BE BACKING UP THE FILES AND DIRECTORIES WITHIN THE MOUNT POINTS. IC37556 - TSM CLIENT FOR WINDOWS CORRUPTS REGISTRY PASSWORD FOR NODE IF PASSWORD IS ENTERED INCORRECTLY. IC37627 - WHEN IMAGE BACKUP FAILS, MESSAGE "ANS1804E SELECTIVE BACKUP PROCESSING FOR 'FOO' FINISHED WITH FAILURES" IS ISSUED. IC37716 - RETURN CODE 121 UNKNOWN - IN DSMERROR.LOG WHEN 'dsmc q node' IS RUN. IC37735 - TSM FILESPACE TYPE MAY CHANGE TO "RAW" UNDER RARE CIRCUMSTANCES CAUSING THE FILESPACE TO BE "INVISIBLE" IN THE TSM B/A GUI. IC37761 - TSM ODBC DRIVER APPLICATIONS MAY HANG. IC37799 - TSM WINDOWS CLIENT BACKUP SANERGY CLUSTER RESOURCES. IC37800 - V5.2 TSM WINDOWS CLIENT WIZARDS OR SCHEDULER SERVICE CAN FAIL IF THE NEW SESSIONINIT SERVERONLY OPTION IS SPECIFIED IN DSM.OPT IC37890 - VIRTUALNODE RESTORE OVER SAN PATH CAN FAIL WITH AUTHENTICATION ERRORS. IC37908 - JOURNAL DB WILL BE INVALIDATED IF THE TSM CLIENT JOURNAL BASED BACKUP IS INTERRUPTED. IC38160 - WINDOWS 2003 64 BIT TSM WINDOWS 5.2 B/A CLIENT ONLY ALLOWS FOR INSTALL OF LANGUAGE PACKS TO THE DEFAULT DIRECTORY. IC38165 - TSM CLIENT IS UNABLE TO RESTORE A WIN 2003 MACHINE WHEN THE AD LOGS & AD DATABASE ARE ON DIFFERENT DRIVES. IC38208 - IMAGE BACKUP HANG WITH MULTIPLE FILESPEC. IC38335 - TSM CLIENT LOCKING UP THE MS CERTIFICATE SERVER DATABASE DURING BACKUP. IC38716 - INCORRECT REGISTRY MERGE DURING RESTORE OF WINDOWS REGISTRY.