Syncovery Support Forum

With a paid for account the 1.4Tb backup took 18 hours not much longer than when I last saved a full backup to server. There speed test is a little odd as my up and down is 600Mb but they had the up as about 350Mb and down at 500Mb which could be allowing for what ever processing they do when ...

Not going well had pCloud running 4hrs and backed up 1.4% said was going to over 2 days. After stopping says errors with 74 files. Clearly not a very viable option like this. Spent hours with B2 and yes its complicated I have a document filled with bucket, logons, master yet another Application keys ...

Asked pCloud on settings for Syncovery and they have sent them but say its not really suitable for use in backups to them "Please note that the WebDAV protocol is mainly suitable for connecting to other applications and transferring smaller files and is not recommended for larger backups"

and
"We ...

I see Backblazee B2 as an option in creating a new backup but not the other two or am I missing something? Oh but that on V11 not on 10 running on the NAS.

Thanks a lot. John

I would be very grateful for some advice. I have a DS920+ and use Syncovery to backup to it and from it to my sons server (it used to be to my brothers as well but he died last year).
I have two problems, I am 80 and when the backup ups were done it was with my son who is knowledgeable. Thus, as ...

Thanks search for Syncovery.cfg found over 40 all dated 2020 so removed them as well

Looking at my NAS I have 2 Synonas items that are very old. Are they actually needed or for old versions of the program left behind?

\\SYNONAS\XXX\SyncoveryConfig

\\SYNONAS\XXX\SyncoveryConfig2020.zip

Problems are back. 10.4.2 has stopped displaying time as 24hr format and displays NAS time one hour slow. Schedule and its logs are using 24hr but have to be set an hour more than the time they are wanted to run. So Syncovery displays on top of bar 11.00 the schedule is set to run at 00.00 and its ...

The reset time zone must have done somthing as the schedule ran at 00:00:02. Why 02 seconds got added to when it ran is odd but not a problem. Iv moved the running time back to 23:00 and see if that works OK but looks like it should. Thanks.

YES ran at 23.00 brilant