Object Storage vs Local Disk for Backups on a $5 VPS: Cost Per GB Math

A $5 VPS with 25 GB of disk feels like enough until you start keeping backups on it. Backups grow, retention grows with them, and the same disk that holds your database is the one that fails. The usual upgrade path is a bigger local plan at $15, but object storage is often cheaper per gigabyte and survives a disk failure. This is a unit-cost comparison: dollars per GB stored, per GB restored, and per month retained, for a $5 plan plus B2, R2 or S3 versus a $15 plan with more local disk.

The unit costs, side by side

Object storage bills on three axes: storage per GB-month, requests, and egress. Local disk bills once as part of the plan, then includes whatever bandwidth the plan allows. That difference matters, because local disk looks free after purchase while object storage keeps charging monthly. The comparison only makes sense when both are modelled over 12 months at the same retention size and restore frequency.

OptionStorage $/GB-moEgress $/GBMin monthly25 GB for a year
B2$0.006$0.01 (3x free daily)~$1.10$1.80
R2$0.015$0$0 (free tier)$4.50
S3 Standard$0.023$0.09~$0.58$6.90
Local disk add-onn/a (plan)included$0plan cost

For 25 GB of backups, B2 costs about $1.80 per year in storage, R2 about $4.50, S3 about $6.90. A $15 local plan instead of a $5 local plan costs $120 more per year. Object storage is one to two orders of magnitude cheaper for the same bytes, which is why the decision usually favors object storage on storage cost alone. The catch is on the restore side.

The egress trap on restore

Storage is cheap; getting data back is where budgets break. S3 charges $0.09 per GB egress. Restoring a 25 GB backup once costs $2.25, which is fine, but restoring weekly costs $117 per year, more than the storage. B2 includes free egress up to three times your average stored data per day, which covers most restore patterns. R2 has no egress fees at all, which is why it is popular for backup targets served back to the VPS.

The subtle part is that a restore is not one download. You usually pull a full snapshot, then an incremental, then verify. A 25 GB full plus a few GB of incrementals can push 30 GB in one restore. If your provider bills egress and you restore twice a year, budget $5-6, not zero. Model restores as an annual line item, not as an emergency that does not count.

Retention rotation changes the storage number

Backups do not stay at one size; retention multiplies them. A simple 7-daily, 4-weekly, 12-monthly scheme keeps about 23 restore points. If each monthly full is 25 GB and weeklies are incrementals, retained storage can land around 3-5x the current data size. So 25 GB of live data may mean 90-120 GB of retained backups, and the object storage bill scales with the retained figure, not the live one.

This is where local disk breaks down faster than object storage. A 25 GB plan cannot hold a 5x retention set, so the local option immediately becomes a larger plan. Object storage at 120 GB on B2 costs about $8.64 per year; on R2 about $21.60. Both are still far below the $120 annual difference between a $5 and $15 plan, and neither competes with your database for IOPS.

Request costs: the number people forget

Storage and egress get the attention, but requests are billed too. B2 charges $0.004 per 10,000 class B calls beyond a free allowance; S3 charges about $0.0004 per PUT. A nightly backup writing 500 chunks costs cents, not dollars. Request fees only matter for tools that poll thousands of times a day.

Check your tool’s request pattern, not its storage volume. A sync job that lists the repository every hour racks up calls, while a nightly tar to one object is a handful of PUTs. If your provider charges per request, batch small files into one archive, because 10,000 tiny objects cost more in requests than in stored bytes.

Worked comparison: $5 plus object storage vs $15 plan

Consider a 40 GB site with a 12 GB database, retained backups of 80 GB, one full restore per year at 40 GB, and normal VPS traffic of 300 GB per month. The $5 plan plus B2 keeps the database on local NVMe and ships nightly dumps to the bucket. The $15 plan doubles local disk to 80 GB and keeps two snapshots on the provider’s storage, but a disk failure still takes the server with it.

Line item$5 + B2$15 plan
VPS monthly$5.00$15.00
Object storage 80 GB$0.48$0.00
Restore egress (annual)$0.40$0.00
Yearly VPS cost$60.00$180.00
Yearly storage + egress$6.16$0.00 (included)
12-month total$66.16$180.00

The $5 plus object storage combination is under $70 for the year against $180 for the larger plan, and it survives a full disk failure because the backups live outside the server. The $15 plan is only justified if you need the extra CPU or RAM for the workload itself, not for storage. Buying a bigger server to hold backups is the most common over spend in this category.

When the $15 plan is the right call

There are real cases for local disk. A backup target on the same provider, restored over a private network, avoids egress entirely and is fast. Workloads that write and read large media continuously need local IOPS, not object storage latency. And if your total data is under 15 GB with a one-week retention, the simplicity of keeping two snapshots on the plan can beat wiring up a bucket and credentials.

The decision rule is simple: if the larger plan is bought for storage, object storage wins on cost almost every time; if it is bought for CPU, RAM or IOPS, buy the larger plan and still send backups offsite. Mixing the two goals into one purchase is how budgets drift upward without improving reliability. Separate compute from backup storage and each decision gets easier.

Practical guardrails before you commit

  • Measure retained backup size, not live data size, before choosing storage.
  • Model one or two full restores per year as an egress line item.
  • Check egress pricing: free tiers differ from zero-fee providers.
  • Keep the database on local NVMe and back it up, rather than running it on object storage.
  • Test a restore quarterly; untested backups are only a storage bill.

When you compare plans, check the entry tiers at affordablevpsserver.com and price the backup side separately before upgrading for disk. The VPS plans page lists local storage per tier, which makes the add-on math concrete. The cheapest reliable setup is often the smaller server plus a bucket, not the larger all-in-one plan.

Object storage wins on storage cost, loses on egress if you restore often, and wins decisively once retention multiplies. A $5 plan with 80 GB of retained backups on B2 costs about $66 a year; a $15 plan costs $180 and still has no offsite copy. Model storage, egress and retention separately, and the smaller server plus a bucket usually wins.

Affordable-Vps-Server-Author
Affordable-Vps-Server-Author
Articles: 434

Leave a Reply