Managed Backup

Backup that's actually tested , not just running

Most backup scripts run fine — until you need them. Studies consistently show a 50%+ restore failure rate on untested backups. ZenoCloud runs automated daily backups with monthly restore verification on every managed server. 3-2-1 architecture, AES-256 encryption, India DC off-site storage for DPDP compliance.

Add Backup to Your Plan See Disaster Recovery

Monthly restore testing — not assumed 3-2-1 backup architecture AES-256 encryption at rest + in transit India DC storage — DPDP compliant 1,000+ servers under management

Running production workloads for

Monthly

Restore Verification

3-2-1

Backup Architecture

AES-256

Encryption Standard

60 days

Max Retention (Enterprise)

1,000+

Servers Under Management

What ZenoCloud managed backup covers

Daily automated backups are table stakes. What separates a working backup strategy from a false sense of security is testing, architecture, and off-site redundancy.

3-2-1 backup architecture

3 copies of your data, on 2 different storage media, with 1 stored off-site. Primary backup on ZenoCloud backup server in a separate DC, secondary on S3-compatible object storage. The 3-2-1 rule is the industry standard — Veeam and Rubrik both recommend it. We implement it by default.

Monthly restore verification

Every month, we perform an actual restore test on a sample of backup data — not a checksum check, an actual file and database restore. We record restore time, verify data integrity, and flag any issues. This is the differentiator: most managed backup services don't test. We do.

AES-256 encryption

All backup data is encrypted at rest with AES-256 and in transit with TLS 1.3. Encryption keys are managed separately from backup data. Backup storage in India by default — DPDP Act compliance requires personal data to remain in India.

Full-stack backup coverage

Files (web root, application files, user-uploaded content), databases (MySQL/PostgreSQL — dump + binary log for point-in-time recovery), configuration (Nginx/Apache config, cron jobs, SSL certificates), and application state (Redis snapshots for session-critical apps).

Configurable retention

7 daily, 4 weekly, 3 monthly snapshots by default. Configurable up to 60-day retention on Enterprise plans. Point-in-time recovery available for databases with binary log backup. Retention policy documented for SOC 2 and ISO 27001 evidence.

Disaster recovery integration

Managed backup pairs naturally with Disaster Recovery planning. DR without backup is a plan with nothing to restore from. See /resilience/disaster-recovery/ for RTO/RPO planning — backup is the data foundation, DR is the operational process built on top of it.

Pricing

Managed backup pricing

Backup is included at every managed hosting tier. The pricing below applies to backup-as-a-service add-ons for custom server configurations and standalone backup engagements.

Standard Backup

/month

Automated daily backups with off-site storage for one server

Daily automated backup (files + DB)
7 daily, 4 weekly, 3 monthly retention
Off-site object storage (India DC)
AES-256 encryption
Backup failure alerting
Quarterly restore test

Add Backup

Managed backup vs backup scripts vs cloud-native backup

A cron job running rsync is not the same as a managed backup service. A cloud-native backup (AWS Backup, RDS snapshots) is good for cloud resources but doesn't cover your full stack.

Feature	DIY backup scripts / cron	ZenoCloud Managed Backup
Automated daily execution
Off-site secondary storage	Manual setup required
AES-256 encryption at rest	Depends on implementation
Monthly restore testing
Alert on backup failure	Manual — usually nobody notices
Database binary log backup	Depends on implementation
India DC off-site storage	Depends on where S3 bucket is
Compliance documentation
One-click restore support	Manual restoration required

DIY backup scripts / cron

ZenoCloud Managed Backup

Automated daily execution

Off-site secondary storage

Manual setup required

AES-256 encryption at rest

Depends on implementation

Monthly restore testing

Alert on backup failure

Manual — usually nobody notices

Database binary log backup

Depends on implementation

India DC off-site storage

Depends on where S3 bucket is

Compliance documentation

One-click restore support

Manual restoration required

Talk About Managed Backup

FAQ

Backup questions

What is the 3-2-1 backup rule?

The 3-2-1 rule is the industry-standard backup architecture: 3 copies of your data, stored on 2 different types of media, with at least 1 copy off-site. For a web server this means: primary data on the server's disk, backup copy on a ZenoCloud backup server in a different datacenter, and a tertiary copy on S3-compatible object storage in a separate region. This means even if your primary server and the backup server both fail simultaneously (datacenter fire, power outage), you still have a recoverable copy.

Why do you perform monthly restore tests?

Studies consistently show that 30–70% of untested backups fail when you actually need them — due to bit rot, corrupted backup scripts, permission changes, or database engine version mismatches. Running a backup script successfully is not the same as having a backup you can restore from. We perform an actual restore test monthly: restore a sample of files and databases to a test environment, verify data integrity, and record restore time. If anything fails, we fix it before you need it.

How long does a server restore take?

File restore (single directory or file): typically under 30 minutes. Full database restore (100GB MySQL): typically 1–3 hours depending on disk I/O and restoration method. Full server restore from bare metal: 4–8 hours for a 100GB server. These are estimates — actual time depends on data volume, network bandwidth, and restoration method. We test restore times during monthly verification and report actual measured times.

Is backup data stored in India?

Yes, by default. Primary backup storage is in ZenoCloud's India datacenter infrastructure. Off-site secondary storage uses S3-compatible object storage in India. For organizations subject to DPDP Act requirements, India-resident backup storage ensures personal data does not leave Indian jurisdiction. International backup storage is available on request for multi-region DR requirements.

What is the difference between backup and disaster recovery?

Backup is the copy of your data. Disaster recovery is the plan and infrastructure that allows you to restore operations using that backup within a defined timeframe. Backup without a DR plan means you have the data but no tested process for using it under pressure. DR without backup means you have a plan but nothing to restore from. See /resilience/disaster-recovery/ for RTO/RPO planning and DR as a Service.

Can I restore a single file or database table without a full restore?

Yes. Granular file restore (single file, single directory) and granular database restore (single table, specific date via point-in-time recovery) are available. Full-server restores are available for disaster recovery scenarios. Contact our support team for any restore request — standard SLA is 4 hours for non-emergency restores, 1 hour for emergency.

Managed backup

The restore test you haven't run is the backup that will fail.

Free migration, zero downtime. Daily backups, monthly tested restores, India DC off-site storage. Talk to our team about adding managed backup.

Talk to Our Team See Disaster Recovery

+1 714 242 5683 · +91 99991 08033 · support@zenocloud.io