[<<]Message[>>]    [<<]Author[>>]    [<<]Subject        [<<]Thread[>>]

Number   :  4118
Date     :  2003-03-24
Author   :  Garry Deane
Subject  :  Re: DATE COMPARISON FAILURE when xxcopying to CD-RW with DLA
Size(KB) :  2


--- In xxcopy@yahoogroups.com, "roaksroaks"  wrote:
> I am encountering a very mysterious problem related to my
> previous post. Help would be greatly appreciated.
> 
> As I mentioned in my original post, I found that date
> comparison doesn't work correctly when copying from an
> XP Pro NTFS folder to a CD-RW drive that uses Veritas
> DLA (a popular DirectCD equivalent). 
> 
> One user (Chaz Cone) suggested using the /FF switch and
> that seemed to resolve the problem but, unfortunately,
> the plot thickens. If anyone has seen anything like the
> following, I'll be amazed.
> 
> Here's my command line:
> 
> /clone /ce /ff90s /yy /pb /oAlog.txt /oD3 /oE3 /oF3 /oS2
> /oI2 /oX2
> 
> I'm cloning the My Documents folder to the same folder on
> the CD-RW. There are 5138 files in 380 folders. Notice
> that I'm using /ff90s in case /ff wasn't sufficient.
> 
> If I run this once and then run it again, shortly
> thereafter (say 30 minutes later), it doesn't copy
> anything (which is correct). If I wait several hours
> (say overnight), it copies about 700 files. 
> Another run, a few minutes later, once again copies nothing.
> There really doesn't seem to be anything distinctive about
> the files that are copied. Obviously, they have not been
> modified. Their folder is not any deeper than folders that
> aren't selected. Their filenames are not distinctive. I
> notice that some selected files are followed by a byte
> count and some are followed by /BI. What is the difference?
> I would assume that /BI indicates a file that was selected
> because it was newer as opposed to being new (not existing
> in the destination folder) but, of course, none of the files
> are new.

I see that you have /ff90s. Although Xxcopy appears to accept this, 
the documentation has no reference to the 's' so maybe try just /ff90.

Also, although there is only a small chance that this will be the 
cause, try using /NX0 to disable short filename preservation. I had a 
simiar set of symptoms using DirectCD which was caused by the 
filesystem that DirectCD used. Using /NX0 solved the problem.


> One other (probably irrelevant) detail. There are two files
> on my system (SQL Server files that are locked) that can't
> be backed up and always generate a file copy error.

Simply exclude them with /X or /EX. If you need to copy 
them, you have to shut down the SQL Server. I'm not familiar with the 
procedures involved but I think you can use SQLManager to shut down 
the Server in an orderly mannner.

Garry



This message if part of XXCOPY's message Archive.
The archive contains all the messages posted at Yahoo!Groups: XXCOPY.