Servers & virtual machines
Keep system images with the configuration and dependencies you need to rebuild your environment.
BACKUP & RECOVERY
Offsite storage.
A plan to restore.
Give backups a separate home. Choose capacity for your servers, databases and files, then plan how long to keep copies and how to bring them back.
STORAGE PRICING
Compare storage plans.
Review capacity, billing and setup fees for each available plan.
| Plan | Capacity & specifications | Price | Setup fee | Order |
|---|---|---|---|---|
| Let’s size the right storage plan. Share your data volume, retention and recovery requirements to discuss current availability. Request a storage proposal | ||||
Configured billing totals in BDT. Review capacity, retention, setup fees and the final service scope before ordering.
WORKLOADS
What are you backing up?
Choose capacity and a backup method that fit the data you need to recover.
RECOVERY PLANNING
Work backward from the restore.
- RPO · Recovery point objective
- How much recent data can you afford to lose?
- RTO · Recovery time objective
- How long can the workload be down while you restore it?
-
Capture
Take a consistent copy of the data your workload needs.
-
Transfer
Agree on access controls and a suitable transfer window.
-
Retain
Allow for changed data, retained versions and growth.
-
Restore
Test selected restores and document how to bring the workload back.
BEFORE YOUR FIRST BACKUP
Backup & recovery FAQs.
Need help planning a particular workload?
Speak to our teamIs storage the same as a backup service?
Storage provides a destination for data. A backup service also needs an agreed capture method, schedule, retention and restore process. Confirm the scope included in your selected plan.
Is a snapshot an independent backup?
Not necessarily. A snapshot tied to production may share its failure risks. Confirm where copies are stored, how they are isolated and how they can be restored.
What are RPO and RTO?
RPO describes acceptable data loss measured in time. RTO describes a target restoration time. These are planning objectives, not guarantees unless explicitly agreed in service terms.
How do I know a backup can be restored?
Agree on restore tests and verification. A successful scheduled job alone does not establish that the application will recover correctly.
How much capacity should I plan for?
Start with the protected data volume, expected change rate, retained versions and growth. Discuss these with our team before selecting an allocation.
Are encryption and immutable copies included?
Capabilities depend on the selected service and configuration. Confirm encryption, key handling, deletion permissions and any immutability requirements in writing before ordering.
PLAN FOR WHAT COMES NEXT
Plan your next backup.
Tell us what you store, how it changes and how you need to recover it.