I think that is a known problem. Below is APAR text for V4 client; there is
also info on this error with 3.1.0.x clients. Go to www.adsm.org, search on
"active object not found".
++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Item IC29552
APAR Identifier ...... IC29552 Last Changed..01/04/19
UMLAUT ANS1304W ACTIVE OBJECT NOT FOUND WITH INTERNATIONAL
CHARACTERS IN DIRECTORY/FILENAME: INCORRECT EXPIRATION OF FILES.
Symptom ...... NF MSGANS1304W Status ........... CLOSED PER
Severity ................... 1 Date Closed ......... 01/04/19
Component .......... 5698TSMCL Duplicate of ........
Reported Release ......... 41W Fixed Release ............ 999
Component Name TIVOLI STR MGR Special Notice HIPER
Current Target Date ..01/06/10 Flags
SCP ................... UNIX FUNCTIONLOSS
Platform ............ UNIX DATALOSS
Status Detail: Not Available
PE PTF List:
PTF List:
Release 41W : PTF not available yet
Release 41W : Relief is available in the form of: 4.1.2.12
Parent APAR:
Child APAR list:
ERROR DESCRIPTION:
This problem is specific to Win32 client and an issue with
international characters.
This problem is also specific to the 4.1.2 TSM client level.
The only character that has been recreated with problems is
the and (u umlaut) character, although this may effect
other umlaut characters, or other international chars.
---
Files backed up that contain or as opposed to
and are handled differently by TSM 4.1.2
windows client.
The apparent cause of this is a problem with casing
with and .
Show versions from the TSM server will display a
difference between capital and lowercase for .to
\\ddoering\d$ : \TEST\ FILE.TXT (MC: DEFAULT)
Active, Inserted 02/07/2001 16:28:20
ObjId: 0.3213
\\ddoering\d$ : \TEST\ FILE .TXT (MC: DEFAULT)
Active, Inserted 02/07/2001 16:28:20
ObjId: 0.3210
All other characters are displayed as capital letters
on the TSM server, regardless of whether they were
originally Upper or Lower case.
This casing issue causes different symptoms:
1) Files backed up with capital are restored as
lowercase .
Ex. A backup of file.txt will be restored as file.txt
The case switching from Upper to Lower case also occurs
for directory entries on restore.
2) Objects are erroneously expired because the client
treats them as being deleted from the filesystem on
incremental backup because we are looking for the
wrong case of filename/directory.
Ex.
Incremental backup of volume 'D:\TEST\*'
Expiring--> \\ddoering\d$\test\ dir\ file.txt Sent
Expiring--> \\ddoering\d$\test\ dir\ file.txt Sent
Expiring--> \\ddoering\d$\test\ dir\ file.txt Sent
Expiring--> \\ddoering\d$\test\ dir\testfile.txt Sent
Expiring--> \\ddoering\d$\test\ dir\file .txt Sent
Expiring--> \\ddoering\d$\test\ dir\file .txt Sent
Expiring--> \\ddoering\d$\test\ dir\file .txt Sent
Expiring--> \\ddoering\d$\test\ dir Sent
Directory-- \\ddoering\d$\test\ dir Sent
Normal File--> \\ddoering\d$\test\ dir\ file.txt Sent
Normal File--> \\ddoering\d$\test\ dir\ file.txt Sent
Normal File--> \\ddoering\d$\test\ dir\file .txt Sent
Normal File--> \\ddoering\d$\test\ dir\file .txt Sent
Normal File--> \\ddoering\d$\test\ dir\file .txt Sent
Normal File--> \\ddoering\d$\test\ dir\testfile.txt Sent
Normal File--> \\ddoering\d$\test\ dir\ file.txt Sent
Notice the Upper case sent at backup is switched to
lower case for expiration (and also on restore).
3) Objects are incorrectly displayed in the client GUI
for restore showing objects that were backed up as
capital to be lower case .
4) Objects backed up under a directory that contains a
lower case are not viewable in the GUI, restoring this
directory will not return any files.
5) Receiving ANS1228E Sending of object ... failed
ANS1304W Active object not found
when trying to expire an object that was backed up with a
or in the name/directory path.
In testing this only happened on files that were located
under a directory that was backed up with a capital , and
the filename contained a lower case .
This problem is specific to the 4.1.2 TSM client on Windows.
Although testing has only shown problems with , this may
effect other international characters.
*note* capital umlaut characters above may not be appearing
in the apar text.
Additional Keywords: MSGANS1228E win95 umluat unicode nls
win2000
LOCAL FIX:
Apply PTF when available, backlevel to 4.1.1 TSM client as
testing did not show problems with case of umlaut characters
at 4.1.1 level of client.
Going back to the V4.1.1 level client may
cause files backed up with the V4.1.2 client with
the incorrect name to be expired. The number of files
expired is controlled by the VERDELETED parameter of the
backup copygroup. Before going back to V4.1.1, consider
increasing VERDELETED if necessary to preserve
the inactive versions.
PROBLEM SUMMARY:
****************************************************************
* USERS AFFECTED: TSM V4.1.2.0 Windows NT and 2000 clients *
****************************************************************
* PROBLEM DESCRIPTION: The TSM 4.1.2.0 Windows NT and 2000 *
* client (not 95, 98, or ME) was storing file names
* containing international characters incorrectly on *
* the TSM server. Symptoms include seeing the following *
* messages displayed during backups and in dsmerror.log: *
* *
* ANS1228E Sending of object <filename> failed *
* ANS1304W Active object not found *
* *
* Another symptom is that files containing international *
* characters could be backed up during every incremental *
* backup operation, even if the file had not changed. This *
* could cause truly different backup versions to be expired *
* prematurely. *
* *
* Another symptom is that valid, existing path names passed *
* to the client via the command line were not recognized if *
* the path contained international characters. For example: *
* *
* SEL E:\DEU\ DIR\ -SUBDIR=YES *
* *
* would result in this message: *
* *
* ANS1092E No files matching search criteria were found *
* *
* where <filename> is the name of an affected file. *
****************************************************************
* RECOMMENDATION: Apply the fixing code when available. There *
* is a fixing patch currently available that consists of: *
* *
* - A TSM client that correctly handles file names with *
* international characters *
* *
* - a clean-up utility to remove incorrect versions from *
* the TSM server. *
* *
* The patch can be obtained via FTP download at site: *
* *
* ftp.software.ibm.com *
* *
* The directory is: *
* *
* storage/tivoli-storage-management/maintenance/client/ *
* v4r1/Windows/i386/LATEST *
* *
* Be sure to read the files IP22151_12_TSMCLEAN_README.FTP *
* and IP22151_12_TSMCLEAN_README.1ST before using either *
* the clean-up utility or the new client patch. Note that *
* the README files mention using the 4.1.2.12 client after *
* performing the clean-up. However, if a version later than *
* 4.1.2.12 is available, then use that later version, *
* because patches are cumulative. *
****************************************************************
PROBLEM CONCLUSION:
Microsoft Windows allows file names to be created that contain
any combination of upper- and lower-case characters, and the
file system will maintain the given casing for a file. This is
known as "case preserving". However, the casing of a file name
by itself does not distinguish one file from another. This is
known as "case insensitive". For example, MYFILE.TXT,
MyFile.txt, and myfile.TXT are all considered to be the same
file. This is as opposed to UNIX, where these would be
considered three separate files.
In order to facilitate TSM support for case preserving, case
insensitive file names, all Windows file backups are stored on
the TSM server with the file names converted to upper case. This
is done in order for the TSM server to recognize that
MYFILE.TXT, myfile.txt, and MyFile.txt all refer to the same
file name. The information necessary to restore the files with
their correct casing is kept elsewhere in the database.
A problem in the TSM 4.1.2.0 client for Windows caused files
with certain international characters in their names (such as a
'u' with an umlaut: ) to be stored incorrectly on the TSM
server. That is, the problem characters are not converted to
uppercase (i.e. is not properly converted to ). As a result,
incremental backup operations may not handle these files
properly. Symptoms were varied, but included the following:
- Backup versions of files with these international characters
that were created with a client version prior to 4.1.2.0 were
expired. Because this caused the VERDELETED setting of the
management class's copygroup to go into effect, older backup
versions were deleted from the server. These versions could no
longer be recovered.
- The existing files with these characters in their names were
backed up during each incremental backup cycle, regardless
of whether the file changed. Prior versions of the file were
deleted from the TSM server based on the VEREXISTS setting. As
a result, the server may have had multiple backup copies of
the same state of the file, and truly different versions of
the file may have been deleted.
- The following messages were displayed during backups, and
logged to dsmerror.log:
ANS1228E Sending of object <filename> failed
ANS1304W Active object not found
- If a directory name contained one of these characters, files
and subdirectories within that directory were also expired and
may not have been restorable.
Starting with client version 4.1.2.12, the code has been fixed
to correctly handle file names containing international
characters. In addition, a utility was made available to clean
up incorrectly cased backup versions from the TSM server. See
the "PROBLEM SUMMARY" section above for information on where to
obtain the clean-up utility and fixing code.
TEMPORARY FIX: *********
* HIPER *
*********
COMMENTS:
MODULES/MACROS: DSMC DSM
SRLS: NONE
RTN CODES:
CIRCUMVENTION:
MESSAGE TO SUBMITTER: Minor punctuation and spacing changes to
the PROBLEM SUMMARY section; added text back in to PROBLEM
SUMMARY that was inadvertantly deleted.
----------------------------------------------------------------------------
----
----
For IBMLink customer support in the U.S, call 1-800-543-3912.
For IBMLink customer support in the U.S, call 1-800-543-3912.
----------------------------------------------------------------------------
----
----
[ IBM Home | Shop | Contact | Search | Privacy | Legal ]
[ IBM Home | Shop | Contact | Search | Privacy | Legal ]
|
