This page exists because backup is the single most commonly assumed and most commonly absent part of a hosting purchase. Read it before you migrate anything you cannot recreate.
The short version
Off-server backup retention is not included in the published plan price. Unless you have separately agreed a backup scope in writing, assume that no copy of your data exists anywhere except on your own server.
What is not a backup
- A snapshot stored on the same host storage as the workload. It survives a mistaken delete inside your operating system. It does not survive a storage failure, and it is no defence against ransomware that has your credentials.
- RAID. RAID protects against a failed disk. It faithfully replicates a
mistaken
DROP TABLEto every disk in the array. - A backup you have never restored. Until a restore has succeeded you have an untested assumption, not a backup.
What a workable arrangement looks like
- Copies stored somewhere other than the server they came from — a second node, object storage, or your own premises.
- A stated retention window, so you know how far back you can go.
- Application-consistent database dumps, not only file-level copies of a running database directory.
- Encryption of the copies, with the key stored separately from them.
- A restore test on a schedule, with the date of the last successful test written down.
Arranging backup with us
If you want backup handled rather than run yourself, ask before you order. Write to sales@awdhpl.com or call +91 98297 14343. The scope needs to state what is copied, how often, where copies are held, how long they are kept, who can trigger a restore, and what the restore time objective is. Anything not written into that scope is not covered.
On termination
When a service ends, its storage is scheduled for deletion. Retrieve your data before the service ends; deletion is not reversible. See the terms of service.