Do you test that backups can actually be restored?

Yes. A successful backup job does not guarantee a successful recovery, so restore testing is built into the higher plans on a set cadence, with a written test report each time.

What are RPO and RTO?

Recovery Point Objective is how much data you can afford to lose, measured in time. Recovery Time Objective is how quickly a service must be restored. Both are design targets that shape backup frequency and recovery architecture, not guarantees.

Managed Infrastructure Services

Backup & Disaster Recovery

Protect Your Data. Recover Your Business.

Monitored backups · Verified restores · Offsite & immutable copies · DR planning

Every backup job monitored — a silent failure is the failure we see most
Restores tested, not assumed — with a written test report each time
Offsite and immutable copies a compromised server can't reach
Built around your RPO and RTO, not a fixed backup schedule
Your storage or ours — you choose where backups live

Get a Free Backup & DR Assessment Talk to a Recovery Expert

Since 2007 Running Production Infrastructure

Monitored Every Backup Job

Tested Restores, Not Assumptions

Any Host Cloud, VPS or On-Premise

When did you last test a restore?

Most businesses discover their backup problem during a recovery, not before it. The free assessment tells you what's actually protected, what isn't, and how long a real recovery would take.

What's backed up today — and what's been missed
Whether the backups can actually be restored
Your realistic recovery time, workload by workload
Ransomware exposure of the backups themselves

Request a Free Assessment

No obligation — the assessment report is yours to keep.

About This Service

Backup Is Only Half the Solution

Having a backup doesn't mean you can recover your business. We regularly see backups that have been failing quietly for weeks, backups sitting on the same server that just died, and backups nobody has ever attempted to restore.

A backup strategy has to answer three questions, and most don't answer the third.

What is protected?

Which servers, databases, files and configuration actually matter — and which are being missed right now.

Where does it live?

Whether a copy exists somewhere the failure, the attacker or the deletion can't reach.

How fast can it come back?

How long a real recovery takes, how much data you'd lose, and whether anyone has proven it.

eWebGuru designs and manages backup and disaster recovery around your infrastructure, applications and how much downtime the business can genuinely absorb.

An honest note on recovery objectives. RPO and RTO are design targets, not guarantees. Actual data loss and recovery time depend on backup frequency, data volume, transfer speed and how far the damage reaches. What we commit to is a designed strategy, monitored jobs, tested restores and a documented recovery procedure — so the outcome is predictable rather than hopeful.

Resilience

Backups That Survive the Incident

A backup stored on the infrastructure that just failed — or reachable by the attacker who just got in — isn't a backup.

Offsite Copies and the 3-2-1 Principle

The traditional 3-2-1 principle is still a sound starting point: three copies of important data, on two different storage types or locations, with one kept offsite. The right strategy for you depends on the workload and how fast it must come back.

An independent copy protects against

Hardware and storage failure
Ransomware and server compromise
Accidental deletion
Infrastructure or provider outage
Corruption that replicates to the live copy

How we apply it

Production backups kept off the production server
A second copy in separate storage or a separate region
Separate credentials for the backup environment
Backup traffic encrypted in transit, data encrypted at rest

Immutable & Protected Backups

A backup an attacker can delete is a backup you don't have. Where the storage platform supports it, backup copies are written so they cannot be altered or deleted for a defined period — including by someone holding your production credentials.

Immutable backup copies and retention locks, where supported
Restricted access to the backup environment
Separate backup credentials from production
Isolated backup infrastructure

Access control and audit of backup operations
Multiple recovery points rather than a single latest copy
Monitoring of deletion and retention changes

Immutability depends on the storage platform in use, so it's confirmed during design rather than assumed.

Ransomware Recovery

Ransomware doesn't only encrypt production — it looks for the backups. Recovery depends on having copies the attacker never had access to, and enough recovery points to go back past the moment of compromise.

What makes recovery possible

Separate backup infrastructure and credentials
Immutable copies where supported
Multiple recovery points across time
Monitoring that shows when the last clean backup was taken
Documented, rehearsed recovery procedures

Recovery is only half the job

Restoring into an environment that is still compromised repeats the incident
Investigation and remediation run alongside recovery
Hardening before the restored system returns to production

Security Services: investigation & remediation

The Part Most People Skip

Don't Assume Your Backup Works. Verify It.

A successful backup job does not guarantee a successful recovery. A backup system that fails silently for weeks is worse than no backup at all, because it creates confidence you haven't earned.

What we monitor

Backup success and failure, job by job
Jobs that didn't run at all
Backup age and the newest available recovery point
Backup storage capacity and growth
Retention compliance
Unexpected changes in backup size

How we verify

Backup integrity checks
File-level restore tests
Database restore tests
Virtual machine recovery tests
Application recovery validation
A written test report each time, with the measured recovery time

Backup

Jobs run to the schedule your RPO requires.

Verify

Integrity is checked and restores are tested on a set cadence.

Monitor

Every job's outcome is tracked, including the ones that never started.

Alert

Failures reach our team and yours, rather than sitting in a log.

Resolve

We investigate the failure and fix the cause, not just re-run the job.

We built tooling for this on our own fleet first. The failure mode we see most often isn't a dramatic one — it's a backup job that quietly stopped succeeding weeks before anyone needed it. Monitoring every job, and testing that the output actually restores, is the difference between having backups and having recovery.

Storage & Restores

Where Backups Live, How Long They Stay

eWebGuru-provided storage

We provide the backup storage as part of your plan, sized to your data volume and retention. One invoice, no separate cloud account to manage, and capacity planned as your data grows.

Your own cloud storage

Backups are written into your own S3, Azure or Google Cloud storage. The cloud provider bills you directly for the space, you keep full ownership and control of the data, and we manage the backup and recovery around it.

Retention designed, not defaulted

Not every backup needs keeping forever, and storage costs scale with retention. We set retention against how fast your data changes, how far back you might need to go, and any regulatory requirement that applies.

A common starting point:

Daily backups retained 7 days
Weekly backups retained 4 weeks
Monthly backups retained 12 months

Your actual schedule comes out of the assessment.

How restores work

Restores are quoted and billed per request, based on what needs recovering
You're not paying a monthly premium for restores you never use
Priority handling when a restore is urgent
Response target: [4 hours] standard, [1 hour] priority
We confirm the scope and cost before recovery work begins
Disaster recovery plans include failover assistance rather than per-incident quoting

Backup data is encrypted in transit and at rest, and access is limited to the engineers working on your environment.

Recovery Objectives

Define Your Recovery Objectives First

Two numbers shape everything else: how much data you can afford to lose, and how long you can afford to be down. We design backwards from them instead of selling a fixed backup frequency.

RPO

Recovery Point Objective — how much data can you afford to lose?

Your RPO sets backup frequency and whether replication or log backups are needed.

An RPO of one hour means the strategy aims to limit potential data loss to roughly the last hour of work — which usually means hourly backups or continuous replication, not a nightly job.

RTO

Recovery Time Objective — how fast must the service return?

Your RTO decides the recovery architecture, because restoring from cold storage takes longer than failing over.

An RTO of four hours means everything needed to bring the service back — data, servers, DNS, networking — must be recoverable inside that window, and tested to prove it.

Different workloads deserve different answers. Business continuity planning identifies the applications, databases and dependencies that are genuinely critical, then sets recovery priorities against them — so you're not paying for four-hour recovery on a system nobody would miss until Monday.

Disaster Recovery

Design a Recovery Environment That Fits

Disaster recovery is about restoring services, not just holding data. Four common architectures, in increasing order of cost and speed.

Lowest cost

Backup & Restore

Back up the workload and rebuild it when required. Suitable where some hours of recovery time are acceptable.

Slowest recovery

Balanced

Pilot Light

Critical components stay provisioned in a minimal state; the rest is brought up when a disaster is declared.

Faster, moderate cost

Fast

Warm Standby

A scaled-down but working copy of the environment runs continuously and is scaled up during an incident.

Minutes to recover

Highest availability

Multi-Site / Active-Active

Workloads run across multiple environments simultaneously, so losing one doesn't stop the service.

Near-zero downtime

A DR plan covers

Recovery infrastructure and backup replication
Application and database recovery, in dependency order
DNS and network configuration
File storage, background services and integrations
Written recovery procedures and runbooks
Failover planning and recovery testing

Recovery environments can be built on AWS, Azure, Google Cloud, eWebGuru Cloud or your own infrastructure — a second physical data centre isn't required.

Testing, and who declares a disaster

A recovery plan nobody has tested is a document, not a capability. Controlled tests validate backup availability, data and server recovery, database and application recovery, DNS and networking, the written procedures themselves, and whether your RTO and RPO are actually achievable.

Failover affects availability and data, so a named authorised contact on your side declares a disaster. That person is agreed when the plan is written, not found during the incident.

Don't discover a problem with your recovery plan during a real disaster. Restore testing runs on a set cadence on Business plans, and documented DR exercises run periodically on Disaster Recovery and Enterprise plans — each with a written report and the measured recovery time.

The Process

Our Backup & Disaster Recovery Process

Assess

We review your infrastructure, applications, data volumes and what the business actually depends on.

Identify

We determine what must be protected and rank workloads by how critical they are.

Define

RPO, RTO, retention and recovery requirements are agreed in writing with you.

Design

The backup and recovery architecture is designed around those objectives and your budget.

Implement

Backup jobs, storage, replication and any recovery infrastructure are configured and documented.

Monitor

Every job, storage pool and recovery point is monitored, with failures alerted rather than logged.

Test

Restores are tested on a cadence, with a written report showing what was recovered and how long it took.

Improve

The strategy is reviewed as your infrastructure, data volume and business requirements change.

Scope

Already Have Backups With Your Plan?

eWebGuru hosting includes weekly off-server backups, and backup add-ons are available on VPS. Here's what this service adds on top.

Capability Where It Sits

Weekly automated off-server backup	In your hosting plan
Backup add-on for VPS and Windows VPS	Hosting add-on
Backup strategy designed around RPO and RTO	Backup & DR
Monitoring of every backup job, with failure alerts	Backup & DR
Verified restore testing with written reports	Backup & DR
Designed retention policy	Backup & DR
Offsite and immutable copies	Backup & DR
Recovery infrastructure, replication and failover	Backup & DR
Documented recovery runbooks and DR exercises	Backup & DR
Investigation and remediation after a compromise	Security

Backup

Recoverable copies of data and systems that can be restored after loss, corruption or deletion. Every environment needs this.

Disaster Recovery

A planned method for restoring critical services after a major disruption — recovery infrastructure, replication, failover and tested procedures. Not every workload needs it, and we'll say so when it doesn't.

Plans

Backup & Recovery Plans

Priced on protection level and recovery requirements rather than gigabytes. Delivered on enterprise backup platforms including Acronis and Comet, chosen to suit the environment.

Backup Essential

Websites and non-critical servers

Custom quote Sized to your data volume and retention

Scheduled backups
Backup monitoring and failure alerts
Defined retention policy
Offsite copy option
File and database recovery on request

Request a Quote

Most Common

Business Backup

Important business applications

Custom quote Built around your RPO

Everything in Essential, plus:
More frequent backups and extended retention
Offsite copies as standard
Immutable copies where supported
Scheduled restore testing with reports
Database backup strategy
Monthly backup report

Request a Quote

Disaster Recovery

Business-critical infrastructure

Custom quote Designed to your RTO and RPO

Everything in Business, plus:
RPO/RTO planning and sign-off
Replication where required
Recovery environment
Documented recovery procedures
Recovery testing and failover assistance
Priority recovery support

Request a Quote

Enterprise DR

Critical multi-server environments

Custom scope Designed around your architecture

Everything in Disaster Recovery, plus:
Multi-workload recovery architecture
Advanced replication
Recovery automation
Documented runbooks per workload
Periodic DR exercises
Dedicated recovery planning

Talk to Us

Fees exclude 18% GST. Backup storage is either provided by eWebGuru as part of the plan or written to your own cloud storage account, billed to you by the cloud provider — your choice. Restores are quoted and billed per request.

Why eWebGuru

Recovery Designed by People
Who Run Production Infrastructure

Backup and disaster recovery are infrastructure problems as much as storage problems. Knowing how servers, databases and applications actually fail is what makes a recovery plan work.

Infrastructure Experience

Running hosting and server infrastructure since 2007, including our own network and hundreds of production virtual machines in Tier-IV facilities.

Recovery, Not Just Copies

We measure success by whether services come back, which is why restore testing and recovery time are part of the service rather than an optional extra.

Silent Failures Get Caught

Every job is monitored, including the ones that never ran. We built this tooling for our own fleet because quiet failure is the most common backup problem there is.

Flexible Architecture

Backup and DR designed across cloud, VPS, dedicated, colocation and hybrid infrastructure — including environments we don't host.

Security-Aware Design

Backup architecture built with access control, credential separation and isolation in mind, because ransomware goes looking for the backups first.

One Infrastructure Partner

Migration, management, security and recovery from the same team, so responsibility doesn't fall between vendors during an incident.

Service Portfolio

Which Service Do You Need?

Move it, automate it, operate it, manage the cloud, protect it, recover it.

What You Need Service

Protect data and recover services	Backup & DR
Secure servers, cloud and infrastructure	Security
Ongoing Linux or Windows server administration	Server Management
Ongoing AWS infrastructure management	Managed AWS
Move existing workloads to the cloud	Cloud Migration
CI/CD and infrastructure automation	DevOps

Security

Hardening, WAF, vulnerability management and incident response — recovery works better when the cause is fixed.

Explore

Server Management

Day-to-day Linux and Windows administration for the servers being protected.

Explore

All Managed Services

The full Managed Infrastructure Services range in one place.

Explore

FAQ

Frequently Asked Questions

What's the difference between backup and disaster recovery?

Backup creates recoverable copies of data and systems. Disaster recovery is the wider plan and infrastructure for restoring critical services after a major disruption — recovery environments, replication, failover and tested procedures. Every environment needs backup; not every workload needs full DR.

Where are my backups stored, and who pays for the storage?

You choose. Either eWebGuru provides the storage as part of your plan, or backups are written to your own cloud storage account and the provider bills you directly for the space. Backup data is encrypted in transit and at rest either way.

How are restore requests handled and charged?

Restores are quoted and billed per request, based on what needs recovering, so you're not paying a monthly premium for restores you never use. We confirm scope and cost before starting, and priority handling is available when a restore is urgent. Disaster Recovery plans include failover assistance rather than per-incident quoting.

Do you actually test that backups can be restored?

Yes. A successful backup job doesn't guarantee a successful recovery, so restore testing runs on a set cadence on Business and higher plans, with a written report showing what was recovered and how long it took. DR plans add periodic full recovery exercises.

Isn't backup already included with my hosting or VPS plan?

Hosting plans include weekly automated off-server backups, and backup add-ons are available on VPS. This service adds what those don't: strategy designed around your RPO and RTO, monitoring of every job, verified restores, designed retention, offsite and immutable copies, and disaster recovery. The comparison table above shows the full split.

Are backups protected from ransomware?

Where the storage platform supports it, we use immutable copies and retention locks, separate backup credentials, restricted access and isolated backup infrastructure — so someone holding your production credentials can't delete the backups. Multiple recovery points also mean you can go back past the point of compromise.

How often should I back up my server?

It depends on how fast your data changes and how much the business can afford to lose. That's what RPO is for: a one-hour RPO points to hourly backups or replication, while a daily RPO suits a nightly job. We set frequency from the objective rather than selling a fixed schedule.

Can you guarantee no data loss?

No. RPO is a design target, and real data loss depends on backup frequency, data volume, transfer speed and the nature of the failure. What we commit to is a designed strategy, monitored jobs, tested restores and a documented recovery procedure — which is what makes recovery predictable.

Can you back up servers hosted with another provider?

Yes. We design backup and recovery for AWS, Azure, Google Cloud, eWebGuru Cloud, other VPS and dedicated providers, colocation, on-premise and hybrid environments. Your infrastructure doesn't need to move.

Who decides when to invoke disaster recovery?

A named authorised contact on your side declares a disaster, agreed in advance as part of the plan. Failover affects availability and data, so that decision stays with you — and the person who makes it should be identified before an incident, not during one.

Can you provide disaster recovery for multiple servers?

Yes. Multi-server DR is designed around application dependencies and recovery priorities, so systems come back in the right order rather than all at once. That's what the Enterprise DR plan covers, including runbooks per workload.

We've been hit by ransomware. Can you help?

Yes, and recovery and investigation need to happen together — restoring into an environment that's still compromised simply repeats the incident. Our Security team handles investigation, containment and remediation while we recover from the cleanest available point.

Backup & Disaster Recovery

When did you last test a restore?

Backup Is Only Half the Solution

What is protected?

Where does it live?

How fast can it come back?

What We Protect, Wherever It Runs

Workloads

Data

Platforms

Backups That Survive the Incident

Offsite Copies and the 3-2-1 Principle

An independent copy protects against

How we apply it

Immutable & Protected Backups

Ransomware Recovery

What makes recovery possible

Recovery is only half the job

Don't Assume Your Backup Works. Verify It.

What we monitor

How we verify

Backup

Verify

Monitor

Alert

Resolve

Where Backups Live, How Long They Stay

eWebGuru-provided storage

Your own cloud storage

Retention designed, not defaulted

How restores work

Define Your Recovery Objectives First

Recovery Point Objective — how much data can you afford to lose?

Recovery Time Objective — how fast must the service return?

Design a Recovery Environment That Fits

Backup & Restore

Pilot Light

Warm Standby

Multi-Site / Active-Active

A DR plan covers

Testing, and who declares a disaster

Our Backup & Disaster Recovery Process

Assess

Identify

Define

Design

Implement

Monitor

Test

Improve

Already Have Backups With Your Plan?

Backup

Disaster Recovery

Backup & Recovery Plans

Recovery Designed by PeopleWho Run Production Infrastructure

Infrastructure Experience

Recovery, Not Just Copies

Silent Failures Get Caught

Flexible Architecture

Security-Aware Design

One Infrastructure Partner

Which Service Do You Need?

Security

Server Management

All Managed Services

What Happens If Your Server Fails Tomorrow?

Frequently Asked Questions

Related Managed Services

Infrastructure Security Services | Server Hardening, WAF & Malware Removal | eWebGuru

Server Management Services | Linux & Windows Server Management | eWebGuru

Managed AWS Services India | 24×7 AWS Management | eWebGuru

Cloud Migration Services

Let's build the right server solution for you.

Send Enquiry

Recovery Designed by People
Who Run Production Infrastructure