Help get this topic noticed by sharing it on Twitter, Facebook, or email.

Excessive disk wear when detecting changes on source directory

Detecting changes on source directory by the desktop client causes much reads resulting in excessive disk wear. And excessive reading time. I have around 9GB backed up in your cloud.

This only happens, obviously, if I close the program and re-open again a time later.

I don't wan't to keep the program running for security reasons, for example, a ransomware attack could encrypt my local files and their mirror in the cloud as well.

Note I use the backup feature only. Not file sync at all.

Just fyi, this backup program, Bvckup 2 ( utilizes a feature called "destination snapshot". You could implement "source snapshot" or something alike to reduce hdd/ssd wear.
1 person likes
this idea