Is there a way to stop SB from constantly wishing to rescan the FTP (target of backing up) after every slight change in directories/filter settings? This is extremely annoying to wait for a hour or so EVERY time I add some change to the Filter or Subdirs (huge website and slow connection).
It's almost impossible to fine tune the subdirs/files inclusions/exclusions rules from the first time when I see bunch of things i need to add/remove in the rules.
Using Fast Backup option (of course).
I know that the change in these rules affects the database, but SB could just scan once and store ALL folders/files locally in the fast backup data, and use that for the next comparisons.
Another question (maybe a feature request).
It would be perfect if there was an option to set so SB uses the datetime of the last Run of a backup profile (to an FTP target) as a base to detect if a file from Source was modified/added.
This will have the benefit of not needing to scan the target at all, just scan the Source and see if the Mod datetime is newer than that of the last run. Then to just copy it to FTP target. Sometimes relying on target FTP's datetime stamps is just not possible.
Example - I uploaded several thousands files website to a server in another country (timezone) in a ZIP and decompressed it there, and the site is live.
It turned out all file times were 8 hours off. Windows Server.
Now SB is totally confused and offers me to upload all the files to the FTP. After a day i didn't find an option to overcome this. After googling I found a little tool I used to touch all the files and their datetimes to subtract 8 hours from their corresponding timestamps.
If SB could just detect modified files locally, I wouldn't have needed to do all this in the first place, and wasting all day.
SB is most close to my needs and I would be very happy to have this program with these things fixed.
It's almost impossible to fine tune the subdirs/files inclusions/exclusions rules from the first time when I see bunch of things i need to add/remove in the rules.
Using Fast Backup option (of course).
I know that the change in these rules affects the database, but SB could just scan once and store ALL folders/files locally in the fast backup data, and use that for the next comparisons.
Another question (maybe a feature request).
It would be perfect if there was an option to set so SB uses the datetime of the last Run of a backup profile (to an FTP target) as a base to detect if a file from Source was modified/added.
This will have the benefit of not needing to scan the target at all, just scan the Source and see if the Mod datetime is newer than that of the last run. Then to just copy it to FTP target. Sometimes relying on target FTP's datetime stamps is just not possible.
Example - I uploaded several thousands files website to a server in another country (timezone) in a ZIP and decompressed it there, and the site is live.
It turned out all file times were 8 hours off. Windows Server.
Now SB is totally confused and offers me to upload all the files to the FTP. After a day i didn't find an option to overcome this. After googling I found a little tool I used to touch all the files and their datetimes to subtract 8 hours from their corresponding timestamps.
If SB could just detect modified files locally, I wouldn't have needed to do all this in the first place, and wasting all day.
SB is most close to my needs and I would be very happy to have this program with these things fixed.