Is an HDD storage VPS fast enough for backups and Nextcloud?

Why is an HDD storage VPS fast enough for backups?

Backups write big pieces of data in order, which is the one thing hard disks do well. Modern backup tools do not copy your files one by one to the server. restic cuts files into blobs of 512 KiB to 8 MiB and bundles them into pack files; Borg appends its chunks to segment files on the repository. The disk therefore sees a stream of large writes, and after the first full run only the changed chunks travel.

The tighter limit is usually the network. A Coffervale server has a 1 Gbit/s port and a monthly traffic quota (4 TB a month on the 1 TB plan); past the quota the port drops to 100 Mbit/s until the next period, with nothing extra billed. Seed a large first backup early in the period and the nightly increments are small change.

One job does feel the hard disks: verification. borg check --verify-data reads, decrypts and decompresses every chunk, and Borg's own manual calls it "very time consuming"; restic check --read-data downloads every pack file, which also counts against the server's traffic quota when it runs from your own machine. Run full checks weekly or monthly, or spread them with restic check --read-data-subset=1/4 and a different slice each time. The whole routine, from first upload to restore test, is in how do I use a storage VPS for off-site backups?

Is an HDD storage VPS fast enough for Nextcloud?

For files, yes; for the web interface, it depends on how much of the small stuff you keep in memory. Uploading, syncing and downloading files are sequential jobs. What makes Nextcloud feel slow is the database, file locking, thumbnails and background jobs, all of them small random reads and writes.

Nextcloud's own administration manual points at the fixes, and each one moves load off the disk:

• Memory caching with APCu, and Redis for transactional file locking, which by default runs through the database.
• MariaDB or PostgreSQL rather than SQLite, which the manual recommends only for testing and minimal instances.
• Background jobs by cron, so maintenance does not run inside page loads.
• Enough RAM: at least 512 MB per process is recommended, and heavy swapping "can severely degrade performance".

With that in place, a household or a small team on a plan with 4 GB RAM or more works without drama. A Nextcloud for many users with office editing belongs on flash, with its files or backups on the storage VPS. Plan sizes for Nextcloud are weighed in what is the best VPS for Nextcloud with 1 TB or more of storage?

What does a shared hard-disk array mean for my VPS?

Your disk space is yours alone; the speed of the array is shared with every other server on the same host. When neighbours run their own backups at 02:00, everyone's throughput drops for a while. Hosts manage this in different ways, and few write it down.

According to Coffervale's survey of 2 November 2026, only 1 of the 18 storage VPS sellers that take crypto and ask no ID published a disk speed limit (Senko Digital: reads and writes capped at 150 MB/s), 2 named an NVMe cache in front of the hard disks (Hostbrr, AlphaVPS), and 5 sold a small NVMe system disk next to a separate data disk (Hostbrr, Senko Digital, NolimitHost, DeluxHost, PrivateAlps). BuyVM reaches the same layout by attaching a storage slab to an NVMe slice.

Coffervale gives no figure: Every plan stores your data on hard disks (HDD) chosen for capacity, not speed: they suit backups, archives and file sync, not databases or heavy random reads and writes. We publish no speed or IOPS figure we cannot back.

Why does an NVMe system disk next to an HDD data disk help?

It puts the small, random work on flash and the big, sequential work on hard disk, each where it runs best. The operating system, packages, the database, Redis and preview caches live on the NVMe disk; the backup repository or the Nextcloud data directory lives on the HDD. Nextcloud's manual makes the same point for virtual machines: give the database its own block device rather than a file inside the VM's disk image.

On a server where everything sits on hard disks, as on a Coffervale plan, you get most of the benefit from memory instead: give the database a buffer pool that holds its working set, keep Redis in RAM, and leave the disk to the files. That is why the larger plans carry more RAM as well as more disk.

How much more does an SSD storage VPS cost per TB?

SSD storage cost three to six times the HDD median per terabyte on 2 November 2026. Contabo, the one large mainstream host in our survey that sells a "Storage VPS", built its line on SSD only, from 300 GB to 1.4 TB. Flash is the right call when the workload is random; for terabytes of backups and files, it is paying for speed the job does not use.

How can I measure the disk of my own storage VPS?

Run fio on the data disk at a few different hours and read the spread, not one number. The three tests below mirror a backup upload, a restore and a database-style random read. --direct=1 skips the page cache, so you measure the disks and not your RAM. Expect large sequential figures and modest random ones: that gap is what a hard-disk array looks like.

# Run on the mounted data disk (here /srv); the test file is removed at the end.
cd /srv || exit 1
# Large sequential write: the pattern of a backup upload
fio --name=seqwrite --filename=fio.test --size=4G --rw=write --bs=1M --direct=1 --ioengine=libaio --iodepth=8
# Large sequential read: the pattern of a restore
fio --name=seqread --filename=fio.test --size=4G --rw=read --bs=1M --direct=1 --ioengine=libaio --iodepth=8
# Small random reads: the pattern of a database or a file index
fio --name=randread --filename=fio.test --size=4G --rw=randread --bs=4k --direct=1 --ioengine=libaio --iodepth=16 --runtime=60 --time_based
rm -f fio.test

What should not go on an HDD storage VPS?

Anything that waits on thousands of small disk operations a second. That means a database taking writes all day, a search engine index, a mail server with large busy mailboxes, or virtual machine images that boot and swap. Each of these is a regular VPS job, as set out in storage VPS or regular VPS: which one do I need?

Everything that moves in large pieces stays: backup repositories, file sync, photo and video archives, exports, mirrors of your own data. For the definition of the product itself, read what is a storage VPS?