Hello Michael,
I should add the comment that I do not know the correct answer to this
question.
But given that. If I read the following url correctly The Linux TSM client does
not support unicode at this time. If the filenames are in unicode. If they are
just using chars code over 128 then the doc in the following url lets you know
how to support them.
http://www-1.ibm.com/support/docview.wss?rs=0&q1=tsm+linux+unicode&uid=swg21249081&loc=en_US&cs=utf-8&cc=us&lang=en
Somebody with better IBM reading skills may give you a better answer.
I suspect that using A NDMP backup of the netapp should support the Unicode
chars and handle the filenames.
len
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Michael Green
Sent: Friday, August 17, 2007 5:20 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Backing up files with ilegal characters
Thanks for raising this topic!
I'm curious how one should go about filenames in more than one language?
I work for an academic institution in Israel and besides hebrew we
have here researchers, students and support personnel that speak all
kinds of languages: Russian, Arabic, German, Chinese, Japanese, you
name it..
Our Netapp system that I backup via NFS (on a Linux client) contains
UNIX home directories of all those fellows, locals and foreigners as
one. As you might expect I get tons of ANS4042E and ANS1228E errors
every night.
Frankly, I have no clue how to solve this problem. I've started
administering our Backup environment only recently and till now hadn't
had time to dig deeper into this problem. But as I saw somebody
raising this question here and now, I decided to step in.
Presently I deal with the problem in administrative, not technical
way: I simply warn users that if their data means anything to them, to
not give your files names in "barbarian" languages or I may not be
able to restore it. So far this approach "works" but I wouldn't call
it a good service.
If you have anything helpful on this matter I'd be happy to learn from you.
On 8/16/07, Ing. Fernando Villarreal - Silice S.A.
<fvillarreal AT silice DOT biz> wrote:
> Thank you, I'ww try tihs.
>
> Fernando.
>
> Rainer Tammer escribió:
> > Hello,
> > the Linux client is as far as I know not UNICODE enabled.
> > I had the same problem with the de_DE locale.
> >
> > I just used this LOCALE settings (TSM 5.3 client):
> >
> > export LANG=de_DE
> > export LC_CTYPE=de_DE
> > /opt/tivoli/tsm/client/ba/bin/dsmc
> >
> > Bye
> > Rainer
> >
> >
> > Ing. Fernando Villarreal - Silice S.A. wrote:
> >
> >> Hi, I'm working with TSM version 5.2 and my linux clients report this
> >> kind of errors
> >>
> >> ANE4042E (Session: 17393, Node: SRVDESARROLLO) Object name
> >> '/opt/Projects/Intranet/WebUI/pngs/Sin título-2.png' contains one or
> >> more unrecognized
> >> characters and is not valid. (SESSION: 17393)
> >>
> >> ANE4042E (Session: 17393, Node: SRVDESARROLLO) Object name
> >> '/opt/Projects/Intranet/WebUI/pngs/ban_galería.png' contains one or
> >> more unrecognized
> >> characters and is not valid. (SESSION: 17393)
> >>
> >> We have a lot of files with spanish characters on the file name and we
> >> cannot change
> >> their names. I was googling for a while and there's no clue about how
> >> to solve this.
> >>
> >> Any ideas?
> >>
> >> Thanks you.
> >>
> >> Fernando Villarreal
> >>
> >>
> > Bye
> > Rainer Tammer
--
Warm regards,
Michael Green
|
