Proxmox, PBS, QNAP, and Backup Architecture
MRDTech uses layered backups: Proxmox Backup Server for VM backups, URBackup for endpoint backup, QNAP NAS units for storage targets, and restore-verification tooling so backup status is not just a green icon with delusions of adequacy.
Repository references:
- https://github.com/mdziegiel/backup-recovery-homelab
- https://github.com/mdziegiel/backup-verify
- https://github.com/mdziegiel/backup-verification-system
Core backup components
| Component | Address / location | Purpose |
|---|---|---|
| Proxmox | 10.10.10.251 | Hypervisor running production VMs |
| PBS | 10.10.10.77 | Proxmox Backup Server for VM backups/restores |
| QNAPNAS1 | 10.10.10.232 | NAS / Container Station host with media automation containers |
| QNAPNAS2 | 10.10.10.231 | NAS / Container Station host with media/library containers |
| QNAPNAS3 | 10.10.10.230 | TS-664; /PVE NFS datastore path for PBS storage |
| URBackup | 10.10.10.76:55414 | Windows endpoint image/file backup |
| Backup Verify | 10.10.10.76:10122 | Restore-confidence and backup verification dashboard |
Proxmox and PBS notes
- VM 101 was restored from PBS after filesystem corruption caused by a failed QCOW2-to-RAW conversion.
- QEMU Guest Agent is now enabled across tracked VMs for safer backup operations and filesystem freeze/thaw behavior.
- Current VM guest-agent configuration verified on Proxmox:
- VM 101 Docker:
agent: 1 - VM 103 Wazuh:
agent: enabled=1 - VM 104 Fing:
agent: enabled=1 - VM 105 HomeAssistant:
agent: enabled=1 - VM 108 Hermes:
agent: enabled=1 - VM 110 Ubuntu-Server:
agent: enabled=1
- VM 101 Docker:
- PBS datastore storage path is backed by QNAP NFS. Known restore-performance clue: PBS default
nic0is 1GbE full duplex and/mnt/datastore/PVEis NFSv3noatimeto QNAPNAS3/PVE.
QNAP storage notes
- QNAPNAS3 is a TS-664 at 10.10.10.230.
- QNAPNAS3 storage: DataVol1 ext4, HDD RAID5 using three 12.73 TB WDC disks.
- SSD cache is enabled using two Crucial CT2000P3SSD8 drives in RAID1.
- QNAP Container Station Docker daemons are exposed on TCP 2376 with mutual TLS and are now registered in Portainer:
- Endpoint 4: QNAPNAS3, 10.10.10.230
- Endpoint 5: QNAPNAS2, 10.10.10.231
- Endpoint 6: QNAPNAS1, 10.10.10.232
QNAP Container Station inventory via Portainer
| Endpoint | Containers |
|---|---|
| QNAPNAS3 | suggestarr |
| QNAPNAS2 | lidarr, navidrome, komga, tautulli |
| QNAPNAS1 | radarr, sonarr, bazarr, prowlarr, sabnzbd |
HBS3 replication
The architecture expects QNAP HBS3 replication between NAS units and/or external targets. Exact job names, schedules, and destination policies still need to be captured from the QNAP HBS3 UI/API before this page can claim a verified replication map. Pretending otherwise would be documentation malpractice.
Verification and alerting
- PBS backup failures are watched by n8n and Telegram alerting.
- Backup Verify checks backup integrity and restore confidence for URBackup data.
- Weekly infrastructure reporting summarizes backup success rate and failures.
- Backup failure alerts should identify affected VM/client, job, timestamp, and last successful restore point.