We installed Syncovery on a Synology NAS (RS822RP+) to synchronise with a SSH/SFTP server, specifically a Hetzner Storage box operated by a supplier.
As background, the same NAS has been using Synology’s own CloudSync tool to sync data to an existing Shared Drive / folder, which I have left in place. Basically I wanted to leave the existing folder configured with CloudSync while creating a new folder to use with Syncovery.
After installing the package and configuring SSL access, I created a new Shared Drive on the NAS and gave the Syncovery user full control, and then configured a profile.
I placed the NAS folder on the left and the Hetzner storage box on the right (SSH/SFTP profile) and configured the profile to only copy right-to-left. I also configured a single top-level folder on the right-side for sync. I ran the profile, which completed successfully.
As a next step I created a second profile, this time copying the contents of the existing Shared Folder (that uses the Synology CloudSync tool) to the Shared Folder configured with the SSH profile (basically avoiding copying all 0.6TB of data again over the Internet). This profile completed successfully.
After this we then tried re-running the first profile, synching from the Hetzner Storage box. I made a small change to sync all directories over SSH and re-ran the profile. It almost immediately failed with a retry message, eventually displaying this error:
Access problem (IncompleteExt empty, Checkpoints: CIAIIFX@0000000000C0E22B)
After various other checks, I realised that this error applied with the HDD to HDD sync profile and indeed any new profile I created. I initially thought the permissions allowing the Syncovery user had been over-written, but this was not the case.
Problems with new install
Re: Problems with new install
Hello,
thanks for your post! Apparently you don't get our emails, so we can use the forum to communicate. Maybe you can check your spam filters, mail system etc. Our emails can come from support@syncovery.com, info@syncovery.com as well as tobiasgiesen@gmail.com.
Which Syncovery version do you have?
In any case, problems are usually analyzed by looking at log files. You can use the "Log Files" button to access them. Please share log files with errors. You can send them to support@syncovery.com and I can reply and also post a possible solution here.
thanks for your post! Apparently you don't get our emails, so we can use the forum to communicate. Maybe you can check your spam filters, mail system etc. Our emails can come from support@syncovery.com, info@syncovery.com as well as tobiasgiesen@gmail.com.
Which Syncovery version do you have?
In any case, problems are usually analyzed by looking at log files. You can use the "Log Files" button to access them. Please share log files with errors. You can send them to support@syncovery.com and I can reply and also post a possible solution here.
Re: Problems with new install
Hi Tobias,
Thanks very much, most weird we're not getting replies back!!
The plugin version installed is 10.15.10.
Thanks,
Chris
Thanks very much, most weird we're not getting replies back!!
The plugin version installed is 10.15.10.
Thanks,
Chris
Re: Problems with new install
Hi,
many thanks. I really need a log file to analyze the problem. You can use the "Log Files" button to access them. Please share log files with errors. You can send them to support@syncovery.com and I can reply and also post a possible solution here.
I will also try to send you another reply from the support address.
I will release a Linux update today or tomorrow, if there is anything to fix I would really like to include it in this update. But the screenshots are not sufficient for finding the problem.
Thanks!
many thanks. I really need a log file to analyze the problem. You can use the "Log Files" button to access them. Please share log files with errors. You can send them to support@syncovery.com and I can reply and also post a possible solution here.
I will also try to send you another reply from the support address.
I will release a Linux update today or tomorrow, if there is anything to fix I would really like to include it in this update. But the screenshots are not sufficient for finding the problem.
Thanks!