A quick note: The features covered in this article are currently in beta. We’re still fine-tuning them.
If you’re managing a NAS backup, you already know that it can be one of the most frustrating things ever. I mean, it can take well over a week. That’s probably longer than your last vacation. Meanwhile, local cache files clog up your PC during large uploads. And there’s no proper one-way sync. Sound familiar?
At pCloud, we built our platform to support reliable NAS backups for anyone running a serious amount of data. Alongside our desktop and web apps, we have four classic, battle-tested tools: rsync, WebDAV, SFTP, and SCP. They’ve been the backbone of professional backup workflows for decades. And once you know what each one does, they can transform how you back up your NAS to the cloud.
The Challenges
NAS backup has some unique demands that go beyond what typical cloud sync tools are designed for. Here’s what to keep in mind:
📦 Local caching is part of the upload process. When you upload files by drag-and-drop, pCloud temporarily stores a cache copy on your computer’s drive to keep the file available during upload. This is standard behaviour for most desktop sync clients. For NAS-scale data, it’s worth knowing this cache will use disk space and some processing power while the upload is running. The good news: it clears automatically the moment the upload finishes.
📦 Large file sizes need the right approach. NAS backups often include files in the 17GB–30GB range or larger. These sizes call for an upload workflow built specifically to handle them smoothly, rather than a general-purpose one.
📦 One-way backup takes a bit of setup. The desktop app doesn’t currently have a single-click “one-way backup” toggle built in. However, as we’ll show below, it’s easy to set up a reliable one-way workflow with the right configuration.
📦 Efficient re-uploads matter at scale. Some backup tools re-upload your entire NAS every time a backup runs. That works fine for a small folder, but for a NAS with terabytes of data, it’s worth choosing a setup that avoids re-uploading unchanged files. Otherwise backup jobs can stretch well over a week.
This is exactly why NAS admins pair pCloud with the following setup for a smooth, scalable NAS backup workflow.
NAS Backup Cheat Sheet
| Tool | Best for NAS backup | Key benefit |
|---|---|---|
| rsync | Ongoing, scheduled NAS backup | Only transfers changes; a fast, incremental, one-way sync |
| WebDAV | Mounting pCloud as a network drive | No commands needed, works through your NAS’s built-in interface |
| SFTP | Interactive browsing and transfers | Secure, works with almost any NAS |
| SCP | Quick, scripted, one-off jobs | Simple “copy from A to B” syntax |
Think of these as four different ways to move files between your NAS and pCloud. They drop neatly into automated scripts, so you can schedule your backup to run on its own with whatever cadence fits your setup. For those of you who are security conscious (who isn’t?), note that the rsync, SFTP, and SCP transfer of files is via SSH, meaning your data is protected.
✔️rsync
Running an actual, recurring, don’t-make-me-think-about-it NAS backup? rsync, every time.
This is the one most NAS admins come to rely on. Unlike a full re-upload, rsync compares what’s already stored on pCloud and transfers only what’s changed. For NAS backup, that means:
✅️ Incremental backups. After your first full backup, every future run only sends the differences. This cuts a multi-day NAS backup job down to minutes.
✅️ Your folder structure stays intact. rsync preserves your NAS’s local file and folder structure exactly, so what’s on your NAS matches what’s on pCloud. However, file permissions are normalised by pCloud.
✅️ True one-way sync, direct to pCloud. You can set up one-way synchronisation straight from your NAS to pCloud.
rsync -av --no-specials --no-devices --no-links --no-times -e ssh <local-folder>/ "<email>"@rsync.pcloud.com:/<destination-folder>/
or, connecting to the rsync module, this is what NAS backup apps such as Synology Hyper Backup and QNAP HBS use:
rsync -av --no-specials --no-devices --no-links --no-times -e ssh <local-folder>/ "<email>"@rsync.pcloud.com::upload/<destination-folder>/
Same rule applies: your pCloud account password is all you need to authenticate. Use ersync.pcloud.com for EU accounts.
✔️ WebDAV
Your NAS interface only offers a “mount as network drive” or “add remote storage” option, and nothing else? WebDAV is your way in.
A lot of NAS boxes already have WebDAV support built into their interface. Instead of running a command, you simply point your NAS’s WebDAV client at pCloud’s WebDAV address, and pCloud shows up as just another network drive your NAS can read from and write to. It’s the most accessible option if your NAS admin panel is entirely point-and-click. Also, it pairs especially well with NAS backup tools that expect a mapped network location rather than a command-line target.
WebDAV is the plug-and-play option. rsync/SFTP/SCP are more like the power-user tools you’d use in a terminal, while WebDAV is more like “type in an address, hit connect, done.”
It won’t give you the smart, incremental, changes-only transfers that rsync does. Thus, it’s not the best fit for huge, frequently-changing datasets.
✔️ SFTP
Need to grab a few things and browse like it’s a remote drive? Use SFTP.
SFTP (SSH File Transfer Protocol) is a secure, command-line way to connect to your pCloud account and transfer files, directory by directory. It’s ideal for a NAS that doesn’t run a full desktop app but does support SFTP.
sftp "<email>"@sftp.pcloud.com
sftp "<email>"@esftp.pcloud.com
Your password is simply your pCloud account password. Many NAS devices support SFTP natively, so it’s one of the easiest ways to connect your NAS to pCloud for backup.
✔️ SCP
Writing a script that fires off once and copies a folder? Go for SCP.
SCP (Secure Copy) copies files from one machine to another, securely, over a network or the internet. If SFTP is like browsing a remote drive, SCP is a straightforward “copy this here” command. It’s great for scripted, one-off NAS backup jobs.
scp -r <local-folder> "<email>"@sftp.pcloud.com:/<destination-folder>/
scp -r <local-folder> "<email>"@esftp.pcloud.com:/<destination-folder>/
Run man scp to see all available options. It’s a lightweight way to push a NAS folder up to pCloud in a single command.
What You’ll Need to Set Up NAS Backup
For any of these tools, you’ll need:
- Your pCloud account email and password.
- The relevant server address for your account (similar in spirit to
webdav.pcloud.com, but specific to SFTP/SCP/rsync access).
Because every NAS brand has its own interface, the exact configuration steps for NAS backup will vary from device to device. If you already know how to configure rsync, SFTP, or WebDAV on your NAS, you’re most of the way there.
