I think that this is a windows problem. I have seen this using ADSM,
NTBACKUP,
and scopy commands. I looks to me like NT has problems when it sees a
file name
that looks like the short version of another file.

Marco Ventura wrote:
>
> All,
>
> I've run into a situation where I have two files. The files are listed below:
>
>         Include accounts.xls
>         Includ~1.xls
>
> By the names of the files it looks like the same file, the long filename and 
> the
> short filename. The two files are in the same directory. Some of the
> characteristics are same file size and different date and time.
>
> During a backup (ADSM backup/archive ver 3.1.0.3) ADSM backs up both file as
> separate and independent files.
>
> During restores adsm detects that the file already exists and asks if you want
> to replace.
> Include accounts.xls is restored first then includ~1.xls which is when you are
> asked if you want to replace.
>
> Where not using ADSM client ver 3.1.0.6 due to some of the problems that exist
> especially the application error we get when using the dsmcutil to setup a
> backup schedule service. It creates the service but it doesn't work.
>
> Thanks
> Marco