BestSync Gets Confused with Backup Feature Enabled
Posted: Fri Sep 28, 2012 12:40 am
Hello Jean-Pierre,
It appears that BestSync is getting confused when I enable the Backup feature.
I setup my Bestsync tasks initially without the backup feature enabled. Then, when I was satisfied I had my tasks working properly, I modified each task to enable BestSync's backup it features. It appears that BestSync eventually becomes "confused" when the backup feature is enabled. I discovered this problem with the Backup feature after enabling Real-time syncing with one of my tasks. After discovering the problem, I turned off Real-time syncing and looked closer using BestSync's Preview Window.
When BestSync becomes confused, here are the errors I'm seeing in the "Backup" column of BestSync's Preview window:
Failed: The system cannot find the path specified
Failed: Unspecified error
On one occasion, I also saw this error in the "Result" column of BestSync's Preview window:
Failed: The process cannot access the file because it is being used by another process.
The errors are intermittent and not perfectly repeatable. When I run the Preview and the executed the sync, some files synced and were backed up, but some files generated errors. If I immediately reran the preview and executed the sync, some of the remaining files were synced and backed up, but some of the remaining files generated errors. If I repeated the Preview and Sync enough times, eventually all the files were synced and backed up.
I've included a couple of attachments that show the errors in the Bestsync Preview window. Example 1 was too big to be accepted by this forum but you can get the Example 1 from here: http://tinyurl.com/8rgyu8b
The attachment for Example 2 is attached normally below.
I've also included an attachment that shows the Backup settings that I have chosen. FYI, I made sure the backup directory is NOT included in the BestSync task's folder1 or folder2.
Perhaps this is relevant: On the "Copy Options" tab, I have chosen "Process multiple files simultaneously" and I've chosen 12 for the "Maximum thread number".
Regards,
Jeff
It appears that BestSync is getting confused when I enable the Backup feature.
I setup my Bestsync tasks initially without the backup feature enabled. Then, when I was satisfied I had my tasks working properly, I modified each task to enable BestSync's backup it features. It appears that BestSync eventually becomes "confused" when the backup feature is enabled. I discovered this problem with the Backup feature after enabling Real-time syncing with one of my tasks. After discovering the problem, I turned off Real-time syncing and looked closer using BestSync's Preview Window.
When BestSync becomes confused, here are the errors I'm seeing in the "Backup" column of BestSync's Preview window:
Failed: The system cannot find the path specified
Failed: Unspecified error
On one occasion, I also saw this error in the "Result" column of BestSync's Preview window:
Failed: The process cannot access the file because it is being used by another process.
The errors are intermittent and not perfectly repeatable. When I run the Preview and the executed the sync, some files synced and were backed up, but some files generated errors. If I immediately reran the preview and executed the sync, some of the remaining files were synced and backed up, but some of the remaining files generated errors. If I repeated the Preview and Sync enough times, eventually all the files were synced and backed up.
I've included a couple of attachments that show the errors in the Bestsync Preview window. Example 1 was too big to be accepted by this forum but you can get the Example 1 from here: http://tinyurl.com/8rgyu8b
The attachment for Example 2 is attached normally below.
I've also included an attachment that shows the Backup settings that I have chosen. FYI, I made sure the backup directory is NOT included in the BestSync task's folder1 or folder2.
Perhaps this is relevant: On the "Copy Options" tab, I have chosen "Process multiple files simultaneously" and I've chosen 12 for the "Maximum thread number".
Regards,
Jeff