Proxmox Backup
How to Back Up Proxmox Virtual Machines to the Cloud
A practical guide to Proxmox VE backup modes, Proxmox Backup Server, incremental backups, offsite copies on S3, verification and restore tests.
Your server holds application code, configuration under /etc, user uploads, certificates and logs you may need for an investigation. Backnix is designed to copy what matters to encrypted cloud storage on a schedule, so a broken disk or a compromised machine is a recovery task, not a disaster.
RAID protects against a disk failure. It does not protect against deleted files, corrupted file systems, a failed distribution upgrade, a compromised account encrypting your data, or a provider closing your account. Snapshots taken by the same provider share the same fate as the server.
A wrong command or a bad deployment can delete or overwrite data in seconds.
Attackers who gain root access can modify or encrypt everything reachable from the server, including local backups.
A data center incident or an account problem can make the server and its local snapshots unavailable at the same time.
Without an independent backup, recovery means reinstalling the operating system, guessing configuration values, chasing old copies of certificates and asking users to upload their files again. Some data simply does not come back, and the outage lasts as long as the reconstruction.
A lightweight agent runs on the server, reads the paths you select and sends compressed, encrypted data to S3 cloud storage outside your infrastructure. After the first full backup, incremental runs transfer only what changed. Every run is recorded so you can see when the last good backup happened.
Protect /etc, /home, /var/www, /srv or any path, and exclude caches and temporary files.
Run backups hourly, daily or at the time that fits your workload.
Data is encrypted on the server before upload.
Check integrity and restore single files or complete directories.
The diagram shows the designed architecture; availability is listed below.
Backups live outside the server, the rack and the provider account that hosts it.
Incremental transfers keep daily backups small after the first run.
Keep several versions according to your retention policy and restore the one you need.
A missed or failed backup is visible instead of silently ignored.
File-level backups are ideal for configuration, application files and user data. For databases, back up a consistent dump instead of raw data files, or use the database backup option. Exclude virtual file systems such as /proc, /sys and /dev. Plan a restore procedure that includes reinstalling packages, because a file backup is not a bootable disk image. Windows Server support is planned and marked as coming soon.
File-level backup of Linux servers to encrypted cloud storage.
Backup for Windows Server, planned for a future release.
Restore single files, directories or complete systems.
Transfer only what changed after the first full backup.
Status is updated as capabilities are released. See all features.
Proxmox Backup
A practical guide to Proxmox VE backup modes, Proxmox Backup Server, incremental backups, offsite copies on S3, verification and restore tests.
Docker Backup
What Docker volumes are, why copying them from running containers can corrupt data, and safe methods to back them up and restore them.
Database Backup
Logical vs physical MySQL backups, consistent dumps with InnoDB, binary logs and point-in-time recovery, retention and restore testing.
Compare storage plans in USD or BRL. Yearly plans include 50% off the first annual payment.
Tell us what you need to protect. We will answer by email; nothing is charged.