Posted by Mike Saunders on November 01, 2007 at 06:09:37:
Well I will report my observations and you can compose your own theories.
Okay running a different part of the conversion last night and slipped again with the backup program(now have the scheduling service disabled). Maybe the backup program is part of the problem, maybe not. Backup scheduled to start at 2355 hrs.
Same old - non updated Comet Server.
This time the conversion program was running in a Comet Session on the Comet Server.
The program was reading from one comet directory and writing to another. About 2.7GB of data in the output.
This conversion process normally takes around 9 hours and we have been testing it for the past week at night, on those runs the backup did not kick in.
I came in, saw the error. Stopped/restarted the comet session on 11/01 about 0725 hrs.
Looking Date/Time stamp for files in output directory through windows.
Conversion started 10/31 @ 1749 hrs
Shows processing files up to 1758 hrs
QDIR file shows time of 1758 hrs.
Then I have one data file with a time of 2359 hrs.
Then I have 97 additional data files, all with a time stamp of 11/01 @ 0725.
Like they were cached somewhere and written (or at least touched) once the Comet Session was either terminated or restarted.
The conversion program did not get restarted.
All these files do show up under a catalog in comet.