I have around 5 servers with a mixture of NT and Mac files, and I only use
one client per server with the "useunicodef yes" option.  The success of
backing up Mac files also depends on your client code level, I am having
problems with some Mac files failing with the 4.1.2 code, which I assume
is related to the current character set problems with that version.  The
later 3.7 clients and the 4.1.1 clients worked well.


===========================================
    John Monahan
    Network Team Coordinator
    Liberty Diversified Industries
    (763) 536-6677
===========================================





Paul Baines <paulbaines AT GMX DOT DE>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
02/23/01 08:57 AM
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: FIVE questions for TSM 4.1.2 (server on AIX,        
      clients on
Windows)


> 4.      Is there a MAC agent that allows for the "illegal characters"
> associated with Apple/Macintosh naming conventions?  EXAMPLE:  We have
an
> NT
> server that the MAC clients connect to.  This NT server contains the
home
> directories for all the MAC clients.  Veritas' Backup Exec handles these
> files (and their "illegal characters") correctly, but TSM has problems.

I believe this is controlled by the USEUNICODEFILENAMES parameter. I am
not
certain, (test it yourself), but you would need to set up two clients on
your
server, one DSM.OPT containing USEUNICODEFILENAMES YES; LANG AMENG; and
EXCLUDE.DIR all the NT directories. And one DSM.OPT containing
USEUNICODEFILENAMES NO; and EXCLUDE.DIR all Mac directories.
This means, of course, 2 client licenses per box.


--
Sent through GMX FreeMail - http://www.gmx.net
Sent through GMX FreeMail - http://www.gmx.net