I have a server that replicates a set of folders out to many machines. However one in particular seems problematic. About once a week it seems like one of the BC3 processes decides it suddenly needs to copy a HUGE number of files. For instance this morning when I came in there were only 2 proceses running, both were the same script. When I cancelled them this is what the log shows:
3/29/2010 6:48:25 AM >> log 3Dvia-fcipofs01.log
3/29/2010 6:48:25 AM >> option confirm:yes-to-all
3/29/2010 6:48:25 AM >> sync create-empty mirror:lt->rt
3/29/2010 10:31:24 AM Successfully synchronized 3681 items. Failed to synchronize 3825 items. Completed in 3 hours, 42 minutes.
3/29/2010 10:31:24 AM >> User Cancelled
3/29/2010 10:31:24 AM Script completed in 6 hours, 52 minutes
3/29/2010 10:31:31 AM Successfully synchronized 104539 items. Failed to synchronize 335616 items. Completed in 4 days, 5 hours.
So the script that started 4 days ago thought it needed to copy (104539 + 335616) files. However even though 4 days later it still had not copied 335616 of those files, when another BC3 script started up, it saw that only 3681 files needed to be copied. Obviously this just makes no sense.
My .bat file:
"C:\Program Files\Beyond Compare 3\BCompare.exe" @d:\admin\replicationdata\3Dvia-fcipofs01.txt
My script:
load "Seemage-Ref fcipofs01"
log 3Dvia-fcipofs01.log
option confirm:yes-to-all
sync create-empty mirror:lt->rt
I use Windows Server 2003's scheduled tasks to start the process at 3:39AM each day. Although I have the 'stop taks if it runs more than.. hours' set, it only kills the bat file, so if this happens, it starts running multiple BC sessions to the same remote client, which only kills our bandwidth even more.
BC ver 3.1.9 build 11282
3/29/2010 6:48:25 AM >> log 3Dvia-fcipofs01.log
3/29/2010 6:48:25 AM >> option confirm:yes-to-all
3/29/2010 6:48:25 AM >> sync create-empty mirror:lt->rt
3/29/2010 10:31:24 AM Successfully synchronized 3681 items. Failed to synchronize 3825 items. Completed in 3 hours, 42 minutes.
3/29/2010 10:31:24 AM >> User Cancelled
3/29/2010 10:31:24 AM Script completed in 6 hours, 52 minutes
3/29/2010 10:31:31 AM Successfully synchronized 104539 items. Failed to synchronize 335616 items. Completed in 4 days, 5 hours.
So the script that started 4 days ago thought it needed to copy (104539 + 335616) files. However even though 4 days later it still had not copied 335616 of those files, when another BC3 script started up, it saw that only 3681 files needed to be copied. Obviously this just makes no sense.
My .bat file:
"C:\Program Files\Beyond Compare 3\BCompare.exe" @d:\admin\replicationdata\3Dvia-fcipofs01.txt
My script:
load "Seemage-Ref fcipofs01"
log 3Dvia-fcipofs01.log
option confirm:yes-to-all
sync create-empty mirror:lt->rt
I use Windows Server 2003's scheduled tasks to start the process at 3:39AM each day. Although I have the 'stop taks if it runs more than.. hours' set, it only kills the bat file, so if this happens, it starts running multiple BC sessions to the same remote client, which only kills our bandwidth even more.
BC ver 3.1.9 build 11282
Comment