none
Synch failed due to error but timestamp modified RRS feed

  • Question

  • SynchToy 2.1 has worked reliably for some time but I recently ran into the following problem.

    File 1 on computer A (A1) was several weeks newer than the same File 1 on computer B (B1). The synch started and A1 was being copied to B1 but an error occured and B1 was not successfully replaced. However the B1 timestamp was modified without me realizing it. I ran SynchToy again and the synch completed without error but because of the timestamp change, B1 replaced A1! It seems reasonable that the destination timestamp should not be changed until the destination is successfully updated.

    BTW, the file in question was an Outlook mailbox and the synch failed because the file was changed during the copy. However Outlook was not running and no Outlook processes were running. Any insight into how the file could have changed would be greatly appreciated.

    Monday, May 10, 2010 3:06 PM

All replies

  • Hi Tom,

    Thanks for reporting your problem. I have never seen similar issues before.

    I am not sure whether timestamp of B1 was changed when the sync error happened, because B1's timestamp should not be newer than A1 (it sould equal to A1 at worst). Thus B1 should not overwrite A1 even if B1's timestamp had been changed during the syncing with sync error, unless the it was influenced by Summer Time (Daylight Saving Time).

    But it seems surely that SyncToy was confused by the error. SyncToy may behave differently to different error it received. Would you like to share the details of the sync error, please?  It could be helpful.

    Thanks


    This posting is provided "AS IS" with no warranties, and confers no rights.
    Thursday, May 13, 2010 1:35 AM
  • I would be happy to report what I can but it is somewhat limitted.

    At the start of the synch, file A1 had a modifed date of 5/6/2010, file B1 had a modified date of 4/21/2010. 4/21/2010 should have been after the switch to DST. The synch attempted to copy A1 to B1, and spent a long time doing it,  but upon completion reported it encountered an error. It said that the file was changed during the copy. I do not recall if it said if it was A1 or B1 that was changed but I assumed it was A1. In either case there was no obvious reason why either would be changed since no Outlook processes were running on A or B. I then reran the synch and watched it attempt the copy again. It completed without error and I headed out of town with computer B. It was later that I discovered B1 was the old file and I anticipated that A1 was the one that got changed which is exactly what happened. I had a backup of A1 from 5/4/2010 but two days worth of messages were lost.

    I agree that in the worst case after the copy error A1 and B1 would have the same timestamp. Is the timestamp comparison accidently less or equal rather than just less? From my end I will be sure to perform a backup before a synch and then do a preview before actually doing the synch. Better to be safe than sorry.

     

    Thursday, May 13, 2010 4:20 PM
  • I have been dealing with the DST issue and synchronizing several hard drives for several years.  My understanding is that twice a year the computer system will adjust its time stamp by 1 hour ahead or one our behind.  It was a real hassle.  Basically I would delete all my synched files from my portable hard drive and then resynch with my desktop.  The program I was using was Second Copy 2000 with my work computer and SynchToy with my home computer.  

     

    Second Copy Version 7 has been released and has a fix for the DST issue.  The text from the Second Copy website is as follows:

     

    If you are copying files from a Win9x machine across the network to or from a Windows NT machine with an NTFS file system, and you have selected the "automatically adjust for Daylight Saving Time" on the NT system, you may see some files getting recopied after a change in the daylight savings time, even though the files have not changed. 

    Windows NT/2000 adds or subtracts one hour from the NTFS file's time stamp when the files are viewed across the network from a Windows 9x system. So the files appear one hour newer or older after the daylight savings time and Second Copy recopies them. For more information on this issue see the Microsoft's knowledge base article Q129574. 

    This is caused by the way Microsoft designed the handling of daylight savings time on Windows NT/2000 systems.

    We have attemted to fix the DayLight Saving Time issue as described at the link below:

    http://www.secondcopy.com/kb/article.aspx?id=13299

     

     The fix from Second Copy was as follows:

     

    We have attempted to fix the Daylight Saving Time (DST) issue in our current version.  Make sure that you are using Second Copy 7 (build 7.1.0.3) or above.
     
    Second Copy includes a few options that are hidden from the user interface. To set these options you need to edit the profiles.dat file. Changing these options is not recommended unless you understand the implications of these changes and are familiar with editing configuration files.

    To edit the profiles.dat file:

    1. Exit Second Copy by right clicking on the icon and selecting Exit.
    2. Open the profiles.dat file in Notepad.
    3. Find the [Options] section and add the option described below. If you don't see an [Options] section you can create it at the end of the file. 

    IgnoreDST=1 

    4. Save the file.
    5. Start Second Copy again from the start menu.   

    Note: 
    profiles.dat file is a hidden file under the folder: 
    Windows 9x: "\Program Files\SecCopy" (or where Second Copy is installed) 
    Windows NT4/2000/XP/2003:"\Documents and Settings\<Username>\Local Settings\Application Data\Centered Systems\Second Copy" 
    Windows Vista: "\Users\<Username>\AppData\Local\Centered Systems\Second Copy"

    When you set this option, Second Copy will not recopy the unchanged files due to the 1-hour time difference after switching between the DST times.

     

    This works great and it worked like a charm when the time changed this spring. 

     

    I don't know if Microsoft has a similar fix for SynchToy.

     

    K

    Friday, May 14, 2010 2:27 AM
  • Thanks any way!

    I think I will need time to investigate the problem. The evidence we have is a little limited for now. I hope you have kept the log about the 2 syncing actions in question. You can get the log by SyncToy menu item "File->View Log".

    A trick is, if you do not need to sync change from B to A, you can try set sync action as Echo to avoid unexpected overwriter from B to A. (Here asume B as the right folder. )

    Sorry for making you trouble and the inconvenience.

    Thanks


    This posting is provided "AS IS" with no warranties, and confers no rights.
    Friday, May 14, 2010 10:36 AM
  • Computer A stays at home and B goes on the road. When B gets back home, its files may be the newest and I need synch to copy them to A. The goal was to have one synch "script" which always runs on A. I looked at the log information and unfortunately it doesn't say what was copied to where, just that something was copied. Had I been more observent I would have realized that A1 had been backed up to the recycle bin and I could have done a better job of piecing things back together when B got back home. Here is the data:

    -----Synch with error ----

    SYNC: 05/06/2010 09:23:40:740: SyncToy run of Mailbox (C:\Users\Margie\AppData\Local\Microsoft\Outlook\, \\MKNB\Users\Margie\AppData\Local\Microsoft\Outlook\) completed at 5/6/2010 9:23:40 AM.
    SyncToy action was 'Synchronize'.
    SyncToy options were:
     Active for run all
     All files included
     No files excluded
     Do not check file contents
     Include read-only files
     Include hidden files
     Include system files
     Backup older files (send to Recycle Bin)
     All subfolders included
    SyncToy run took 00:02:29:588.
    Copied 185,712,205 bytes in 3 files in 00:02:29:588.
    Bytes per second 1,241,485.8, files per second 0.0.
    Avoided copying 199,685,173 bytes in 59 files that did not require action.
    Saved approximately 00:02:40:844 by not copying all files.
    Warning: 1 failures occured.
    You can retry by selecting "Run" again or select "Preview" to see
    the operations that remain to be performed.

    SYNC: 05/06/2010 09:23:40:740: *** Error: The destination file has been modified during the synchronization process. Item changed unexpectedly during synchronization. Copying C:\Users\Margie\AppData\Local\Microsoft\Outlook\Margie's mailbox.pst to \\MKNB\Users\Margie\AppData\Local\Microsoft\Outlook\Margie's mailbox.pst

    --- Synch that copied in the wrong direction. Run immediately after above failure. ---

    SYNC: 05/06/2010 09:27:02:901: SyncToy run of Mailbox (C:\Users\Margie\AppData\Local\Microsoft\Outlook\, \\MKNB\Users\Margie\AppData\Local\Microsoft\Outlook\) completed at 5/6/2010 9:27:02 AM.
    SyncToy action was 'Synchronize'.
    SyncToy options were:
     Active for run all
     All files included
     No files excluded
     Do not check file contents
     Include read-only files
     Include hidden files
     Include system files
     Backup older files (send to Recycle Bin)
     All subfolders included
    SyncToy run took 00:02:20:150.
    Copied 194,290,688 bytes in 1 files in 00:02:20:150.
    Bytes per second 1,386,298.9, files per second 0.0.
    Avoided copying 191,110,670 bytes in 61 files that did not require action.
    Saved approximately 00:02:17:857 by not copying all files.

    Friday, May 14, 2010 4:12 PM
  • Thank you for sharing the log info.

    According to the error message, it looks more likely that SyncToy considered B1 as the one which had been modified during the sync process, if you were running SyncToy at machine A and the "\\MKNB" is shared by machine B.

    And glad to see backed up file in the Recycle Bin could help you.

    Thanks


    This posting is provided "AS IS" with no warranties, and confers no rights.
    Monday, May 17, 2010 1:32 AM
  • Yes, SyncToy always runs on A. I too noticed in the log that it was B1 that had changed during the synch. It occurred to me that whatever changed B1 during the sync could have caused the last modified date to have changed such that it was then newer than A1. If that wasthe case then SyncToy would have behaved properly and copied the newer B1 over A1 on the subsequent synch. The mystery remains as to what changed B1 during the synch.

     

    Monday, May 17, 2010 1:39 PM
  • I also began to have this problem recently. According to Synctoy's log, the first occurrance was on 11/13/2010. I only noticed it relatively recently, but I've been assuming the synchronization just wasn't taking place (possibly incorrectly-see below). I use a laptop when I travel, and a couple of different machines at home, and I use Synctoy to keep certain files on all machines syncronized. If I haven't used a machine in a while, I just remember to run Synctoy on the one I've been using and then on the one I've just fired up (some synchronization is done via an intermediate/master copy on one machine), before continuing. It has worked fine from the beginning...until this problem started. I know Synctoy uses some kind of "Framework". Could it be that there was an update to that "Framework" around November 2010 that Synctoy doesn't know about? In any case, if this continues, I guess I'll just have to give up on Synctoy. The only thing worse than a program that doesn't work as it should is a program that's not dependable.

    Here's this morning's error, running Synctoy on an Optiplex GX260  to synchronize with changes on a Dimension 8300. Depending on what's being backed up and why, the "left" folder could be either (remember, until mid November 2010, this worked fine):

    SYNC: 01/02/2011 13:06:32:778: -------------------------------------------------------------------------
    SYNC: 01/02/2011 13:06:32:825: Starting SyncToy, version 2.1.0.0, built 10/19/2009 3:58:16 AM.
    SYNC: 01/02/2011 13:06:49:916: Started scanning directory : \\Dimension8300\shared\Propagate\Common\
    SYNC: 01/02/2011 13:06:49:932: Started scanning directory : C:\Documents and Settings\User\My Documents\Common\
    SYNC: 01/02/2011 13:06:50:416: Stopped scanning directory : C:\Documents and Settings\User\My Documents\Common\
    SYNC: 01/02/2011 13:06:50:479: Stopped scanning directory : \\Dimension8300\shared\Propagate\Common\
    SYNC: 01/02/2011 13:06:50:979: Preview of Common (\\Dimension8300\shared\Propagate\Common\, C:\Documents and Settings\User\My Documents\Common\) in time 00:00:01:77.
    SyncToy action was 'Synchronize'
    Found 6 actions to perform.
    Found 18 files that did not require action.
    Analyzed 16.7 files per second.
    Avoided copying 3,092,688 bytes in 18 files.
    Saved approximately 00:00:06:00 by not copying any files.

    SYNC: 01/02/2011 13:06:51:151: Started scanning directory : \\Dimension8300\shared\Propagate\Desktops Plus\
    SYNC: 01/02/2011 13:06:51:151: Started scanning directory : C:\Documents and Settings\User\My Documents\My Pictures\Desktops Plus\
    SYNC: 01/02/2011 13:06:51:682: Stopped scanning directory : \\Dimension8300\shared\Propagate\Desktops Plus\
    SYNC: 01/02/2011 13:06:51:932: Stopped scanning directory : C:\Documents and Settings\User\My Documents\My Pictures\Desktops Plus\
    SYNC: 01/02/2011 13:06:52:197: Preview of Desktops & Icons (\\Dimension8300\shared\Propagate\Desktops Plus\, C:\Documents and Settings\User\My Documents\My Pictures\Desktops Plus\) in time 00:00:01:46.
    SyncToy action was 'Synchronize'
    Found 0 actions to perform.
    Found 162 files that did not require action.
    Analyzed 154.8 files per second.
    Avoided copying 282,558,510 bytes in 162 files.
    Saved approximately 00:09:25:00 by not copying any files.

    SYNC: 01/02/2011 13:06:52:400: Started scanning directory : \\Dimension8300\shared\Propagate\Favorites\
    SYNC: 01/02/2011 13:06:52:400: Started scanning directory : C:\Documents and Settings\User\My Documents\Favorites\
    SYNC: 01/02/2011 13:06:55:494: Stopped scanning directory : \\Dimension8300\shared\Propagate\Favorites\
    SYNC: 01/02/2011 13:06:57:197: Stopped scanning directory : C:\Documents and Settings\User\My Documents\Favorites\
    SYNC: 01/02/2011 13:06:58:181: Preview of Favorites (\\Dimension8300\shared\Propagate\Favorites\, C:\Documents and Settings\User\My Documents\Favorites\) in time 00:00:05:780.
    SyncToy action was 'Synchronize'
    Found 8 actions to perform.
    Found 567 files that did not require action.
    Analyzed 98.1 files per second.
    Avoided copying 389,844 bytes in 567 files.

    SYNC: 01/02/2011 13:06:58:415: Started scanning directory : \\Dimension8300\shared\Propagate\Special\
    SYNC: 01/02/2011 13:06:58:415: Started scanning directory : C:\Documents and Settings\User\My Documents\Special\
    SYNC: 01/02/2011 13:06:59:399: Stopped scanning directory : C:\Documents and Settings\User\My Documents\Special\
    SYNC: 01/02/2011 13:06:59:478: Stopped scanning directory : \\Dimension8300\shared\Propagate\Special\
    SYNC: 01/02/2011 13:07:00:384: Preview of Special (\\Dimension8300\shared\Propagate\Special\, C:\Documents and Settings\User\My Documents\Special\) in time 00:00:01:968.
    SyncToy action was 'Synchronize'
    Found 2 actions to perform.
    Found 4 files that did not require action.
    Analyzed 2.0 files per second.
    Avoided copying 1,441,082 bytes in 4 files.
    Saved approximately 00:00:02:00 by not copying any files.

    SYNC: 01/02/2011 13:07:00:774: Started scanning directory : C:\Documents and Settings\User\My Documents\
    SYNC: 01/02/2011 13:07:00:774: Started scanning directory : \\Dimension8300\shared\Transfer\Optiplex GX260\Backups\
    SYNC: 01/02/2011 13:07:28:208: Stopped scanning directory : C:\Documents and Settings\User\My Documents\
    SYNC: 01/02/2011 13:07:29:286: Stopped scanning directory : \\Dimension8300\shared\Transfer\Optiplex GX260\Backups\
    SYNC: 01/02/2011 13:07:32:005: Preview of My Documents Backup (C:\Documents and Settings\User\My Documents\, \\Dimension8300\shared\Transfer\Optiplex GX260\Backups\) in time 00:00:31:230.
    SyncToy action was 'Synchronize'
    Found 4 actions to perform.
    Found 9,428 files that did not require action.
    Analyzed 301.9 files per second.
    Avoided copying 5,997,718,253 bytes in 9,428 files.
    Saved approximately 03:19:55:00 by not copying any files.

    SYNC: 01/02/2011 13:07:32:426: Started scanning directory : C:\Documents and Settings\User\My Documents\Finance\
    SYNC: 01/02/2011 13:07:32:426: Started scanning directory : \\Dimension8300\shared\Transfer\Optiplex GX260\Backups\Finance\
    SYNC: 01/02/2011 13:07:39:207: Stopped scanning directory : C:\Documents and Settings\User\My Documents\Finance\
    SYNC: 01/02/2011 13:07:41:207: Stopped scanning directory : \\Dimension8300\shared\Transfer\Optiplex GX260\Backups\Finance\
    SYNC: 01/02/2011 13:07:43:019: Preview of Finance Backup (C:\Documents and Settings\User\My Documents\Finance\, \\Dimension8300\shared\Transfer\Optiplex GX260\Backups\Finance\) in time 00:00:10:592.
    SyncToy action was 'Synchronize'
    Found 2 actions to perform.
    Found 2,824 files that did not require action.
    Analyzed 266.6 files per second.
    Avoided copying 904,893,503 bytes in 2,824 files.
    Saved approximately 00:30:09:00 by not copying any files.

    SYNC: 01/02/2011 13:07:58:845: SyncToy run of Common (\\Dimension8300\shared\Propagate\Common\, C:\Documents and Settings\User\My Documents\Common\) completed at 1/2/2011 1:07:58 PM.
    SyncToy action was 'Synchronize'.
    SyncToy options were:
     Active for run all
     All files included
     No files excluded
     Do not check file contents
     Include read-only files
     Do not include hidden files
     Do not include system files
     Backup older files (send to Recycle Bin)
     All subfolders included
    SyncToy run took 00:00:03:405.
    Copied 1,511,936 bytes in 6 files in 00:00:03:405.
    Bytes per second 443,927.9, files per second 1.8.
    Avoided copying 3,092,688 bytes in 18 files that did not require action.
    Saved approximately 00:00:06:967 by not copying all files.

    SYNC: 01/02/2011 13:07:59:923: SyncToy run of Desktops & Icons (\\Dimension8300\shared\Propagate\Desktops Plus\, C:\Documents and Settings\User\My Documents\My Pictures\Desktops Plus\) completed at 1/2/2011 1:07:59 PM.
    SyncToy action was 'Synchronize'.
    SyncToy options were:
     Active for run all
     All files included
     No files excluded
     Do not check file contents
     Include read-only files
     Do not include hidden files
     Do not include system files
     Backup older files (send to Recycle Bin)
     All subfolders included
    SyncToy run took 00:00:00:828.
    Copied 0 bytes in 0 files in 00:00:00:828.
    Bytes per second 0.0, files per second 0.0.
    Avoided copying 282,558,510 bytes in 162 files that did not require action.
    Saved approximately 00:09:25:00 by not copying all files.

    SYNC: 01/02/2011 13:08:01:876: SyncToy run of Favorites (\\Dimension8300\shared\Propagate\Favorites\, C:\Documents and Settings\User\My Documents\Favorites\) completed at 1/2/2011 1:08:01 PM.
    SyncToy action was 'Synchronize'.
    SyncToy options were:
     Active for run all
     All files included
     No files excluded
     Do not check file contents
     Include read-only files
     Include hidden files
     Do not include system files
     Backup older files (send to Recycle Bin)
     All subfolders included
    SyncToy run took 00:00:01:906.
    Copied 3,852 bytes in 8 files in 00:00:01:906.
    Bytes per second 2,021.0, files per second 4.2.
    Avoided copying 389,844 bytes in 567 files that did not require action.
    Saved approximately 00:03:12:898 by not copying all files.

    SYNC: 01/02/2011 13:08:03:360: SyncToy run of Special (\\Dimension8300\shared\Propagate\Special\, C:\Documents and Settings\User\My Documents\Special\) completed at 1/2/2011 1:08:03 PM.
    SyncToy action was 'Synchronize'.
    SyncToy options were:
     Active for run all
     All files included
     No files excluded
     Do not check file contents
     Include read-only files
     Do not include hidden files
     Do not include system files
     Backup older files (send to Recycle Bin)
     All subfolders included
    SyncToy run took 00:00:01:312.
    Copied 1,441,157 bytes in 2 files in 00:00:01:312.
    Bytes per second 1,098,164.9, files per second 1.5.
    Avoided copying 1,441,082 bytes in 4 files that did not require action.
    Saved approximately 00:00:01:312 by not copying all files.

    SYNC: 01/02/2011 13:08:17:218: SyncToy run of My Documents Backup (C:\Documents and Settings\User\My Documents\, \\Dimension8300\shared\Transfer\Optiplex GX260\Backups\) completed at 1/2/2011 1:08:17 PM.
    SyncToy action was 'Synchronize'.
    SyncToy options were:
     Not active for run all
     All files included
     No files excluded
     Do not check file contents
     Include read-only files
     Do not include hidden files
     Do not include system files
     Backup older files (send to Recycle Bin)
     All subfolders included
    SyncToy run took 00:00:13:795.
    Copied 24,836,131 bytes in 4 files in 00:00:13:795.
    Bytes per second 1,800,357.7, files per second 0.3.
    Avoided copying 5,997,718,253 bytes in 9,428 files that did not require action.
    Saved approximately 00:55:31:404 by not copying all files.
    Warning: 2 failures occured.
    You can retry by selecting "Run" again or select "Preview" to see
    the operations that remain to be performed.

    SYNC: 01/02/2011 13:08:17:218: *** Error: The source file has been modified during the synchronization process. Item changed unexpectedly during synchronization. Copying C:\Documents and Settings\User\My Documents\Common\Logdata.xls to \\Dimension8300\shared\Transfer\Optiplex GX260\Backups\Common\Logdata.xls

    Error: The source file has been modified during the synchronization process. Item changed unexpectedly during synchronization. Copying C:\Documents and Settings\User\My Documents\Special\Events.dat to \\Dimension8300\shared\Transfer\Optiplex GX260\Backups\Special\Events.dat


    SYNC: 01/02/2011 13:08:23:420: SyncToy run of Finance Backup (C:\Documents and Settings\User\My Documents\Finance\, \\Dimension8300\shared\Transfer\Optiplex GX260\Backups\Finance\) completed at 1/2/2011 1:08:23 PM.
    SyncToy action was 'Synchronize'.
    SyncToy options were:
     Active for run all
     All files included
     No files excluded
     Do not check file contents
     Include read-only files
     Include hidden files
     Include system files
     Backup older files (send to Recycle Bin)
     All subfolders included
    SyncToy run took 00:00:06:046.
    Copied 24,772,365 bytes in 2 files in 00:00:06:46.
    Bytes per second 4,097,246.3, files per second 0.3.
    Avoided copying 904,893,503 bytes in 2,824 files that did not require action.
    Saved approximately 00:03:40:854 by not copying all files.
    Warning: 2 failures occured.
    You can retry by selecting "Run" again or select "Preview" to see
    the operations that remain to be performed.

    SYNC: 01/02/2011 13:08:23:420: *** Error: The destination file has been modified during the synchronization process. Item changed unexpectedly during synchronization. Copying \\Dimension8300\shared\Transfer\Optiplex GX260\Backups\Finance\MSMoney\Backups\MSMoney.mbf to C:\Documents and Settings\User\My Documents\Finance\MSMoney\Backups\MSMoney.mbf

    Error: The destination file has been modified during the synchronization process. Item changed unexpectedly during synchronization. Copying \\Dimension8300\shared\Transfer\Optiplex GX260\Backups\Finance\MSMoney\MSMoney.mny to C:\Documents and Settings\User\My Documents\Finance\MSMoney\MSMoney.mny

    No, MSMoney was not running on either machine, either before or during the synchronization process. After pasting the above log, I started MSMoney and looked for a transaction I know wouldn't be on this machine, and it's there; so the synchronization appears to have taken place.  Still, "appears to have" doesn't cut it with backups. Having to run WinDiff every time I use SyncToy would sort of eliminate any benefit to synchronization...

    One other thing occurred to me. The filetype of the other file that I noticed the problem with is ".dat", even though it's just a text file that's not used by a database program, and is not associated with any particular program on any of my machines (the program that uses it is a small C++ program that always knows where to find the file, and that is never started by double-clicking on its data file). I'm sure Windows will assume an ".mdf" is an Access file, and I seem to recall that trying to synchronize such a database file in a briefcase is asking for trouble (a reason I like(d?) SyncToy). TomTX's problem is also occurring with a database file ("pst"). Nowadays, database files are typically kept open 100% of the time they're in use. Is it possible that a change was made to the way Windows handles any file it thinks might be a database file, like keeping it open, or automatically opening it for use even if it's not being opened for anything but copying (which would cause the file's last access date to be changed)?

    • Edited by K.Lion Sunday, January 2, 2011 7:06 PM typo
    Sunday, January 2, 2011 7:04 PM