# Where should I store server backups off-site?

> Off-site server backup storage on an S3-compatible bucket: restic, Kopia or rclone, encrypted on the server, $2.23/TB-month on 12 months, no KYC.

- URL: https://privates3.com/server-backup-storage/
- Last updated: 2026-11-17
- Publisher: PrivateS3 (https://privates3.com)

**Quick answer — Where should I store server backups off-site?**

In an S3-compatible bucket run by someone other than your server host, encrypted on the server before upload. **PrivateS3** sells such buckets from $5.40 a month for 1 TB, or $2.23/TB-month on a 12-month plan, with no API fees. Restic, Kopia, rclone and Veeam all write to it.

**In brief**

- **Off-site means another company**: a backup on the same host shares its outages and its account.
- **Encrypt on the server**: restic and Kopia do it always; rclone with `crypt`; Veeam with its backup encryption.
- **Fixed cost**: The plan size is a hard quota: an upload that would pass it is refused with a QuotaExceeded error, nothing is billed on top.
- **Limit**: Erasure-coded across disks and servers in one data center; not copied to a second region, so a second copy elsewhere is advised for data that cannot be lost.

## Which backup tool should a server use with S3?

*Server backup tools that write to an S3-compatible bucket: encryption, deduplication and the command that starts them*

| Tool | Encrypts before upload | Deduplicates | First command |
| --- | --- | --- | --- |
| [restic](https://privates3.com/restic-backup-storage/ "Where should I store restic backups?") | Always (AES-256 CTR, Poly1305-AES) | Yes | `restic -r s3:https://s3.privates3.com/BUCKET init` |
| Kopia | Always (repository password) | Yes | `kopia repository create s3 --bucket=BUCKET ...` |
| rclone | Only through a `crypt` remote | No (file sync) | `rclone sync /srv privates3:BUCKET/srv` |
| [Veeam Backup & Replication](https://privates3.com/veeam-s3-storage/ "Can I use S3-compatible storage as a Veeam repository?") | If backup encryption is turned on | Yes | New Object Storage Repository wizard |

## Why keep server backups with a different company?

**Because a backup that shares the server's host shares its failures.** A billing dispute, a suspended account, a fire or a ransomware attack that reaches the host's panel can take the server and its snapshots together. A bucket at a second company, reached with keys that live only on the server and in your password manager, survives all four.

The common 3-2-1 rule asks for three copies on two kinds of media, one off-site. A PrivateS3 bucket can be that off-site copy. It should not be the only copy. PrivateS3's storage design: Erasure-coded across disks and servers in one data center; not copied to a second region, so a second copy elsewhere is advised for data that cannot be lost.

According to PrivateS3's survey of 17 November 2026, 1 TB of S3-compatible storage costs from $6.00 a month at IDrive e2 to $23.00 at Amazon S3 Standard. The table below lists the sellers in between.

## How do you set up Kopia against a PrivateS3 bucket?

**Create an S3 repository with the bucket, the key pair and the endpoint.** Kopia's repository docs, read on 17 November 2026, say a bucket, access key and secret key are the minimum, and that S3-compatible sellers also need the endpoint and sometimes the region. The endpoint and region are shown with the keys in the client area.

*Kopia with a PrivateS3 bucket*

```bash
kopia repository create s3 \
  --bucket=BUCKET \
  --access-key=ACCESS_KEY \
  --secret-access-key=SECRET_KEY \
  --endpoint=s3.privates3.com \
  --region=eu-central-1

kopia snapshot create /etc /var/www /root/db-dumps
```

## What should a server backup include?

**Configuration, data and a database dump taken just before the backup.** Copying a running database's files can save a broken state. Dump it first (`pg_dump`, `mysqldump`) into a folder the backup tool reads, then back up that folder with `/etc`, the web roots and the home directories.

Leave out caches, logs you do not need and package folders you can reinstall. The repository size depends on how much changes each day; `restic stats` or `kopia content stats` shows the real figure after a week. The [1 TB storage page](https://privates3.com/1tb-cloud-storage/ "What can I do with 1 TB of S3 cloud storage?") shows what else fits.

## What does 1 TB of off-site backup cost?

*1 TB of S3-compatible backup storage per month and per year, read on 17 November 2026*

| Seller | 1 TB, one month | 1 TB, 12 months | Minimum retention |
| --- | --- | --- | --- |
| PrivateS3 | $5.40 | $26.77 | None |
| IDrive e2 | $6.00 | $29.75 first year, then $59.50 | None |
| Backblaze B2 | $6.95 | $83.40 | None |
| Hetzner Object Storage | $7.13 | $85.58 | None |
| Wasabi | $7.99 | $95.88 | 90 days |
| Amazon S3 Standard | $23.00 | $276.00 | None |

*Prices checked on November 17, 2026.*

## What happens if the server is hacked?

**An attacker with the server's bucket keys can delete the backups, unless the bucket is locked.** Restic's design document says plainly that restic does not protect against deletion at the storage location; the same holds for any tool.

PrivateS3 offers two answers. Object Lock (immutable backups) is set on a new bucket on request through a support ticket; locked objects cannot be deleted before their date, even with the keys. S3 versioning can be turned on per bucket from any S3 client; old versions count toward the quota. The [versioning guide](https://privates3.com/guides/how-to-turn-on-s3-versioning/ "How do I turn on S3 versioning?") shows how to turn it on with the AWS CLI or rclone.

## Server backup storage: common questions

### Can PrivateS3 read my server backups?

Not if the tool encrypts them. Without client-side encryption, the operator can technically read stored files, file names and sizes; with it, the operator sees only encrypted blobs, their sizes and upload times.

### What does PrivateS3 log about my backups?

Request logs (source IP, time, bucket, operation, bytes) are kept 14 days for abuse handling and quota accounting, then deleted.

### Is there a fee to restore a whole server?

No fee per GB. Download traffic included up to 3 times the plan size each month; above that, download speed is limited to 100 Mbit/s until the next month, never billed.

### How fast is the bucket ready?

Bucket and access keys created by a person within 24 hours of the order. Set the backup up the next day, not during an emergency.

### What happens when the plan ends?

A plan ends at the end of its period unless renewed from the balance; the bucket then turns read-only for 14 days, then it and its contents are deleted. Renew from the balance before the date to keep the backups.

**Verdict**

- **Use PrivateS3 as the off-site copy** of a server's encrypted backups: $26.77 for 1 TB over 12 months, no retention fee, paid in crypto.
- **Keep another copy** at a second region or seller if the data cannot be lost; several sellers offer multi-region options.

## Sources

1. [Repositories (Amazon S3 and S3-compatible)](https://kopia.io/docs/repositories/) — Kopia (read 17 November 2026)
2. [References: design](https://restic.readthedocs.io/en/stable/100_references.html) — restic documentation (read 17 November 2026)
3. [Preparing a new repository](https://restic.readthedocs.io/en/stable/030_preparing_a_new_repo.html) — restic documentation (read 17 November 2026)
4. [Amazon S3 Storage Providers](https://rclone.org/s3/) — rclone (read 17 November 2026)
5. [Backblaze B2 pricing](https://www.backblaze.com/cloud-storage/pricing) — Backblaze (read 17 November 2026)

**Off-site server backups for 12 months: 1 TB for $26.77** S3-compatible bucket and keys within 24 hours, paid in crypto, no ID. [Get backup storage](https://privates3.com/app/checkout/?plan=s3-1t-12m&product=storage&from=server-backup-storage&lang=en)

---

PrivateS3: PrivateS3 sells S3-compatible object storage billed per terabyte for backups and files (restic, rclone, Veeam, Cyberduck, Nextcloud), meant to be encrypted on the customer's side before upload. A terabyte costs $5.40 a month or $26.77 for 12 months, 10% under the lowest comparable offer read on 17 November 2026, with no API or egress fees up to 3 times the stored size, paid in crypto with no ID document.
