Peter,

Yes, the netware client does support all netware name spaces, including
the OS2 or long name space. There is something to be aware of however...

Since ADSM keeps only the DOS name space in the data base, ADSM only
supports restoring to the location that the file resided when it
was backed up. In other words, DO NOT give a restore destination. The
creator name, or in this case the long name, of the file is actually
in the SIDF data that ADSM hands back to the tsa during the restore
process. The TSA creates  the file from the SIDF data ADSM keeps in
the repository, not what it keeps in the data base...unless you
restore to a different location. If you do, ADSM basically tells
the TSA to ignore the data in the SIDF, and name it with the name you've
provided with the ADSM data base short name appended. The long name
will be truncated to the short name.

We are currently looking at ways to fix this problem. It would seem
easy to fix, by just keeping the creator name in ADSM's data base rather
than the DOS name. But that leads to other problems. I am leaning toward
keeping 2 entries, the DOS name, like it is done now, along with the
creator name in ADSM's database. During a rename, ie. giving ADSM
a "restore to target", we'll have the real name, not just the DOS name.

Regards,
Frank Ramke

 =======================================================================

Will the ADSM Novell V2R1M0.2 client backup long file names properly on from a
Novell 3.11/3.12 server.

Any feedback would be most appreciated. Have a super weekend, Peter.

BC Institute of Technology
Computer Resources
3700 Willingdon Avenue