We also have a similar situation at my company. Since we can not dedicate
a server specifically for Japanese files, we did set up a specific
directory on one of the servers for the Japanese. This directory is then
zipped and the zipped file is backed up during our normal processing.
Andrew Webster <andrew.webster AT DB DOT COM>@VM.MARIST.EDU> on 05/14/2001
11:03:14 PM
Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Re: Japanese Filenames
Hi Paul,
> Has any body had any experience of this in this type of environment?
Unfortunately YES.
USEUNICODEFILENAMES NO (The Default)
TSM won't backup Japanese filenames unless you run the client on a Japanese
NT server. Adding the Japanese codepage to a UK build won't work.
USEUNICODEFILENAMES YES
TSM will backup Japanese filenames most of the time, but occassionally dies
a horrible death on certain filenames. With lots of people with lots of
Japanese filenames, the client will fail more than it suceeeds.
USEUNICODEFILENAMES is suppose to be used with Macintosh files, any other
use is convenently unsupported by Tivoli.
You need to do your restores, with the same USEUNICODEFILENAMES setting
that was done with the Backup. As you've found.
Under Japanese NT, all filenames with show up in Japanese characters in
GUI. The same can't be said about the WEB GUI.
Tivoli support (especially, the Japanese end) are no help whatsoever. As a
company, Tivoli seem to have no concept that people do business in multiple
languages, and as a backup product Tivoli need to support it. Recents
failures, where the NT server product failed as soon as you run it under
Japanese, German etc.. bears testiment to the fact, Tivoli aren't even
testing their products under different languages.
<I'll get off my soap box now >
The only way out of it, is to build a dedicated Japanese NT server, and
back everything up remotely with multiple schedules. The one I set up Tokyo
was running 12 backup schedules (that 12 NT services). You need a big box
though, preferable with GigE links to whatever you are going to backup. CPU
power is also an issue, I had to upgrade from a Dual to a Quad processor to
get the backups completed overnight.
You'll also have to do your restores from there as well, so need a Remote
Console/Control utility to get to the box and not many of them will let you
control a Japanese PC from an English workstation.
Regards
Andrew Webster
TSM/Storage Consultant
Deutsche Bank, Australia
Office : +61 3 9270-4229
Mobile : +61 (0) 40999 6515
Fax: +61 3 9270-4144
E-Mail : andrew.webster AT db DOT com
paul.bestow@pho
enixsm.com To: ADSM-L AT vm.marist DOT edu
cc:
14/05/2001 Subject: Japanese Filenames
11:32 PM
Please respond
to ADSM-L
Hi all,
We are running an NT environment using version 4 TSM client and server code
to back up all our data. On our file and print server we have a lots of
Japanese filenames. We have installed our NT servers as UK operating
systems, but have installed the Japanese code page to facilitate the use of
Japanese filenames.
When we use TSM gui to back up these filenames they are displayed as
invalid
files. We have tried turning on USEUNICODEFILENAMES in the client option
file, and all these seems to do is instead of the filenames being invalid
they appear as question marks.
Has any body had any experience of this in this type of environment?
http://www.phoenixitgroup.com
******************Internet Email Confidentiality Footer*******************
Phoenix IT Group Limited is registered in England and Wales under company
number 3476115. Registered Office: Technology House, Hunsbury Hill Avenue,
Northampton, NN4 8QS
Opinions, conclusions and other information in this message that do not
relate to the official business of our firm shall be understood as neither
given nor endorsed by it.
No contracts may be concluded on behalf of our firm by means of email
communications.
Confidentiality: Confidential information may be contained in this message.
If you are not the recipient indicated (or responsible for delivery of the
message to such person), you may not take any action based on it, nor
should
you copy or show this to anyone; please reply to this email and highlight
the error to the sender, then delete the message from your system.
Monitoring of Messages: Please note that we reserve the right to monitor
and
intercept emails sent and received on our network.
Warning: Internet email is not 100% secure. We ask you to understand and
observe this lack of security when emailing us. We do not accept
responsibility for changes made to this message after it was sent
Viruses: Although we have taken steps to ensure that this email and any
attachments are free from any virus, we advise that in keeping with good
computing practice the recipient should ensure they are actually virus
free.
--
This e-mail may contain confidential and/or privileged information. If you
This e-mail may contain confidential and/or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorised copying, disclosure or distribution of the material in this
e-mail is strictly forbidden.
|
