No edit summary |
No edit summary |
||
| Line 23: | Line 23: | ||
'''Notes:''' | '''Notes:''' | ||
* Make it use the community repo https://geekistheway.com/2021/03/06/how-to-setup-proxmox-backup-server-pbs-community-repository/ | * Make it use the community repo https://geekistheway.com/2021/03/06/how-to-setup-proxmox-backup-server-pbs-community-repository/ | ||
* Disks added to VM using | |||
qm set 137 -virtio1 /dev/disk/by-id/ata-TOSHIBA_MD04ACA400_761AKLZCFSAA | |||
qm set 137 -virtio2 /dev/disk/by-id/ata-TOSHIBA_MD04ACA400_761DKTFUFSAA | |||
Revision as of 11:37, 2 August 2023
Summary
Our current backup solution is running into limits. We need to rebuild this into something more usable. First decision will be to determine which plan we are going to use for this.
Architecture
We are going to use proxmox-backup as our backup solution. This means that all systems need to have the proxmox backup client. For systems that cannot run this client (eg, arm devices), we need to have an in-between system which does have the client.
There is an ARM solution https://github.com/ayufan/pve-backup-server-dockerfiles
Steps
Install PBS- Configure Erratic to backup to PBS
- Setup Proxmox Backup Client on X86 systems
- Setup Proxmox Backup Client on ARM systems
The last two steps could possibly be automated with Ansible.
Some caveats:
- Some of our systems are running Ubuntu
- Spacesound is running Fedora
Notes:
- Make it use the community repo https://geekistheway.com/2021/03/06/how-to-setup-proxmox-backup-server-pbs-community-repository/
- Disks added to VM using
qm set 137 -virtio1 /dev/disk/by-id/ata-TOSHIBA_MD04ACA400_761AKLZCFSAA qm set 137 -virtio2 /dev/disk/by-id/ata-TOSHIBA_MD04ACA400_761DKTFUFSAA