2 questions on realtimesync and automatic backup

[jimhaley]

I want to set up automatic backup of multiple USB drives. Assuming I use RealTimeSync:

1. I am scared that in the event of a corrupt USB drive, if I plug it in, it will delete my backup in the event of a two-way sync if I use [USB_NAME] and keep the batch file on the desktop. Is this a valid concern (i.e. will the corrupted drive be treated as its files being deleted if it's not accessible because it's corrupted)? If so, does that mean that the alternative of using relative names and instead keep the batch file on the USB to be run automatically by RealTimeSync a better idea because if the .ffs_batch file from the USB is detected, it most likely means the drive is not corrupted and if the drive is corrupted, then RealTimeSync won't be able to run the batch file because of that?

2. Do I have to have a separate RealTimeSync instance for each USB drive I want to backup? I have a lot of them and it would be better if I can simplify things by combining them together (perhaps it's a more efficient use of system resources this way as well). If I can't, does that mean I will need to have to create multiple services (one for each .ffs_real file)? Anyway to simplify what I'm trying to accomplish further?

[Zenju]

1. FFS won't delete files as a result of a failed read access on the source side. Only if the folder traversal is successful (= it didn't return any errors), FFS will assume an empty source directory. This doesn't change even if you have selected to ignore all errors. (ignoring errors is designed to never cause accidental data loss, but only skip the current action)

2. You'll need on RTS instance per FFS sync job.