Welcome to the IBM Tivoli Storage Manager Version 5.3.2 Windows 32-bit Backup-Archive client!
This file contains information you need for using both the base API and the Backup-Archive Client, as well as information that was not available for the printed publications.
Licensed Materials - Property of IBM
© Copyright International Business Machines Corporation 1990, 2005. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
APARs fixed in Version 5, Release 3, Level 2.0
The client APARs fixed in V5.3.2 can be found in IBM Tivoli Storage Manager
technote 1218412:
http://www.ibm.com/support/docview.wss?rs=663&context=SSGSG7&dc=DB520&uid=swg21218412&loc=en_US&cs=utf-8&lang=en
All client APARs fixed in V5.3 can be found in the '5.3 Fixed Client APARs' section
of Version Release Information in the Other Resources section on the Tivoli Storage
Manager technical support web site at:
http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html
As part of a migration plan from Tivoli Storage Manager V5.2 to Tivoli Storage Manager V5.3, Tivoli Storage Manager clients and servers can 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.
Backup-Archive Client (Includes Base, Common, Image, NAS*, and Admin Client files)
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.
INSTALLATION TYPE TOTAL MB -------------------------------------- Full install (all languages) 216 MB Full install (one language) 60 MB Complete (Typical) install 32 MB
The IBM Tivoli Storage Manager Extended Edition and documentation, while contained on this client CD, is a separate product, and therefore subject to the fees and licensing required by Tivoli and IBM.
See readme file 'README_api_enu_htm'.
The online installation instructions display how much space is required for the selected installation options, and how much space is available on the hard disk.
Rarely, backups of some files might be missed without an explicit error message or warning in the final statistics. However, the operation does return a nonzero return code.
This problem can only occur when all of the following are true:
Until a fix is provided for the problem, use one of the following workarounds:
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
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.
http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/index.jsp
Due to a problem in the TSM BA Client version 5.2.0.x installation program, upgrading the features "Open File Support" and/or "Image Backup" from TSM BA Client version 5.2.0.x will not succeed. The only current workaround is to uninstall version 5.2.0.x and install version 5.3.x. Upgrades from version 5.2.2.x and higher are unaffected by this problem.
Note that 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.
If you are upgrading from client version 4.1 or below, then it is strongly recommended that you rename your existing file spaces before performing your first backup with the 5.3 client. If you already ran a backup with the 5.3 client without renaming the file spaces, then perform a selective or full backup of your volumes to ensure that all Mac files have at least one backup with the 5.3 client. These recommendations also apply to users upgrading from a 4.2 or later client who have not already taken these steps.
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.
Install the 32-bit client on Windows x32 operating systems. Install the 64-bit client on Windows x64 and IA64 operating systems.
+--------------------------+------+-------+-------+--------+--------+--------+
| | 2000 | XP | XP | 2003 | 2003 | 2003 |
| | |32-bit |64-bit | 32-bit | 64-bit | 64-bit |
| | | | x64 | | x64 | IA64 |
| | | | | | | |
+--------------------------+------+-------+-------+--------+--------+--------+
| Journal Based Backup | yes | yes | yes | yes | yes | no |
+--------------------------+------+-------+-------+--------+--------+--------+
| On-line image backup | yes | yes | no | yes | no | no |
| using snapshot | | | | | | |
+--------------------------+------+-------+-------+--------+--------+--------+
| Off-line image backup | yes | yes | yes | yes | yes | yes |
+--------------------------+------+-------+-------+--------+--------+--------+
| System object support | yes | yes | yes | n/a | n/a | n/a |
| via legacy APIs | | | | | | |
+--------------------------+------+-------+-------+--------+--------+--------+
| System State and System | n/a | n/a | n/a | yes * | yes * | yes* |
| Service support via | | | | | | |
| Volume Shadowcopy | | | | | | |
| Services (VSS) | | | | | | |
+--------------------------+------+-------+-------+--------+--------+--------+
| LAN-free operations | yes | yes | yes | yes | yes | yes |
+--------------------------+------+-------+-------+--------+--------+--------+
| Server-free operations | yes | no | no | no | no | no |
+--------------------------+------+-------+-------+--------+--------+--------+
| Automated System | n/a | yes | yes | yes | yes | yes |
| Recovery (ASR) | | | | | | |
+--------------------------+------+-------+-------+--------+--------+--------+
| Open File Support | yes | yes | no | yes | no | no |
+--------------------------+------+-------+-------+--------+--------+--------+
* - the TSM client must be connected to a Tivoli Storage Manager
version 5.2.0 or higher server.
If you are installing from a file downloaded from the anonymous FTP server, then the installation involves two phases:
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 50 MB of disk space for the base client, and 13 MB of disk space for each language pack.
After the second phase (install the client) is complete, the install image will remain on your hard drive. 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:
1682 ANS3010E The Logical Volume Snapshot Agent wizard operation failed.
To bypass this error, point the Setup Wizard to the temporary installation directory or the installation media.
Note: Installing additional features at a later date requires the TSM Client installation media.
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, you can determine the version of MSI on your system as follows:
When performing an interactive install, MSI will be upgraded, if necessary, when the TSM installation is started Following the MSI upgrade, a reboot will probably be required. TSM client installation will continue after the machine has rebooted.
For silent installs, the MSI upgrade will not occur automatically. Instead, the MSI must be manually upgraded before installing the TSM client. The MSI upgrade package, "instmsiw.exe", is included with the TSM client install package. Run "instmsiw /?" from an OS prompt for a list of install switches.
The msiexec REBOOT option can specify one of the following values:
Update to "Client Features" table:
Installing a custom dsm.opt file
If you want to install a custom dsm.opt file, place a copy of the file in the ..\config directory located within the install image:
c:\tsm_images\TSM_BA_Client\baclient\Program Files\Tivoli\TSM\config
The file must be named dsm.opt.
The custom dsm.opt file will not be installed if a dsm.opt file already exists in the ..\baclient directory.
Installation of Microsoft MFC and C Runtime dlls
The following Microsoft dlls are installed to the system directory via Microsoft redistributable package:
The following TSM DLLs are installed in the system32 directory:
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.
Removing online image backup or open file support during the 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, deselecting the features during the upgrade installation will not work. To remove either or both features, 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
How to completely remove TSM from your System
The Tivoli Storage Manager Backup-Archive client generates a variety of user preference information. Some of this resides on the file system and some of it resides in the Windows registry. TSM utilizes Installshield / MSI to handle installing and removing the program bits on the machine. In general, whatever is installed by the setup program is removed by the setup program during uninstall. This is not the case for preference data itself or for containers (registry keys/branches or directories) which contain preference data. In some cases the preference data may be shared with other TSM components or may be intentionally left behind to facilitate a reinstall which will allow the customer to leverage their previous customization settings.
This removal procedure is documented in IBM TSM technote 1141048:
http://www.ibm.com/support/docview.wss?uid=swg21141048
Creating and using SSL certificates is documented in IBM TSM technote 1218512:
http://www.ibm.com/support/docview.wss?rs=663&context=SSGSG7&dc=DB520&uid=swg21218512&loc=en_US&cs=utf-8&lang=en
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\x32\client\Disk1" sub-directory of the CD-ROM, type "setup", and follow the directions in the dialog.
Refer to Chapter 1, section "Upgrading, modifying, or reinstalling the client" in the Tivoli Storage Manager for Windows: Backup-Archive Clients Installation and User's Guide for uninstallation information.
For migration information, see Chapter 1 of the Tivoli Storage Manager Backup-Archive Client Installation and User's Guide for your operating system.
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 Getting Help, Product Documentation section:
http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/index.jsp
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.
Refer to Chapter 2, "Configuring Tivoli Storage Manager" in the Tivoli Storage Manager for Windows: Backup-Archive Clients Installation and User's Guide for complete setup and configuration information.
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
Place this option in the dsm.opt file.
Syntax
->>-TCPCADAddress- cad_address----------------------------><-
Parameters
Examples
The enablearchiveretentionprotection option allows the client to connect to a Tivoli Storage Manager data retention server to ensure that archive objects will not be deleted from the server until policy-based retention requirements for that object have been satisfied. This option is ignored if the client connects to a server that is not retention protection enabled. If the option is 'no' (the default) and an attempt is made to connect to a data retention server, the connection will be refused.
The data retention server is specially configured for that task, so normal backup or restore processing is rejected by the server. When the client is connected to a data retention server, the following commands will not be available. If you attempt to use these commands, a message will be displayed indicating that they are not valid with this server.
Note: restore backupset -location=file or -location=tape do not connect to any server (except the virtual one) and thus will not be blocked under any circumstances.
Supported Clients
This option is valid for all clients.
Options File
This option is valid only in the dsm.sys file within a server stanza and is not valid in a client option set from the server. It is not valid on any command line.
Syntax
-No--
->>-ENABLEARCHIVERETENTIONProtection-+-----+--------------------><-
-Yes-
Parameters
The set event command allows you to specify when archived data is deleted. You can use the set event command to:
Objects affected can be specified with a standard Tivoli Storage Manager filespec (including wildcards), a list of files whose names are in the file specified using the filelist option, or a group of archived files with the description specified with the description option.
Note: When only a <filespec> is used, all archived copies of files or folders matching the filespec are affected. If you only want to affect certain versions of a file, use the -pick option and select from the displayed list.
Interaction with down-level servers: If the set event command is issued when the client is connected to a server that does not support event-based policy (previous to Tivoli Storage Manager 5.2.2), the command will be rejected with an error message indicating that the current server does not support event-based policy.
The enablearchiveretentionprotection option allows the client to connect to a Tivoli Storage Manager data retention server to ensure that archive objects will not be deleted from the server until policy-based retention requirements for that object have been satisfied. See "Enablearchiveretentionprotection" above for more information on this option.
Supported Clients
This command is valid for all clients.
Syntax
->>-SET Event---- -TYPE=--+-Hold--------------+------------------>-
+-Release-----------+
-Activateretention-
->-- ---- -- -FILEList=-- -- -DEScription=--->-
->-- -PIck------------------------------------------------------><-
Parameters
The following options can also be used and serve their usual purpose:
Examples
Rebinding--> 274
/home/accounting/ledgers/jan05.books
opt [Sent]
Rebinding--> 290
/home/accounting/ledgers/feb05.books
opt [Sent]
Total number of objects archived: 0
Total number of objects failed: 0
Total number of objects rebound: 2
Total number of bytes transferred: 0 B
Data transfer time: 0.00 sec
Network data transfer rate: 0.00 KB/sec
Aggregate data transfer rate: 0.00 KB/sec
Objects compressed by: 0%
Elapsed processing time: 00:00:02
TSM Scrollable PICK Window - Retention Event : ACTIVATE
# Archive Date/Time File Size File
----------------------------------------------------------------------
1. | 08/05/2003 08:47:46 766 B \\user\c$\tsm521\common\winnt
2. | 08/01/2003 10:38:11 766 B \\user\c$\tsm521\common\winnt
3. | 08/05/2003 08:47:46 5.79 KB \\user\c$\tsm521\common\winnt
4. | 08/01/2003 10:38:11 5.79 KB \\user\c$\tsm521\common\winnt
5. | 08/05/2003 08:47:46 10.18 KB \\user\c$\tsm521\common\winnt
The TSM Logical Volume Snapshot Agent (LVSA) is a storage volume filter driver that provides open file and online image support. IBM has done extensive testing with the LVSA driver and is confident in its stability and function, and it is fully supported by IBM. IBM is actively working with Microsoft on a driver signing process but, the driver is currently not signed. Since LVSA is not signed, it was not tested as part of the windows certification process. The LVSA driver is included with the TSM client package but is not installed by default. If your organization has a strict policy which does not allow non-signed drivers to be installed, then you should not use TSM's open file and online image features until the LVSA driver signing work has been completed.
Note that offline image backups can be performed without installing the LVSA driver.
The Tivoli Storage Manager Backup-Archive client generates a variety of user preference information. Some of this resides on the file system and some of it resides in the Windows registry. TSM utilizes Installshield / MSI to handle installing and removing the program bits on the machine. In general, whatever is installed by the setup program is removed by the setup program during uninstall. This is not the case for preference data itself or for containers (registry keys/branches or directories) which contain preference data. In some cases the preference data may be shared with other TSM components or may be intentionally left behind to facilitate a reinstall which will allow the customer to leverage their previous customization settings.
This removal procedure is documented in IBM TSM technote 1141048. To read the technote you can go to the following URL and enter 1141048 in the search box, then click on the resulting entries.
http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html
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
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 system options file.
Syntax
->>-LANFREETCPServeraddress- stagent_address----------------------><-
Parameters
Examples
Rarely, backups of some files might be missed without an explicit error message or warning in the final statistics. However, the operation does return a nonzero return code.
This problem can only occur when all of the following are true:
Until a fix is provided for the problem, use one of the following workarounds:
During a command line client operation, CTRL-C might result in a TSM client program exception or other unexpected behavior. To abort a command line client operation, use the 'Q' key instead of CTRL-C.
The Search/Filter function might appear unresponsive when searching through very large filesystems. This is caused by the Java Virtual Machine (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.
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 UNIX and Linux Backup-Archive Clients Installation and User's Guide" for more information.
Running more than one restore or retrieve operation at the same time from the Web Client might 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, close the Web Client browser windows, stop the TSM Agent service, then try again using only one Web Client session.
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 might cause the browser to crash due to resource limitations.
ANS1521E Failure writing to a Tivoli Storage Manager log or log-related
file: TSM Pruned Log, errno = 28, There is not enough space in
the file system
This is correct behavior. However, the log header record might 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.
"dsmc backup nas -nasnodename=netapp1"
all the mounted filesystems on the node netapp1 will get backed up. The reason for this is that there is no filespec specified on the command line and there is no domain.nas option specified in the options file - with the result the default for domain.nas option, ALL-NAS is used and all the mounted filesystems on the node netapp1 will get backed up.
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.
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 the version that you want to restore.
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:
HKEY_LOCAL_MACHINE\
SYSTEM\
CurrentControlSet\
Control\
Nls\
CodePage
c_858.nls
To enable support for the Latin 1 code page, do the following:
HKEY_LOCAL_MACHINE\
SYSTEM\
CurrentControlSet\
Control\
Nls\
CodePage
c_850.nls
09/20/2005 14:44:24 Attempt to free unknown pointer. Addr 010C0546, File \Tsm532c_g4_x32\client\winnt\DPrefsInclExclPage.cpp, Line 1492
The above problem might occur 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.
http://uranus.it.swin.edu.au/~jn/linux/rawwrite/dd.htm
As an example, you can enter the following command to copy the image data from the file x.img to the volume x: with the block size of 1 megabyte:
c:\> dd if=x.img of=\\.\x: bs=1M
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.
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 occurrences, 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:
Change statement
"REM pause"
to
"pause"
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.
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 V5.1.5 (or higher) clients.
The new journal database implemented in release 5.3.0 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 can 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.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem
Notes:
A directory move operation can 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 performed, the TSM Journal daemon might not correctly identify the operation as a directory "move".
Some antivirus software can incorrectly generate change notifications to the TSM journal service, causing files that have not changed to be incorrectly backed up during 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 and higher.
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:
HKLM\Software\Intel\LANDesk\VirusProtect6\CurrentVersion
NoFileMod = 1
This setting prevents Nav from caching and restoring timestamps and security information during scan processing.
[JournaledFileSystemSettings]
NotifyFilter=0x15b
This setting will generate change notifications for the following type of change activity:
It will not generate notification for last access timestamp or attribute bitmask changes.
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.
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.
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.
If part of the volume resides on an area of the drive with bad sectors TSM will skip 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:
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.
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.
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 client can be used for remote OFS operations.
If the temporary installation directory (i.e.,
ANS3010E The Logical Volume Snapshot Agent wizard operation failed.
To bypass this error 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.
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 precludes inadvertently restoring 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:
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.
MAXNUMMP | LANFREE mounts | LAN mounts
-------------------------------------------
2 | 1 | 2
3 | 2 | 3
4 | 3 | 3
IBM Software Support provides assistance with product defects.
Before you submit your problem to IBM Software Support, ensure that your company has an active IBM software maintenance contract, and that you are authorized to submit problems to IBM. The type of software maintenance contract that you need depends on the type of product you have:
For IBM distributed software products (including, but not limited to, Tivoli, Lotus, and Rational products, as well as DB2 and WebSphere products that run on Windows or UNIX operating systems), enroll in Passport Advantage in one of the following ways:
If you are not sure what type of software maintenance contract you need, call 1-800-IBMSERV (1-800-426-7378) in the United States. From other countries, go to the "Contacts" page of the IBM Software Support Handbook at http://techsupport.services.ibm.com/guides/contacts.html and click the name of your geographic region for phone numbers of people who provide support for your location.
To contact IBM Software support, follow these steps:
When you report a problem to IBM, you are asked to supply a severity level. Therefore, you need to understand and assess the business impact of the problem that you are reporting. Use the following criteria:
| Severity 1 | The problem has a critical business impact: You are unable to use the program, resulting in a critical impact on operations. This condition requires an immediate solution. |
| Severity 2 | This problem has a significant business impact: The program is usable, but it is severely limited. |
| Severity 3 | The problem has some business impact: The program is usable, but less significant features (not critical to operations) are unavailable. |
| Severity 4 | The problem has minimal business impact: The problem causes little impact on operations, or a reasonable circumvention to the problem was implemented. |
When describing a problem to IBM, be as specific as possible. Include all relevant background information so that IBM Software Support specialists can help you solve the problem efficiently. To save time, know the answers to these questions:
You can submit your problem to IBM Software Support in one of two ways:
If the problem you submit is for a software defect or for missing or inaccurate documentation, IBM Software Support creates an Authorized Program Analysis Report (APAR). The APAR describes the problem in detail. Whenever possible, IBM Software Support provides a workaround that you can implement until the APAR is resolved and a fix is delivered. IBM publishes resolved APARs on the Software Support Web site daily, so that other users who experience the same problem can benefit from the same resolution.
To receive technical support for Tivoli Storage Manager:
http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html
On-line discussions
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:
Latest info
http://www.ibm.com/software/tivoli/products/storage-mgr/index.html
The following terms are trademarks of International Business Machines Corporation 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.
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.
Third party license terms and conditions, notices and information
The license agreement for this product refers you to this file, or to a file referenced by this file, for details concerning terms and conditions applicable to third party software code included in this product, and for certain notices and other information IBM must provide to you under its license to certain software code. The relevant terms and conditions, notices and other information are provided in the "LICENSE.TXT" file on the root directory of the first installation CD-ROM for this product. The "LICENSE.TXT" file is also installed into the root installation directory as part of the installation process. Please note that any non-English version of the information in this file is unofficial and is provided to you for your convenience only. The English version of the file is the official version.