Disaster Recovery

Back in business in minutes after a disaster. Not days.

Hurricane, flood, ransomware, or a dead server. We keep a secure, up-to-date copy of your systems on AWS, ready to switch on the moment you need it. You pay for the full recovery site only when you use it.

AWS Partner

AWS Select Tier Services Partner

Built on AWS Elastic Disaster Recovery

  1. Something breaks

    Your office server goes offline

    Storm, flood, attack, or a failed drive.

  2. Your copy on AWS takes over

    Last copiedSeconds ago
    Last recovery drillPassed
    Recovery siteSwitching on
  3. Minutes later *

    Back online, running on AWS

    Your team keeps working, from wherever they are.

* This shows a standby copy of systems that run in your office. If your systems run fully on AWS instead, there is no office server to lose and no switch-over to wait for.

Any IT disruption can stop the business.

Natural disasters, malicious attacks, or simple human error. Each one can take mission-critical applications offline, and each one tests your recovery targets.

Natural disasters

A hurricane, flood, or fire can take a primary site, or a whole region, offline for days.

Ransomware and malicious attacks

Attackers lock or corrupt production data. Without a clean, isolated copy to recover from, operations stop.

Infrastructure failure

Hardware, power, or network failure at a data center takes down every application hosted there.

Human error and data corruption

One accidental deletion or one bad change can corrupt an application the whole company depends on.

Recovery targets nobody has proven

Many teams avoid drills because they are complex and disrupt production. A plan that is not tested rarely meets its targets.

Compliance and contract penalties

Regulators and customer contracts set limits on downtime and data loss. Missing them adds penalties on top of lost revenue.

What does an hour of downtime cost?

More than lost revenue. Customers leave, staff sit idle, your reputation takes the hit, and regulators add penalties.

$1M

an hour at the high end. A critical application failure costs Fortune 1000 companies $500K to $1M per hour on average.

IDC

76%

of companies had an outage in the past two years that needed a disaster recovery plan.

Gartner survey of 1,200 companies

$150M

in profits lost by one leading U.S. airline after a single outage.

Forbes

A backup is not a recovery plan.

Backups save your files. They do not bring your business back. Here is the difference on the day something breaks.

Backups only

You have your files. You do not have your business.

  • Copies your files and data on a schedule
  • Everything since the last backup is gone
  • Servers must be rebuilt before anything runs
  • Running again in hours or days
  • Rarely tested from start to finish

Disaster recovery

Your whole system, ready to switch on.

  • Copies whole systems: applications, databases, settings, files
  • Copies continuously, so you lose seconds of work, not a day
  • Starts up on AWS as working servers
  • Running again in minutes
  • Tested with drills that do not interrupt your team

Keep your backups for long-term records. Disaster recovery is what gets you running again.

A second copy of your business, kept on standby.

The same four steps whether your systems run in your office, in a data center, or in another cloud.

Your systems today

Office, data center, or cloud

Copied all the time, encrypted

Low-cost standby on AWS

Data loss of seconds (RPO)

Switched on only when needed

Full recovery site

Running in minutes (RTO)

01

Set up

We install a small piece of software on each server. No reboot, and no slowdown your team will notice. Copying starts right away.

02

Test, then keep testing

We run a recovery drill on AWS while your real systems keep working. You watch it work before you ever need it. Then we repeat the drill on a schedule.

03

Switch over

When something goes wrong, we start your systems on AWS from the latest copy, or from an earlier moment if the latest one is damaged.

04

Switch back

Once your office or data center is fixed, we move you back and turn the recovery site off, so you stop paying for it.

Run it yourself, or leave it to us.

The steps are the same either way. You choose who handles them after set up.

Option 1: we set it up

We install it, test it, and hand it to your IT team. They run steps 2 to 4 from there.

Option 2: we set it up and run it

We also run the drills, check the status of the copy, and handle the switch-over and the switch back.

Ransomware recovery

Built for ransomware, not only weather.

A storm takes out a building. An attack takes out your data and waits for you to pay. Your recovery has to work for both.

  • Go back to before the attack

    Your systems restart from a clean copy taken before your files were locked.

  • Copies that cannot be changed

    Each saved copy is locked. An attacker cannot alter it or overwrite it.

  • Kept apart from your network

    The copy sits in its own separate AWS account. Getting into your office network does not get anyone into it.

  • Encrypted on the way

    Your data is encrypted while it travels to AWS.

Pick the moment to go back to

  1. Monday, 9:00 amSaved copy
  2. Tuesday, 9:00 amSaved copy
  3. Tuesday, 2:00 pm

    Last clean copy

    Restart from here
  4. Tuesday, 2:14 pmFiles start getting locked

Your systems restart clean. Nothing from after the attack comes with them.

Tested by a real hurricane.

A 35-person manufacturer we moved to AWS kept working through a Category 1 hurricane.

Server hardware, from the Entvas hurricane case study

Zero*

Downtime during a Category 1 hurricane

The storm dropped more than 30 inches of rain and cut off every road. Employees opened their laptops from hotels and relatives' houses and kept working. Orders were processed and invoices went out on schedule.

  • $58,000 in daily sales kept flowing
  • 98% of their systems moved to AWS before the storm
Read the full story

* This client runs almost everything on AWS, so the storm had no office server to take down. That is one way to be protected, and it relies on AWS itself staying up. The standby copy on this page is the other way, for systems that stay in your office.

What other companies report with the same AWS service

12x

Faster recovery

A government software company. It protects more than 4,300 virtual machines and can recover entire data centers.

80%

Lower recovery cost

A specialty food maker running SAP. Recovery time target of 15 minutes. Data loss target of 5 minutes.

72 hrs to 2

Recovery time

A community hospital. Almost 140 servers. Recovery time cut by 97%, from 72 hours to under 2.

Results published by AWS about its own customers, shown here without names. They are not Entvas clients.

20+

Founder's years building business systems

Our founder has been automating business workflows since 2006, through the whole move from server rooms to the cloud.

AWS Select Tier Services Partner

AWS has reviewed our team and our work. Your recovery copy lives in your own AWS account, so it stays yours. The AWS service we use was named market leader in the 2022 Frost Radar for disaster recovery as a service (Frost & Sullivan).

Based in St. Petersburg, Florida

We live and work in hurricane country. Storm season is on our calendar every year, the same as yours.

Questions owners ask

Plain answers. Bring the rest to the assessment call.

Backups save your files. After a disaster you still have to find new servers, rebuild them, and restore everything before anyone can work. That takes hours or days. Disaster recovery keeps your whole system ready to start, so you are running again in minutes.

Find out how long you would be down.

Book a free recovery assessment. We look at what you run, what a day offline would cost you, and what it takes to be back in minutes. No pitch, no obligation.

Book a Free Recovery Assessment