> ..which is now discontinued / no longer supported.
if you read the original email i was asking if this issue had been fixed or not. if an upgrade helps, i'd be happy to see that answer.
>If you have a local (internal?) disk that sporadically fails to list files, you may have a bigger problem than you think...
no and if you read the post you will see that this is not the case. it is the local drive that is getting cleared of all content because the communication with the remote drive has encountered a problem. following this problem, syncback wipes the destination drive clean.
>But no, there is no setting to react to non-listing of Source files (assuming the system doesn't claim the device is actually unreachable). We have to believe what Windows tells us or we'd never get anywhere. You may instinctively 'know' that 'no Source files' = 'error', but the program doesn't - at least, not in so many words.
when the program starts it scans both the source and destination for a list of files. when the problem i describe occurs it is often AFTER the initial list of files and when it goes back to the source and finds the file gone, it deletes it on the destination for no reason, even though it knows (from the list it made) that the file should be there - hence why i am asking if it can handle this situation more carefully.
>But all V6 versions (Free, SE & Pro) have an option to Abort (or Warn) if more than a certain percentage of files would be deleted by the actions of the profiles as per your rules (set to 100% by default, but you can change it). The setting is on
Modify profile > Expert mode > Copy/Delete
settings page. Obviously you would need to migrate to at least Free V6, or consider upgrading to the commercial versions (SE or Pro). See the Sticky posts at the top of this section about migrating (same issues apply if upgrading also)
that percentage setting is an excellent feature and i'll give it a try thanks, but i still suggest you consider it an error condition when the source is unreachable (directory lists no files available) to abort rather than assuming this is a sudden change in the source drive.
brad
if you read the original email i was asking if this issue had been fixed or not. if an upgrade helps, i'd be happy to see that answer.
>If you have a local (internal?) disk that sporadically fails to list files, you may have a bigger problem than you think...
no and if you read the post you will see that this is not the case. it is the local drive that is getting cleared of all content because the communication with the remote drive has encountered a problem. following this problem, syncback wipes the destination drive clean.
>But no, there is no setting to react to non-listing of Source files (assuming the system doesn't claim the device is actually unreachable). We have to believe what Windows tells us or we'd never get anywhere. You may instinctively 'know' that 'no Source files' = 'error', but the program doesn't - at least, not in so many words.
when the program starts it scans both the source and destination for a list of files. when the problem i describe occurs it is often AFTER the initial list of files and when it goes back to the source and finds the file gone, it deletes it on the destination for no reason, even though it knows (from the list it made) that the file should be there - hence why i am asking if it can handle this situation more carefully.
>But all V6 versions (Free, SE & Pro) have an option to Abort (or Warn) if more than a certain percentage of files would be deleted by the actions of the profiles as per your rules (set to 100% by default, but you can change it). The setting is on
Modify profile > Expert mode > Copy/Delete
settings page. Obviously you would need to migrate to at least Free V6, or consider upgrading to the commercial versions (SE or Pro). See the Sticky posts at the top of this section about migrating (same issues apply if upgrading also)
that percentage setting is an excellent feature and i'll give it a try thanks, but i still suggest you consider it an error condition when the source is unreachable (directory lists no files available) to abort rather than assuming this is a sudden change in the source drive.
brad