Hello,

starting with version 4.2 the TSM client for Windows NT/2000/XP writes
filespaces in unicode format, if the server also is 4.2 or higher.

For new filespaces, this is ok. The problem comes with old filespaces,
which have been backed up with an old client or server version. They
have to be converted to unicode format, triggered by the AUTOFSRename
option on server and client side.

As long as this conversion is not done, some files are skipped during
backup (those having names containing characters from a code page
that is different from the current locale) and even better: if they
have previously been backed up with a pre-4.2 client, they are now
expired!

So, the conversion is URGEND! On the other hand, it is expensive,
because it renames the old filespace and creates a completely new
backup. For us this means that we cannot do all conversions at once,
we have to spread them over time. So now comes the question:

How do you determine, which filespaces need the conversion most?

How do you determine, which ones need it at all?

The skipped files do not show up in dsmsched.log (at least under
my 4.2.2 client running on Win 2000). Are there any other means,
perhaps Windows based, to find file name containig characters from
a different code page than the client's current one?

Has anybody gone through it at all?

Greetings,

Reinhard
--
Reinhard Mersch                        Westfaelische Wilhelms-Universitaet
Zentrum fuer Informationsverarbeitung - ehemals Universitaetsrechenzentrum
Roentgenstrasse 9-13, D-48149 Muenster, Germany      Tel: +49(251)83-31583
E-Mail: mersch AT uni-muenster DOT de                       Fax: 
+49(251)83-31653