Hi, I have been using the program to sync about 100Gb of data (roughly 200mb of changes per day) and since the setup it has been working fine. I use the batch mode and run it silently via the task scheduler and I have ignore errors selected. My issue is according to the log the other day there was an error and it mentioned 50% of the data has changed on either side and it sat over night and deleted every file and folder??!?!?? The data sync'd perfectly the previous night so I'm not sure if it couldn't contact the one drive over the network or something but the data would have been very similar. Luckily it only did this to one of the drives, the other untouched but it's pretty BAD! If it didn't have a backup I would be in big trouble!
If there's an error message in a log there must be something that can be done about this. Is there a way to say if this 50% error appears again = do nothing, not let's wipe all the data?
Deletion of files upon comparison
- Posts: 3
- Joined: 14 May 2013
-
- Site Admin
- Posts: 7281
- Joined: 9 Dec 2007
FFS has very strict checks and precautions against (temporal) network drops, so an "ignore errors" should always be safe and never lead to the deletion of data. It's hard to say what is going on in this case, but it's easy to test FFS's behavior to various network drops on some test data by pulling the network cable, during sync, during comparison, or only temporarily during comparison, etc. None of these tests should lead to accidental data loss.
> Is there a way to say if this 50% error appears again = do nothing, not let's wipe all the data?
This would be the error handling setting "exit". But as mentioned the situation of FFS deleting files due to a temporary unavailability should not occur in first place so there is a bug somewhere (not necessarily in FFS, though: the tool is dependent from reliable error reporting of the underlying software stack, i.e. Operating system layer, drivers, etc.). BTW which version of FFS are you using?
> Is there a way to say if this 50% error appears again = do nothing, not let's wipe all the data?
This would be the error handling setting "exit". But as mentioned the situation of FFS deleting files due to a temporary unavailability should not occur in first place so there is a bug somewhere (not necessarily in FFS, though: the tool is dependent from reliable error reporting of the underlying software stack, i.e. Operating system layer, drivers, etc.). BTW which version of FFS are you using?
- Posts: 3
- Joined: 14 May 2013
Hi,
Thanks for looking into this, the version of the software is 5.3. The issue with me setting errors to be "exit instantly" is there's normally some warnings at the beginning, like unresolved conflicts for file dates and sizes mismatch, or the re-cycle bin isn't available for network drives. Will these still be ignored and my project run? Or will it just quit?
Thanks for looking into this, the version of the software is 5.3. The issue with me setting errors to be "exit instantly" is there's normally some warnings at the beginning, like unresolved conflicts for file dates and sizes mismatch, or the re-cycle bin isn't available for network drives. Will these still be ignored and my project run? Or will it just quit?
-
- Site Admin
- Posts: 7281
- Joined: 9 Dec 2007
> Or will it just quit?
It will quit.
> the version of the software is 5.3
The strict precautions against all kinds of temporary network drops were implemented not before v5.5. So an update to a more recent version will allow you to continue using "ignore", but without the risks of losing data.
It will quit.
> the version of the software is 5.3
The strict precautions against all kinds of temporary network drops were implemented not before v5.5. So an update to a more recent version will allow you to continue using "ignore", but without the risks of losing data.
- Posts: 3
- Joined: 14 May 2013
Ok that's great thank you, I'll update to a newer version.> Or will it just quit?
It will quit.
> the version of the software is 5.3
The strict precautions against all kinds of temporary network drops were implemented not before v5.5. So an update to a more recent version will allow you to continue using "ignore", but without the risks of losing data.Zenju
