Now Available: Weekly Cloud Backups Across All Plans
One more housekeeping announcement: we've now switched on free weekly cloud backups for every customer, regardless of plan. The backups are stored in a separate region from your live hosting, and you can restore from them via your control panel in a few clicks.
Yes, free. Yes, on the Starter plan too.
What's included by plan
| Plan | Frequency | Retention |
|---|---|---|
| Starter | Weekly | 7 days (2 snapshots) |
| Business | Daily + Weekly | 14 daily + 4 weekly |
| Cloud Business | Daily + Weekly | 30 daily + 8 weekly |
| Reseller | Daily + Weekly | 14 daily + 4 weekly |
What gets backed up
- Your entire
public_htmldirectory (website files) - All databases on the account
- Email mailboxes and aliases
- cPanel configuration and DNS zone files
- Cron jobs and SSL certificates
Basically, "everything you'd need to recreate this account from scratch."
Where they're stored
Our backups go to an object storage cluster in a different geographic region from your hosting node. The reason: if the rare bad day comes for your primary data centre — fire, flood, hardware failure — your backups are not in the same building. This is the "off-site" leg of the 3-2-1 backup rule that we wrote about in our post on daily backups.
How to restore
From your control panel:
- Open Cloud Backups.
- Pick a snapshot from the dropdown — they're labelled by date.
- Choose what to restore: full account, files only, database only, or a specific path.
- Click Restore. The process takes 30 seconds to a few minutes depending on size.
If you'd rather download a snapshot instead of restoring it directly, that's also an option — useful when you want a copy outside our infrastructure entirely.
What this doesn't replace
Two things this isn't:
- Real-time replication. Snapshots are point-in-time. If you need zero data loss, you still need application-level replication, which we offer on Cloud Business plans.
- Version control. If you're a developer, you should still keep code in Git. Backups are for recovery, not history.
The boring details
For the technically curious:
- Backups are taken using
rclonewith server-side encryption (AES-256). - Compression is applied before transit — your stored backup size is typically 40–60% of your live account.
- Retention is enforced with a separate cleanup job that runs daily; you'll see snapshots quietly age out.
- Backup windows are 2am–5am IST. CPU and disk impact during the backup is negligible thanks to our NVMe upgrade earlier this year.
Backups don't matter until the day they do. The good news is that day comes once or twice per business, ever — and on that day, you'll find five minutes of restore time is the difference between a non-event and a catastrophe.
If you have specific compliance requirements that go beyond what's included — longer retention, customer-managed encryption keys, geographically specific storage — get in touch. We have solutions for that on the Enterprise tier.
Thanks as always for trusting us with your sites. The whole point of this work is so you don't have to think about it.