Continuing with my early bird top secret announcements, November advent's calendar style.
I built an artsy backup tool for Proxmox VE.
https://github.com/norandom/restic-pve
Alpha, of course. It's new.
Conceptually this is like a full-scale backup console. You do (live) guest backups. Via Prox (API, fleecing, roles etc.)
On the inside it is a modern backup system, inspired by Veeam.
restic-pve uses Restic for block based differentials, and Proxmox's fleecing for performance (even on spin disks). It uses Rclone for the file transfers, and it is shipped as a self-contained Go binary (to a Prox host).
You can use Google Drive, S3 etc.. Or SFTP. Your choice. As long as Rclone supports the backend.
restic-pve is load-aware, and slows down based on the Prox machine status. It will not choke Proxmox hosts. It wll not saturate your bandwidth. It will not kill itself.
It is getting simplified and streamlined to include backup plans, retention definitions and restore tests. Compliance style.
Backups are of course encrypted, and transferred via TLS.
But restic-pve features a retro-style DOS era progress bar and menu.
restic-pve allows full automation (schedules, OpenTelemetry endpoint etc).
Defrag and chill becomes backup and chill now. Because backups save the day, when shit hits the fan.
All it needs:
* self-updating Go binary on the Proxmox host (root for now, but you can use a backup user)
* slim Docker container on the host (VM not LXC because Docker in LXC is too slow)
If the Ransomware comes 2027, because time to patch goals were missed maybe, restic-pve will have your back.
#restic #proxmox #golang #retrocomputing #opentelemetry #automation #backups #earlygifts #infosec #admin-tools #security
I built an artsy backup tool for Proxmox VE.
https://github.com/norandom/restic-pve
Alpha, of course. It's new.
Conceptually this is like a full-scale backup console. You do (live) guest backups. Via Prox (API, fleecing, roles etc.)
On the inside it is a modern backup system, inspired by Veeam.
restic-pve uses Restic for block based differentials, and Proxmox's fleecing for performance (even on spin disks). It uses Rclone for the file transfers, and it is shipped as a self-contained Go binary (to a Prox host).
You can use Google Drive, S3 etc.. Or SFTP. Your choice. As long as Rclone supports the backend.
restic-pve is load-aware, and slows down based on the Prox machine status. It will not choke Proxmox hosts. It wll not saturate your bandwidth. It will not kill itself.
It is getting simplified and streamlined to include backup plans, retention definitions and restore tests. Compliance style.
Backups are of course encrypted, and transferred via TLS.
But restic-pve features a retro-style DOS era progress bar and menu.
restic-pve allows full automation (schedules, OpenTelemetry endpoint etc).
Defrag and chill becomes backup and chill now. Because backups save the day, when shit hits the fan.
All it needs:
* self-updating Go binary on the Proxmox host (root for now, but you can use a backup user)
* slim Docker container on the host (VM not LXC because Docker in LXC is too slow)
If the Ransomware comes 2027, because time to patch goals were missed maybe, restic-pve will have your back.
#restic #proxmox #golang #retrocomputing #opentelemetry #automation #backups #earlygifts #infosec #admin-tools #security