Feature requests
Ugly: Implement checksum comparison failback option. To use checksum comparison if filesystem monitor fails for unknown reason (for example, when files sources OS rebooted during updates) to prevent FULL many many many TBs remirroring and reuploading. Allow to configure to use remote services for remote checksum computation in failback mode.
Speed: Implement multithreaded checksum comparison. Hint: use remote services workers on local machine and allow using it on both left and right sides even on local machine.
Thank you.
Feature Request: checksum comparison failback option if filesystem monitor fails & multithreads
Re: Feature Request: checksum comparison failback option if filesystem monitor fails & multithreads
Hello,
thanks, I will consider these for Syncovery 10!
thanks, I will consider these for Syncovery 10!
Re: Feature Request: checksum comparison failback option if filesystem monitor fails & multithreads
Hi again, Tobias!
After visiting customer that is actually using v9 I wanted to come back here and check for a progress with my requests.
Surprisely there is v10 available for some time, but I didn’t found clear announcement of failback and multithreading options in a v10 New Features page.
May be I missed something and these options are already built-in into v10 as you wrote before (for example using another feature naming)?
After visiting customer that is actually using v9 I wanted to come back here and check for a progress with my requests.
Surprisely there is v10 available for some time, but I didn’t found clear announcement of failback and multithreading options in a v10 New Features page.
May be I missed something and these options are already built-in into v10 as you wrote before (for example using another feature naming)?