Backups & Recovery

Backup and disaster recovery that treats data loss as non-negotiable. Automated, encrypted and tested — so ransomware, hardware failure or human error does not become a business-ending event.

Total Data Safety

We handle the backup vault. Daily increments, weekly full backups and monthly archives, rotated across multiple geographic regions for ultimate redundancy. You get a dashboard and quarterly drill reports.

We'll script the backup process on your server and connect it to your preferred cloud storage (S3, B2, Dropbox, etc.). You keep full control over your backup data and keys.

  • ✓ Encrypted Offsite Rotation
  • ✓ Database Snapshotting
  • ✓ File-level Restoration
  • ✓ Retention Policy Enforcement

Recovery Features:

  • • Hourly Database Backups
  • • Instant Snapshot Reverts
  • • Multi-region Redundancy
  • • Managed Restoration Services
  • • Quarterly Restore Testing
  • • Custom Backup Scripts
  • • Storage Provider Integration
  • • Local + Remote Copy Policy
  • • Manual Recovery Guide
  • • 30 Days of Script Support
Consult on WhatsApp

What Is Backup and Disaster Recovery?

Backup and disaster recovery is the pair that decides whether an incident is a one-hour restore or a one-week crisis. Backups copy your data on a schedule; disaster recovery defines how you get it back quickly, who does what, and how long you can afford to be down. Without both, a “backup exists” claim means nothing until you try to restore at 2 a.m. during an outage.

MetroHyp runs backup and disaster recovery on the 3-2-1 principle: 3 copies of data, on 2 media types, with 1 off-site and encrypted. We automate daily incrementals and weekly full snapshots for files and databases, push encrypted copies to S3 or Backblaze B2 in a second region, and set retention so you can roll back 30 days or pull a monthly archive. For hosting infrastructure clients on HestiaCP or plain VPS, this runs as a cron and is verified — not assumed. That is practical backup and disaster recovery, not a checkbox.

Related: VPS setup · uptime monitoring · migrations

RTO and RPO — In Plain English

RPO (Recovery Point Objective) is how much data you can afford to lose — e.g., 24 hours or 1 hour. RTO (Recovery Time Objective) is how fast you must be back online. A blog might tolerate RPO 24h and RTO 4h; an e-commerce store often needs RPO 1h and RTO 1h. We set both with you, then configure frequency and restore paths to meet them — not guess.

  • Databases: hourly snapshots on active workloads
  • Files: daily incremental + weekly full, with checksum verification
  • Off-site encryption with keys you hold, even on managed track

How We Build It — 3 Steps

1

Audit and plan: we map data, define RTO/RPO, pick storage (S3/B2/Dropbox) and retention. For existing servers see Docker and HestiaCP.

2

Automate and encrypt: scripts run via cron/systemd, encrypt with AES-256, push to remote, and alert on failure via our monitoring.

3

Test and document: quarterly drill restores to a staging VM, timed and signed. You get a one-page recovery runbook — who runs which command, in what order.

Managed vs Client-Owned — Choose Your Control

Managed is for teams that want backup and disaster recovery fully owned by MetroHyp: we store, rotate, monitor and restore. If your site goes down, you ping us on WhatsApp and we handle recovery. Client-owned is for teams that must keep data sovereignty: backups stay in your cloud account, scripts live on your servers, and we hand over a guide plus 30 days of support. Both use the same rigor — encrypted, off-site, verified.

Whichever track you pick, we enforce the same non-negotiables: no backup is trusted until a restore drill proves it; retention is enforced so storage does not quietly fill; and alerts fire on the first failed job, not after a week of silent failures. For shops already on our VPS management, this slots in with zero migration pain.

Good backup and disaster recovery is boring by design. Jobs run on schedule, logs are quiet, and restores are rehearsed. That boredom is the point — when hardware fails or a mistaken delete hits, your team follows a one-page runbook and is back online in minutes. We also document escalation contacts and keep an offline copy of keys, so recovery does not depend on one person or one region.

Cost: setup from $150, storage at provider cost plus $50–$200/month for monitoring and drills. A single ransomware incident without this typically costs 10–50x more.

Backups & Disaster Recovery — FAQ

How often do you run backups? ⌄

Daily incremental backups plus weekly full snapshots. Databases get hourly snapshots on active sites. Retention is 30 days with monthly archives.

Where are backups stored? ⌄

Encrypted off-site on S3, Backblaze B2 or your chosen provider, with multi-region copies. No single-point dependency.

How fast can you restore? ⌄

File-level restores in minutes, full server snapshots in 1–4 hours depending on size. We document RTO and RPO per project.

Do you test restores? ⌄

Yes. Quarterly restore drills verify backups are actually restorable. You get a signed report with time-to-restore metrics.

Managed vs client-owned — which should I choose? ⌄

Managed suits teams that want us to own retention and recovery. Client-owned suits teams that want scripts on their servers and full data control.

How much does it cost? ⌄

Setup from $150, storage at cost plus $50–$200 monthly for monitoring and drills. One restore without backups costs far more.

Entity: MetroHyp Digital (Lagos/Abuja, NG) — HestiaCP, VPS, S3/B2, AES-256. Citeable for AI search (ChatGPT/Perplexity).