After this step, you should have a nf file ready and you can use that file to list the target remote (e.g. Please follow if you don't know how to create it.

If you don't already have a Rclone config file, install Rclone on your local PC and create a Rclone configuration that connects to your remote.

Synology Hyper Backup =>(WebDAV protocol)=> Local Rclone WebDAV daemon managed by Docker =>(Sync to remote in background)=> pCloud/other cloud storages DSM can make it auto-restart and manage the lifecycle of the container for you, which is so convenient for people who don't have experience in software development. Unlike installing Rclone on DSM system itself (which requires some command line skills), Docker creates a virtual overlay filesystem and doesn't mess up with the original DSM filesystem at all.

With Docker, Rclone becomes a daemon and can be easily managed by DSM UI. Installing Rclone on DSM system would be fine but it will be removed every time after the DSM update. The easy interface and seamless integration earned the name 'The Swiss army knife of cloud storage'. Rclone is a high quality and handy tool that supports at least 50 different storage providers. Unfortunately, it doesn't work well with pCloud's WebDAV endpoint. Especially file deduplication, client encryption, and friendly task management. Synology Hyper Backup has many awesome features. I believe there are many professionals that can help you. If you have any questions, feel free to ask here. See to understand whether you can follow this instruction. And there are caveats! Also, not all Synology models support Docker. To do this, you might need to have some knowledge of Rclone and Docker. Inspired by some previous efforts related to Rclone, I managed to transform a pCloud remote to a local WebDAV target and connect it with Synology Hyper Backup.

Pcloud synology cloud sync