PBS Backups & Replication
Proxmox Backup Server instances, IPs, VLAN 90 allocation, and the cross-site replication strategy for disaster recovery.
Each site runs Proxmox Backup Server (PBS) for local VM backups and cross-site disaster-recovery replication. PBS-A serves Site A and PBS-B serves Site B; neither site is the sole backup target.
No Stretched Ceph: Use PBS Replication for Cross-Site DR
Site B Ceph stays local to Site B. Do not stretch Ceph across sites. Cross-site disaster recovery uses PBS replication, not stretched Ceph.
PBS Instances
Each PBS instance has two network interfaces: a management interface on VLAN 30 (VM Services) and a backup-data interface on VLAN 90 (Backup / Replication).
| Instance | Site | Mgmt IP (VLAN 30) | Backup-data IP (VLAN 90) |
|---|---|---|---|
| PBS-A | Site A | 10.10.30.20 | 10.10.90.40 |
| PBS-B | Site B | 10.20.30.20 | 10.20.90.40 |
PBS-A runs on sa-stor-01 (the Supermicro 5049A-T), co-located with ZFS storage, the Site A DNS VMs (sa-dns-01 / sa-dns-02), monitoring, and core infrastructure VMs. PBS-B runs as a service VM within the sb-pve cluster; the specific Proxmox node that hosts the PBS-B VM is not pinned in the current design.
VLAN 90: Backup / Replication
Backup and replication traffic flows on VLAN 90, separate from management (VLAN 20), Corosync (VLAN 25), and general VM services (VLAN 30).
| VLAN | Name | Site A | Site B |
|---|---|---|---|
| 90 | Backup / Replication | 10.10.90.0/24 | 10.20.90.0/24 |
The .40 address within each /24 is reserved for the PBS backup-data interface (10.10.90.40 for PBS-A, 10.20.90.40 for PBS-B). This follows the address-block convention: .40-.49 is the band for infrastructure service VMs.
Backup Strategy
Both PBS instances run local backups at their own site. PBS data is replicated cross-site for disaster recovery so that a full site failure does not result in complete data loss.
- Run local backups at each site independently.
- Replicate PBS data cross-site for disaster recovery.
- Do not rely on one site for all backups.
Local-First Backup
Each PBS instance operates locally within its site. Local backup jobs continue regardless of the inter-site WireGuard tunnel state.
The cross-site PBS replication path uses the WireGuard tunnel (10.255.0.0/24) that connects sa-fw-01 and sb-fw-01. See WireGuard for tunnel configuration.
Operating Contract
The source design fixes the failure boundary and traffic path without claiming an implementation schedule that has not been chosen.
| Area | Decided posture |
|---|---|
| Local operation | Each site runs backups to its local PBS instance; a WireGuard outage does not stop local backup jobs. |
| Cross-site DR | PBS data is replicated between sites so neither location is the only recovery copy. |
| Network path | Backup data uses routed VLAN 90 and crosses the site-to-site WireGuard tunnel. |
| Storage boundary | Site B Ceph remains site-local; PBS replication is the cross-site protection mechanism. |
| PBS-A placement | PBS-A runs on sa-stor-01. |
| PBS-B placement | PBS-B is a service VM in sb-pve; its specific Proxmox host is not pinned. |
Open Operating Decisions
Backup Policy Is Not Yet Complete
The architecture sources do not define retention, prune or garbage-collection cadence, synchronization schedule or direction, datastore encryption and credentials, recovery objectives, or restore-test frequency. These remain open design work rather than implicit defaults.
| Open item | Current status |
|---|---|
| Retention policy | No keep-last/daily/weekly/monthly values are decided. |
| Prune and garbage collection | No cadence or maintenance window is decided. |
| Cross-site synchronization | Replication is required; job direction, order, bandwidth window, and retry policy are not specified. |
| Credentials and encryption | The authentication, key custody, and datastore encryption procedure is not specified. |
| RPO / RTO | No recovery-point or recovery-time objective is committed. |
| Restore verification | No recurring restore-test procedure or evidence cadence is committed. |
| PBS-B host and datastore | The service VM address is reserved, but its hosting node and backing datastore are not pinned. |
Related Pages
- Proxmox Clusters: cluster setup and node membership
- Site A ZFS: ZFS mirror vdevs on
sa-stor-01 - Site B Ceph: local Ceph cluster within
sb-pve - VLAN Reference: full VLAN table including VLAN 90
- WireGuard: inter-site tunnel used for cross-site replication
Site B Ceph Storage
Site B Ceph plan: five-node cluster across FN8TP and FN4T hardware, replication size 3, public (VLAN 60) and cluster (VLAN 65) network split, Micron drive recommendations, and Proxmox pveceph deployment.
Kubernetes / OpenShift
Status and navigation hub for the site-local Kubernetes and OpenShift plan, including locked network allocations and still-tentative platform choices.