Private mCloud Architecture: Secure Data Storage & the 3-2-1 Backup Strategy

· 5 min read

Secure data management is a top priority for every developer. Commercial cloud providers often impose rising subscription costs and bandwidth limits. Deploying a self-hosted private cloud gives you complete sovereignty over your data.

1. The 3-2-1 Backup Architecture

Data durability in mCloud follows the industry-standard 3-2-1 engineering rule:

2. End-to-End Encryption & Data Sovereignty

All transfers are encrypted in transit using TLS 1.3 with Perfect Forward Secrecy, and accessed via key-authenticated SFTP or high-entropy REST API tokens.

3. Automated Backup Script with Zstandard Compression

The following Bash script creates an atomic snapshot, compresses it multi-threaded usingzstdand syncs it to an off-site vault:

#!/usr/bin/env bash
set -euo pipefail

BACKUP_DIR="/var/backups/mcloud"
TIMESTAMP=$(date +"%Y%m%d_%H%M%S")
ARCHIVE_NAME="mcloud_backup_${TIMESTAMP}.tar.zst"
REMOTE_HOST="backup-node.mermiko.com"
REMOTE_DIR="/mnt/storage/vault"

mkdir -p "$BACKUP_DIR"

echo "[$(date)] Rozpoczynanie tworzenia kopii zapasowej..."
tar -cf - /var/www/mcloud | zstd -T0 -3 -o "${BACKUP_DIR}/${ARCHIVE_NAME}"

echo "[$(date)] Przesyłanie do bezpiecznego węzła off-site..."
rsync -avz -e "ssh -i /root/.ssh/backup_key" "${BACKUP_DIR}/${ARCHIVE_NAME}" "backupuser@${REMOTE_HOST}:${REMOTE_DIR}/"

# Retencja: zachowaj tylko kopie z ostatnich 14 dni
find "$BACKUP_DIR" -type f -name "*.tar.zst" -mtime +14 -delete
echo "[$(date)] Kopia zapasowa zakończona pomyślnie."

4. Integrity Verification & Disaster Recovery Drills

Backups are only as good as their restore process. mCloud periodically spins up an isolated verification container to validate SHA-256 checksums and database schema integrity.

Also read