Author |
Message |
jy3sonet
Joined: 09 May 2008 Posts: 5
|
Posted: Fri May 09, 2008 5:39 pm Post subject: Causing file conflicts and corruption |
|
|
Currently use ViceVersa PRO2 and VVEngine to schedule Synchronization of 2 folder directories over a VPN between 2 sites. I use size and timestamp for comparison.
Each time that this is ran, I have 3 file conflicts. The timestamps on the 3 files change to 2/1/1982 and are corrupt and unreadable.
I manually restore the files with the correct timestamp and they are readable until the next time that the file sync runs and again, they get corrupted.
I don't know what is causing, both Source and Target servers are time sync together on a domain and out of another 100 or so files, these are the only ones that being affected? |
|
Back to top |
|
|
jy3sonet
Joined: 09 May 2008 Posts: 5
|
Posted: Fri May 09, 2008 5:42 pm Post subject: Another note |
|
|
I do want to note that I have done chkdsk on the disk volumes and have found no problems with the NTFS file structure. |
|
Back to top |
|
|
jy3sonet
Joined: 09 May 2008 Posts: 5
|
Posted: Sat May 10, 2008 1:40 am Post subject: I may of resolved my own problem |
|
|
I reset the tracking database, deleted the files in the target that were corrupt and been changed with a timestamp of 1982.
I then performed a manual syncronization with VVEngine and it automatically removed the files from the source.
I restored the files to the source from a backup copy, and initialized another manual synchronization and it correctly copied the files back to the target.
So right now things are working good but I still can't explain how the files became corrupt in the first place with a timestamp of 2/1/1982? All workstations are in sync and current with the time of their domain controllers, there are no disk errors, and I have found no network errors either locally or thru our VPN to our branch office? |
|
Back to top |
|
|
|