Storage VPS: how to build reliable storage on a server with a large disk
A storage VPS is a server where what matters is neither the CPU nor the memory but the size of the disk. People take one to keep backups from other servers, hold the team's files, a media library or an archive. Buying a lot of gigabytes is easy; it is harder to understand how well they are protected and what will happen to the data if a disk in the host's node fails.
What a storage VPS is used for
- Remote backups. Copies of production servers, databases and websites that are kept in another data centre and won't disappear together with the main machine. The scenario is described in detail on the VPS for backups page.
- Your own file cloud. Nextcloud or Seafile for a team: document sync, sharing, calendars. The requirements for such a server are covered in the VPS for Nextcloud selection.
- A media library and archive: company photos and videos, webinar recordings, project sources that you don't want to delete and that are inconvenient to keep locally.
- Storage for applications through an S3-compatible server such as MinIO or Garage, when a cloud object store costs more.
Choose where to place the storage by two rules. First, not in the same data centre as the main server, or an outage or fire will destroy both copies. Second, take the law into account: if the backups contain personal data of Russian citizens, Russia's personal data law (Federal Law No. 152-FZ) requires the primary database to be located in Russia, so it is more convenient to keep such storage with a Russian host. More on the requirements on the VPS for 152-FZ page. Ping hardly matters for storage; a stable connection matters more.
The host's RAID and what it really guarantees
Almost all hosts build a node's disks into RAID, most often RAID 10 or RAID 6. This protects against the failure of one or two disks: the server keeps running while an engineer replaces the broken one. But RAID does not protect against deleted files, a bug in a script, ransomware, a file system failure or problems with the whole node. And most importantly, most plans state plainly in the contract that the host does not guarantee the safety of customer data, and backups remain your responsibility.
Before buying, find out three things: which RAID level is used, whether the host makes its own copies of customers' disks and at what price, and what the service level agreement promises in case of data loss. If the answer is "we make no copies", that is normal for budget storage; just build the protection yourself.
A snapshot is not yet a backup
A snapshot in the host's panel captures the state of the disk at the moment it is created and lets you roll back quickly after a failed update. But it is usually kept in the same storage system as the disk itself. If the account, the node or the array is lost, the snapshots disappear along with the data. A real backup lies elsewhere and with another provider.
A practical rule is 3-2-1: three copies of the data, on two different media or in two systems, one of them in another location. A storage VPS is perfect for the role of that remote copy, but it should not itself remain the only instance of an important archive.
A snapshot is useful before risky actions: a system upgrade, a database migration, a Nextcloud version change. Take it, check the result and delete it when it is no longer needed. Many hosts limit the number of snapshots or charge for them by size, and on some storage systems a long-lived snapshot slows down disk writes.
How to set up storage you can trust
- Encrypt on the client side. restic and BorgBackup encrypt data before sending it, so even with access to the disk an outsider will see only encrypted blocks. Keep the key separately from the server.
- Use deduplication. The same restic and Borg store repeated blocks once, and daily backups take up a fraction of the full volume.
- Block deletion from the source. If the server sending the backups is compromised, the attacker must not be able to erase the archive. For this there is the append-only mode in Borg, separate access keys and immutable buckets in S3-compatible servers.
- Calculate the traffic. The first full upload of several hundred gigabytes can eat up a monthly allowance. For storage, unlimited traffic or a large allowance is more convenient.
- Test restores. Once a month, restore a random set of files or a whole database to a test machine. A backup that has never been restored is a hope, not a copy.
Most plans in this selection run on hard disks, so they are good for storage but not for a database or an active website. How to measure disk speed and tell a normal HDD array from an overloaded one is described on the VPS on HDD page.