DreamServer Backup
Managed Proxmox Backup Server in our Bucharest datacenter.
Slide to pick the size you need. Flat €10 per TB per month, resize online any time.
Need more than 25 TB or a custom retention? Contact sales for a custom datastore.
Three steps from order to first backup
No agent to install, no surprises. You order, we provision, you plug it into Proxmox VE.
Order online
Pick a size on the slider above and pay. Provisioning runs automatically and the datastore is live in a few minutes.
Get credentials
Your control panel in the client area shows the server address, API token, fingerprint and datastore name, ready to copy with one click.
Plug into PVE
Paste the four fields into Datacenter → Storage → Add → Proxmox Backup Server. Schedule jobs from the PVE UI like any other datastore.
Built for Proxmox VE, excellent for everything else
Four deep-dive features that make DreamServer Backup the short path between a running VM and a durable, encrypted, verifiable snapshot in our Bucharest datacenter.
Native Proxmox VE integration
Your DreamServer Backup datastore plugs straight into Proxmox VE’s built-in backup engine. Add it once from the web UI, schedule jobs like any local storage, restore whole VMs or individual files from the same interface you already use every day.
- Shows up as a regular datastore in the PVE Datacenter tree
- Uses the PVE scheduler you already use, no extra cron or agent
- A single API token and fingerprint, nothing to install on the host
- Works with containers, VMs and bare-metal hosts through the same client
Deduplication & compression
Proxmox Backup Server chunks your data at the block level and stores each unique chunk exactly once. Across daily snapshots of the same VM, the shared OS pages and static files get written once, the incremental chunks grow linearly with your actual changes, not with retention length.
- Typical 10x to 30x space savings after a few daily snapshots
- Incremental-forever: only new chunks travel the network
- Zstd compression on every chunk, stacked on top of ZFS compression
- Your retention grows without blowing up the quota
End-to-end encryption you control
If you turn on client-side encryption, every chunk is encrypted with AES-256 on your Proxmox VE host before it ever leaves your network. We only store opaque ciphertext. The key stays on your side, which means a compromised backup server cannot leak your data.
- AES-256 encryption happens on your PVE host, not on our servers
- Keys stay with you. We cannot read your backups, even if we wanted to
- Jurisdiction: Bucharest datacenter, Romania, full EU and GDPR
- Lose the key, the data is gone, no backdoor, no recovery service
Granular recovery and automatic verification
A backup only counts if you can restore it. Proxmox Backup Server runs scheduled chunk-level verification in the background so silent corruption is caught long before you actually need the backup. When recovery time comes, restore an entire VM to any PVE host, mount a snapshot as a virtual disk to browse its files, or pull out a single path through the client.
- Full VM restore back to any Proxmox VE host
- Mount a snapshot as a read-only filesystem, copy specific files
- Pinpoint file restore by pattern from the CLI
- Scheduled chunk verification catches bit rot before you need a restore
Your control panel, inside your account
Once your backup datastore is active, every detail you need to plug it in shows up in your DreamServer client area: usage charts, login credentials for the PBS web UI, an Add-Storage helper for Proxmox VE, the full proxmox-backup-client CLI guide, and a filterable list of your snapshots and tasks. Here is exactly what you see, populated with sample values.
Storage usage
Backup Count
| Groups | Snapshots | |
|---|---|---|
| CT | 12 | 168 |
| Host | 2 | 28 |
| VM | 5 | 70 |
Stats from last Garbage Collection
ZFS properties
Graphs
Web UI access
Copy the fields below into the PBS login form, then pick "Proxmox Backup authentication server" at Realm.
Add to Proxmox VE
In Proxmox VE: Datacenter → Storage → Add → Proxmox Backup Server. Fill in the fields exactly as shown in the dialog below:
The fingerprint was auto-detected. If PVE refuses to connect, copy it manually from PBS → Configuration → Certificates.
- Log into Proxmox VE as root@pam (or another user with Datacenter Admin rights).
- In the left tree click Datacenter (top node), then the Storage tab.
- Click Add and pick Proxmox Backup Server from the dropdown.
- Fill in the fields with the values above.
- Click Add. The storage shows up under the left Storage View, ready to receive backups from any VM / container.
API token credentials
Use the token for automated integration from Proxmox VE or scripts. It is not used for web login.
Use with proxmox-backup-client
All examples below use proxmox-backup-client, the official PBS Linux command-line tool. Your token and repository URL are pre-filled.
1. Install the client (one-off)
On any Debian/Ubuntu (or Proxmox VE / PBS) system, install the official package:
2. Set credentials (per session or in .bashrc)
These three env vars tell the client where to connect and which token to use. Add them to ~/.bashrc or ~/.profile for persistence:
3. First backup, a whole directory
Backs up everything in a directory (with permissions, metadata, hardlinks). The name etc.pxar is arbitrary, use anything that identifies the source.
4. Multi-source backup, several inputs in one snapshot
You can combine several directories / files / DB dumps into a single snapshot. Each source becomes one "archive" inside the snapshot.
5. Backup from stdin (e.g. database dump)
Pipe the output of any command directly into PBS, no on-disk intermediate file. Useful for big SQL dumps.
6. List snapshots and backups
See what is already stored. group = type + ID combo (e.g. host/myserver); snapshot = one point-in-time backup.
7. Restore, recover files
List the contents of a snapshot, then extract everything or just a specific file/directory.
8. Mount a snapshot, browse like a normal folder
For granular recovery: mount the snapshot as a read-only filesystem and navigate with cd, ls, copy files, etc.
9. Verify backups (integrity)
Re-reads chunks to detect corruption. Also runs automatically (see the Snapshots & Activity tab, "Verify all backups" button).
10. Prune manually (delete old backups)
Remove old backups by retention rules. Warning: irreversibly deletes, always test with --dry-run first.
11. (Optional) Client-side encryption
Data is encrypted LOCALLY before reaching PBS. Not even we (PBS admins) can read backups without the key. Generate a key once and use it for every backup. Lose the key, the data is gone forever.
Full help:
Full official documentation: https://pbs.proxmox.com/docs/
Manual actions
Trigger on-demand operations on the datastore. Each queues an async task, watch progress in "Recent activity" and in the PBS web UI.
Snapshots
| Type | ID | Last backup | Size | Verify | Protected | |
|---|---|---|---|---|---|---|
| VM | vm/100web frontend | 2026-04-24 03:17 | 11.4 GB | ✓ OK | ||
| VM | vm/101api service | 2026-04-24 03:18 | 8.2 GB | ✓ OK | ||
| VM | vm/102postgres primary | 2026-04-24 03:19 | 14.8 GB | ✓ OK | ||
| VM | vm/110accounting production | 2026-04-24 03:22 | 28.9 GB | ✓ OK | 🔒 | |
| VM | vm/120staging | 2026-04-24 03:24 | 6.1 GB | ✓ OK | ||
| CT | ct/200reverse proxy | 2026-04-24 03:25 | 3.4 GB | ✓ OK | ||
| CT | ct/201mail gateway | 2026-04-24 03:26 | 1.9 GB | ✓ OK | ||
| CT | ct/202monitoring | 2026-04-24 03:27 | 2.7 GB | ✓ OK | ||
| CT | ct/205new container | 2026-04-24 03:28 | 0.8 GB | unverified | ||
| CT | ct/210dns | 2026-04-24 03:29 | 1.2 GB | ✓ OK | 🔒 | |
| HOST | host/myserverbare-metal | 2026-04-24 04:30 | 42.1 GB | ✓ OK | 🔒 | |
| HOST | host/nasstorage node | 2026-04-24 04:32 | 19.5 GB | ✓ OK | ||
| VM | vm/100web frontend | 2026-04-23 03:17 | 11.3 GB | ✓ OK | ||
| VM | vm/101api service | 2026-04-23 03:18 | 8.1 GB | ✓ OK | ||
| VM | vm/102postgres primary | 2026-04-23 03:19 | 14.6 GB | ✓ OK | ||
| CT | ct/200reverse proxy | 2026-04-23 03:25 | 3.4 GB | ✓ OK | ||
| HOST | host/myserver-legacylegacy | 2026-04-23 04:30 | 38.4 GB | × FAILED | ||
| VM | vm/100web frontend | 2026-04-22 03:17 | 11.5 GB | ✓ OK | ||
| VM | vm/110accounting production | 2026-04-22 03:22 | 28.6 GB | ✓ OK | ||
| CT | ct/202monitoring | 2026-04-22 03:27 | 2.6 GB | ✓ OK |
Recent activity
| Task | Started | Duration | Status |
|---|---|---|---|
backup vm/110 | 2026-04-24 14:31 | - | ▶ Running |
backup ct/205 | 2026-04-24 03:28 | 0m 14s | ✓ OK |
backup ct/200 | 2026-04-24 03:25 | 1m 03s | ✓ OK |
backup vm/110 | 2026-04-24 03:22 | 4m 45s | ✓ OK |
backup vm/100 | 2026-04-24 03:17 | 4m 12s | ✓ OK |
verify svc7342:all | 2026-04-24 02:45 | 18m 21s | ✓ OK |
garbage-collection svc7342 | 2026-04-24 02:01 | 1h 17m 03s | ✓ OK |
prune svc7342 | 2026-04-24 01:50 | 0m 08s | ✓ OK |
backup host/nas | 2026-04-23 04:32 | 12m 42s | ✓ OK |
backup host/myserver-legacy | 2026-04-23 04:30 | 2m 18s | × connection reset |
verify svc7342:weekly | 2026-04-21 02:40 | 22m 06s | ✓ OK |
Pick a size and you are done
Configure the datastore, order in the client area, and we onboard you in a few days. Need custom sizing beyond 25 TB or a non-standard retention? Talk to us.
Enterprise-grade backup storage, fully managed
What you actually buy is a dedicated quota of off-site backup space on our Proxmox Backup Server (PBS), in our Bucharest datacenter. You do not rent or manage a server, you do not get an OS or root access. You get a backup datastore that you target from your existing Proxmox VE cluster, LXC containers or bare-metal Linux hosts. Deduplicated, encrypted, verifiable, with snapshot-level granularity.
You keep the keys. Client-side encryption with AES-256, deduplication across all your backups so growth stays linear with changes, not with retention. Restore a single file, a single VM or a whole datacenter with identical latency.
We operate the underlying PBS host, the storage pool, monitoring and garbage collection. That side is invisible to you. You just paste the storage credentials into Proxmox VE, schedule jobs in the PVE UI, and watch retention happen automatically.
Included
- Client-side AES-256 encryption (keys stay on your side)
- Content-defined deduplication, typical 10-30x space saving
- Incremental-forever, only changed chunks transferred
- Scheduled verify (checksum validation) by our automation
- Off-site storage: EU-jurisdiction, Bucharest datacenter
- Connectivity over DSIX peering, free for members
- We operate the PBS host, storage pool and monitoring
What you are signing up for, in plain terms
Operational targets, payment policy and data boundaries. No surprises.
Uptime target
99.9% excluding scheduled maintenance. Maintenance windows are announced in advance in the client area.
Provisioning
Automated after payment clears. Credentials and the full control panel show up in your client area within minutes, no manual setup on your side.
Non-payment policy
5-day grace period after the invoice due date. If the invoice is not paid within that window, the datastore is deleted irreversibly. Pay on time or renew early.
Redundancy & liability
Primary storage on DreamServer infrastructure with an offsite copy synced at most once per month, not a realtime replica. We are not liable for data loss, keep an independent second backup for anything critical.
Location & jurisdiction
Bucharest datacenter, Romania. EU jurisdiction, GDPR-aligned by design. Your data never leaves the EU.
Support
Ticket system inside the DreamServer client area. For pre-sales questions, use the contact page.
Questions we hear before signup
If yours is not here, ask us on the contact page.
Can you read my backups?
No, if you enable client-side encryption with proxmox-backup-client. Data is encrypted with AES-256 before leaving your machine; we only store opaque chunks and the key stays with you.
See the CLI tab, example 11, for the one-liner to set it up. Lose the key and the data is gone, we cannot recover it either.
What is the uptime target?
99.9% excluding scheduled maintenance. Maintenance windows are announced in advance in the client area so you can plan around them.
What happens if I miss a payment?
You get a 5-day grace period after the invoice due date. If the invoice is not paid within that window, the datastore is deleted irreversibly. Pay on time or renew early.
Are you liable for data loss?
No. Your backups live on DreamServer infrastructure in our Bucharest datacenter. We maintain an offsite copy synced at most once per month, not a realtime replica, so anything written since the last offsite sync would be lost if our primary copy is destroyed.
For anything business-critical, keep a second independent backup somewhere else. We are not liable for data loss.
Are there egress fees or bandwidth caps?
No. Ingress (your backup uploads) and restore traffic are included at the flat monthly price. Throughput is limited only by the physical link between you and our Bucharest datacenter.
What Proxmox VE version do I need?
Proxmox VE 8.0 or newer. For bare-metal Linux hosts, proxmox-backup-client from the official Proxmox Debian repository works on Debian 11+ and Ubuntu 22.04+.
What happens if I go over quota?
New backups that would exceed the datastore quota are refused by PBS. No surprise overage fees, no silently billing you more. Resize online from your client area and retry.
How fast do you provision?
Automated after payment clears, typically within minutes. You receive an email with a link to the control panel in your client area where credentials and all integration details are ready to copy.
Can I migrate from another PBS or backup provider?
If you are already on another Proxmox Backup Server, use proxmox-backup-client pull-sync from your old repository into the new one. Content-defined deduplication means only new chunks transfer, not a full re-upload of identical data.
What if I need more than 25 TB?
Contact us for a custom-sized datastore. The 25 TB cap is only on the self-serve slider, not on the product itself.
Can I back up containers and bare-metal Linux hosts, not just VMs?
Yes. The same datastore accepts Proxmox VE virtual machines, LXC containers, and bare-metal Linux hosts via proxmox-backup-client. You can mix all three in one account and even in one snapshot, no separate plans or extra fees.
How do I configure retention and pruning?
Retention is set on the PVE side per backup job (keep last/daily/weekly/monthly/yearly). PBS enforces it automatically: when a snapshot falls outside the rules, it gets pruned at the next garbage collection.
You can also prune manually from the CLI with proxmox-backup-client prune, and we recommend a --dry-run before any large cleanup.
Can I cancel any time?
Yes. Cancel from your DreamServer client area at any billing cycle and the datastore is released at the end of the paid period. No long-term contract, no cancellation fee. Export your backups before the end date if you want to keep them.
Do you encrypt at rest on your side as well?
Yes. The underlying ZFS pool uses native encryption, so even if a disk leaves our datacenter the data on it is unreadable. This is in addition to the optional client-side AES-256 encryption you control with your own key.
How do I rotate or revoke the API token?
From your client area you can request a token rotation; the old token is revoked and a new one is issued immediately. If you suspect an exposure, do this first, then update PBS_PASSWORD in your scripts and the storage credentials in PVE.
What backup throughput can I expect?
The bottleneck is almost always your uplink and dedup hit-rate, not us. From a Romanian ISP we typically see line-rate over the 1 to 10 Gbps link the source has. The first full backup of a VM is the slowest; daily incrementals after that are tiny because deduplication only sends new chunks.
How do I monitor backup status and get alerts?
The PBS web UI and the dashboard inside your DreamServer client area show every snapshot, verification result and recent task with its status. PVE itself can email job results on success or failure; configure it in Datacenter → Notifications.
Can I export my backups and take them elsewhere?
Yes. Use proxmox-backup-client pull-sync from another PBS instance or restore the snapshots locally with proxmox-backup-client restore. The data format is fully open, your snapshots are not locked to us.
How long does a restore take?
It depends on the snapshot size and your downstream link. With deduplication and parallel chunk fetch, restores generally run close to the line speed between you and our datacenter. A 50 GB VM over a 1 Gbps link typically lands in well under 10 minutes.
Do scheduled maintenance windows interrupt running backups?
We schedule maintenance for low-traffic windows and announce it in the client area in advance. proxmox-backup-client retries on transient errors, so a short blip during maintenance usually just delays a job rather than failing it. Long restarts pause new connections until we are back.
