Skip to main content
A backup that has never been tested is not a backup — it is a hope. Many Cambodian businesses discover the reliability of their backup strategy only at the worst possible moment: during a ransomware incident, a hardware failure, or a misconfigured update that corrupts production data. This guide gives you a practical, layered backup strategy built around the industry-standard 3-2-1 rule, paired with the specific tools and cloud storage targets that work well in the Cambodia and Southeast Asia context.

​
The 3-2-1 Rule Explained

The 3-2-1 rule is the foundational framework for resilient data protection. It defines the minimum structural requirements that ensure your backups can survive any single category of failure — hardware fault, site disaster, or ransomware encryption.

3 Copies

Maintain 3 total copies of every critical dataset: 1 production copy and 2 backup copies. If you only have 1 backup and it fails, you have nothing.

2 Media Types

Store your backups on 2 different physical media types — for example, a local server (internal disk) and a network NAS. Relying on a single media type means one hardware category failure wipes all copies.

1 Offsite Copy

Keep at least 1 copy offsite in secure cloud storage. An onsite disaster — fire, flood, theft, or power surge — cannot reach an offsite copy.
For 3CX phone systems, “critical data” includes: your 3CX configuration backup (extensions, trunks, IVR, call queues), active call recordings, voicemail messages, and the SQL database that stores CDR (call detail records).

​
Backup Architecture Overview

A well-structured backup topology for a KHCOLO cloud deployment looks like this: This three-layer structure maps directly onto the 3-2-1 rule: the live VM is copy 1, the local snapshot is copy 2, and the offsite cloud is copy 3.

​
Backup Tools

Proxmox Backup Server (PBS) is an open-source, enterprise-grade backup solution designed specifically for Proxmox VE environments. It provides deduplicated, incremental backups of KVM VMs and LXC containers.Key capabilities:
  • Incremental client-side deduplication (dramatically reduces storage usage and backup duration)
  • AES-256 encryption at rest and in transit
  • Catalogue-based restore — restore individual files or entire VMs
  • Integrated with the Proxmox VE web UI (schedule backups directly from the cluster GUI)
  • Open-source, free to use
Best for: Any organisation running Proxmox VE. PBS is the natural first choice for local and NAS-based VM backups.
Deploy PBS on a dedicated VM or physical node — never on the same host as the VMs you are backing up. If the host fails, you need to be able to recover from PBS independently.

​
Cloud Storage Targets

For your offsite copy, choose an S3-compatible object storage provider that offers competitive egress pricing and geographic proximity.
All three providers expose an S3-compatible API, which means tools like Rclone, Veeam, Proxmox Backup Server, and Acronis can write directly to any of them without custom connectors. Backblaze B2 and Wasabi offer significantly lower storage and egress costs than AWS S3 — a meaningful saving for organisations storing large volumes of call recordings.

​
Backup Schedule

A two-tier schedule — weekly full backups plus daily incrementals — balances recovery-point granularity with storage consumption.
1

Daily Incremental Snapshots (Every 24 Hours)

Run incremental VM snapshots and database exports every day during a low-traffic window (e.g., 02:00–04:00 local time). Incrementals capture only the blocks that changed since the last backup, making them fast and storage-efficient.What to back up daily:
  • VM incremental snapshot (PBS / Veeam)
  • MySQL / PostgreSQL database dump (mysqldump, pg_dump)
  • 3CX configuration export (via 3CX Management Console scheduled backup)
  • Call recordings sync to offsite S3 bucket (Rclone incremental sync)
Retention: Keep 7 daily snapshots (rolling 7-day window).
2

Weekly Full Backup (Every 7 Days)

Run a full VM backup once per week to create a clean, self-contained restore point. Full backups take longer and use more storage, but they eliminate dependency chains that can complicate incremental restore chains.What to back up weekly:
  • Full VM backup for all production servers
  • Full database dump with schema and all tables
  • Archive of call recordings for the preceding 7 days to offsite storage
  • Export of any IaC/configuration-as-code (Ansible playbooks, Terraform state)
Retention: Keep 4 weekly full backups (rolling 28-day window).
3

Monthly Archival Backup (Optional but Recommended)

For compliance, audit, or long-term recovery purposes, retain at least one monthly full backup on cold or archival storage with a retention period of 12 months or more.Storage options for archival:
  • AWS S3 Glacier Instant Retrieval
  • Backblaze B2 (lifecycle rules to cold storage)
  • Wasabi (no egress fees make retrieval cost-predictable)

​
Recovery Testing

An untested backup is not a backup. Backup files can become corrupted, storage targets can silently fail, and restore procedures can have undocumented dependencies. If you have never successfully restored from a backup, you do not know whether your backup strategy works. Schedule a restore test — to an isolated environment — at least once per quarter.
A basic quarterly restore test should verify:
  • VM restored from weekly full backup and boots cleanly
  • Database restored and passes row-count integrity check
  • 3CX configuration restored and extensions register correctly in test environment
  • Call recordings accessible and playable from restored archive
  • Document the time taken for each restore step (this becomes your RTO baseline)
Use Proxmox’s snapshot restore or Veeam’s SureBackup isolated lab feature to run recovery tests without risking your production environment. Document the result — pass or fail — in a recovery test log and share it with your IT manager or auditor.

​
Summary

For assistance configuring Proxmox Backup Server, S3 offsite sync, or a managed backup service, contact KHCOLO’s technical team. We can design and implement a backup architecture that meets your RTO/RPO targets and fits your storage budget.