Skip to content

Nuface Blog

้šจๆ„้šจๆ‰‹่จ˜ Casual Notes

Menu
  • Home
  • About
  • Services
  • Blog
  • Contact
  • Privacy Policy
  • Login
Menu

Proxmox Backup Server in Multi-Site Redundancy and Automation Design

Posted on 2025-11-032025-11-03 by Rico

๐Ÿ”ฐ Introduction

As enterprise IT infrastructures evolve toward multi-site distribution and hybrid cloud environments,
maintaining data consistency across locations and ensuring rapid recovery in case of disaster
has become a mission-critical requirement.

Beyond its role as a local backup solution,
Proxmox Backup Server (PBS) can serve as the foundation for multi-site data resilience.
Through its built-in Sync Jobs, Remote Datastore Replication, and REST API automation,
PBS enables a complete, scalable, and automated Disaster Recovery (DR) framework
that ensures business continuity and long-term data reliability.


๐Ÿงฉ 1. Typical Multi-Site Architecture

Architecture Overview

             โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”
             โ”‚     Site A (Primary Site)     โ”‚
             โ”‚ Proxmox VE + PBS + ZFS/NVMe   โ”‚
             โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜
                            โ”‚  Incremental Sync
                            โ”‚
             โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ดโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”
             โ”‚     Site B (DR / Secondary)   โ”‚
             โ”‚ PBS + Ceph Object Storage     โ”‚
             โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜
                            โ”‚
               Optional Cloud Tier Replication
                            โ”‚
             โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ดโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”
             โ”‚     Site C (Cloud Archive)    โ”‚
             โ”‚ S3 / Wasabi / B2 / GCP / Azureโ”‚
             โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜

Three-Tier Model

1๏ธโƒฃ Primary Site (A) โ€” Production workloads and local PBS backups
2๏ธโƒฃ DR Site (B) โ€” Receives incremental PBS replication and supports failover
3๏ธโƒฃ Cloud Tier (C) โ€” Long-term archiving and offsite retention


โš™๏ธ 2. Core Mechanism: PBS Sync Job

At the heart of PBS multi-site synchronization lies the Sync Job,
which performs incremental data replication between independent PBS servers.

Key Features

  • Transfers only new data chunks (incremental)
  • Supports compression and encrypted transport
  • Allows automatic scheduling and retry policies
  • Integrates with Verify Jobs for integrity validation

Example Sync Job Configuration

proxmox-backup-manager sync-job create \
--id sync-to-dr \
--source local-pbs \
--remote dr-pbs@192.168.10.20:8007 \
--store pbs-remote \
--schedule "daily"

๐Ÿ“ฆ This ensures the DR site always maintains up-to-date backup copies with minimal bandwidth usage.


๐Ÿง  3. Cross-Site Verification and Data Consistency

To ensure remote data integrity,
PBS can combine Sync Jobs and Verify Jobs to execute a complete โ€œReplicate โ†’ Verify โ†’ Reportโ€ cycle.

Automated Workflow

1๏ธโƒฃ Daily Incremental Sync โ€” Transfers new data chunks
2๏ธโƒฃ Weekly Verification โ€” Recomputes checksums and detects corruption
3๏ธโƒฃ Automated Reporting โ€” Sends results via API or email

Verify Job Example

proxmox-backup-manager verify start --store pbs-remote --all --jobs 4

โœ… If inconsistencies are found, PBS flags the affected chunks and queues them for re-sync.


โ˜๏ธ 4. Integrating with Cloud Object Storage

To achieve true offsite durability,
PBS can be extended with rclone or s3cmd to replicate data to public or private cloud storage platforms
such as AWS S3, Wasabi, Backblaze B2, or Google Cloud Storage.

Example: PBS โ†’ Ceph RGW โ†’ S3 Cloud Tier

rclone sync /mnt/datastore/pbs-remote ceph-s3:cloud-archive

Benefits:

  • Three-layer protection (Local โ†’ DR โ†’ Cloud)
  • Automated archival and versioning
  • Integrated retention and lifecycle management

๐Ÿงฎ 5. Automated Failover and Restore Design

A. Automated Failover (Trigger-Based)

By integrating monitoring tools like Prometheus and Alertmanager,
you can automatically trigger DR operations when the primary PBS becomes unavailable:

  1. Switch Proxmox VE cluster backup target to DR PBS
  2. Enable write access on the DR datastore
  3. Notify administrators via webhook or email

B. Automated Restore via PBS API

PBS provides a full RESTful API for programmatic restores and re-deployments:

curl -k -X POST \
https://dr-pbs:8007/api2/json/admin/datastore/pbs-remote/restore \
-d "backup-type=vm&backup-id=vm-101&target=/mnt/vmrestore"

You can integrate this with Ansible, N8N, or Python automation scripts
to fully automate recovery or re-attach VM disks after a disaster.


๐Ÿ”„ 6. Task Scheduling and Automation

Use systemd timers or cron jobs to orchestrate recurring maintenance tasks.

TaskFrequencyDescription
Sync JobDailyIncremental replication
Verify JobWeeklyData integrity check
Prune JobMonthlyCleanup of expired snapshots
Report JobWeeklyGenerate and email backup summary

Example Automation Script

#!/bin/bash
proxmox-backup-manager sync-job run --id sync-to-dr
proxmox-backup-manager verify start --store pbs-remote --all
proxmox-backup-manager prune start --all

๐Ÿ“Š 7. Monitoring and Observability

1๏ธโƒฃ Built-in Logging

  • View task results under /var/log/proxmox-backup/
  • PBS Web UI displays Sync and Verify progress in real time

2๏ธโƒฃ External Monitoring Integration

Integrate Prometheus + Grafana + Wazuh for unified observability:

  • Prometheus: collects PBS metrics (task duration, throughput, errors)
  • Grafana: visualizes multi-site sync status dashboards
  • Wazuh: provides audit logs, login tracking, and data change alerts

โœ… With this setup, PBS becomes not just a โ€œbackup server,โ€
but an observable and intelligent data protection platform.


๐Ÿงฉ 8. Real-World Deployment Scenarios

Enterprise SetupImplementationRedundancy Level
Taipei HQ + Shanghai BranchSite A: ZFS + PBS; Site B: PBS + CephDual-site replication
Taiwan HQ + Vietnam Plant + GCP CloudAโ†’B replication, Bโ†’C cloud archivalThree-tier protection
On-Prem + DR IDCSync + Verify + Ansible-based failoverAutomated DR
SME Single-SitePBS + rclone to S3Cloud redundancy

โœ… Conclusion

Proxmox Backup Server (PBS) has evolved far beyond a traditional local backup tool.
It now serves as a central component in enterprise-grade multi-site DR and automation frameworks.

Through:

  • Incremental Sync Jobs for efficient cross-site replication
  • Automated Verify and Repair cycles for data integrity
  • REST API automation for instant restores
  • Cloud-tier archival integration

Organizations can achieve a truly modern data strategy characterized by:

Multi-Site Redundancy ยท Automated Recovery ยท Verified Integrity ยท Cloud Governance

๐Ÿ’ฌ Coming next:
โ€œAutomated Backup Orchestration with PBS + N8N + Ansibleโ€ โ€”
demonstrating how to integrate Proxmox Backup Server APIs
for fully automated synchronization, verification, restoration, and reporting workflows.

Recent Posts

  • Postfix + Letโ€™s Encrypt + BIND9 + DANE Fully Automated TLSA Update Guide
  • Postfix + Letโ€™s Encrypt + BIND9 + DANE TLSA ๆŒ‡็ด‹่‡ชๅ‹•ๆ›ดๆ–ฐๅฎŒๆ•ดๆ•™ๅญธ
  • Deploying DANE in Postfix
  • ๅฆ‚ไฝ•ๅœจ Postfix ไธญ้ƒจ็ฝฒ DANE
  • DANE: DNSSEC-Based TLS Protection

Recent Comments

  1. Building a Complete Enterprise-Grade Mail System (Overview) - Nuface Blog on High Availability Architecture, Failover, GeoDNS, Monitoring, and Email Abuse Automation (SOAR)
  2. Building a Complete Enterprise-Grade Mail System (Overview) - Nuface Blog on MariaDB + PostfixAdmin: The Core of Virtual Domain & Mailbox Management
  3. Building a Complete Enterprise-Grade Mail System (Overview) - Nuface Blog on Daily Operations, Monitoring, and Performance Tuning for an Enterprise Mail System
  4. Building a Complete Enterprise-Grade Mail System (Overview) - Nuface Blog on Final Chapter: Complete Troubleshooting Guide & Frequently Asked Questions (FAQ)
  5. Building a Complete Enterprise-Grade Mail System (Overview) - Nuface Blog on Network Architecture, DNS Configuration, TLS Design, and Postfix/Dovecot SNI Explained

Archives

  • December 2025
  • November 2025
  • October 2025

Categories

  • AI
  • Apache
  • Cybersecurity
  • Database
  • DNS
  • Docker
  • Fail2Ban
  • FileSystem
  • Firewall
  • Linux
  • LLM
  • Mail
  • N8N
  • OpenLdap
  • OPNsense
  • PHP
  • QoS
  • Samba
  • Switch
  • Virtualization
  • VPN
  • WordPress
© 2025 Nuface Blog | Powered by Superbs Personal Blog theme