Without specific error message, I'm going to assume you're getting the same
problem we have/had here. The new client is trying to do the short-to-long
filename conversion and choking. We opened an ETR with Tivoli and the
response was the 4.2 level of BOTH client and server will fix the problem
with the conversion. In the mean time, you can either:

1. Specify MEMORYEFFICIENTBACKUP YES in the DSM.OPT file. This will prevent
the client from doing the conversion.

2. Give the client a different nodename. The files will be backed up
correctly using the long filename. No conversion is done in this case, BUT
you'll get a full backup the first time.

We've done a combination of the two, depending on the size of the client.
Can't really afford to backup everything on some of them again.

Bill Boyer
DSS, Inc.
  -----Original Message-----
  From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
kelil kenzu
  Sent: Tuesday, August 28, 2001 11:40 AM
  To: ADSM-L AT VM.MARIST DOT EDU
  Subject: Long Filename Error


  We recently upgrade NT client from version 3.1.7 to 4.1.3.  Since the
upgrade we have had problems backing up some of our clients.  Scheduled
backups abort with the error of long filenames.  However, the same files
that we are having problems backing up with the new client used to be
backuped with 3.1.7 with out any problems.  When i try to do a restore the
last time these files were backuped were with the old ADSM Client version.

  Any Ideas would be greatly appreciated


  Thanks,

  Kelil


----------------------------------------------------------------------------
--
--
  Get your FREE download of MSN Explorer at http://explorer.msn.com
  Get your FREE download of MSN Explorer at http://explorer.msn.com