Skip to content

Disaster recovery

We run your disaster recovery plan with you, and prove it works

Managed disaster recovery is a service in which a provider plans, tests and runs your recovery alongside your IT team. In the Storcom Managed Recovery Program, a named service delivery manager owns the failover, keeps runbooks current, schedules tests against a stated RTO and RPO, and reports the results to leadership and auditors.

Last updated

Practice: Backup and disaster recovery

Built for
For teams whose backups run but who have never tested a full recovery.
What you get
  • Named service delivery manager owns failover
  • Runbooks written and kept current
  • Tests scheduled against your RTO and RPO
  • Reports for leadership and auditors
Delivered from
Geneva, Illinois, for Chicagoland and customers across the U.S.

Watch a failover

Lose the primary site and see what a tested runbook does next: systems come up in dependency order at the recovery site and users are reconnected.

OfficesRemote usersBranch sitesPrimary siteStorcom recovery siteImmutable backup

Production running. Replication healthy.

  1. 1Primary site lost
  2. 2Failover started from the runbook
  3. 3Systems up in dependency order
  4. 4Users reconnected at the recovery site

Illustration only. Your recovery time is the RTO we design and test with you.

Why do backups alone fall short?

Most teams have backups. Fewer have restored a full application from them under pressure. A recovery depends on much more than data: the order systems start in, DNS and network changes, service accounts and credentials, and the people who know which step comes first.

If that knowledge lives in one engineer’s head, or in a runbook nobody has opened since the last migration, your recovery time is a guess. The Managed Recovery Program turns it into a number you have tested, with someone at Storcom accountable for hitting it.

How does the Managed Recovery Program work?

  1. Discover

    We inventory your production applications and map their dependencies: the servers, databases, network services and outside connections each one needs. This sets the recovery order.

  2. Design

    Together we place each application in a recovery tier with its own RTO and RPO, then write the runbook: every step, its owner, and the check that proves it worked.

  3. Test

    We run failover tests on an agreed schedule, including outage and cyber incident scenarios, time each step against the objective, and review the results with you.

  4. Manage

    As your environment changes, we update the runbooks and the recovery configuration so the plan never drifts from what is actually running.

What is included

  • A named service delivery manager

    One person at Storcom who knows your environment, owns the failover during tests and real events, and is your escalation point.

  • Documented runbooks

    Written recovery procedures for each application and its supporting infrastructure, versioned and kept current.

  • Scheduled failover tests

    Tests against a stated RTO and RPO, run by Storcom with your team, followed by a review of anything that missed.

  • Application-level recovery

    Applications are brought back to a working state, not just restored: services started, databases consistent, users reconnected.

  • Reporting for leadership and auditors

    Test results, timings against objectives and open remediation items, in a form you can hand to your board or your auditors.

  • 24×7×365 support

    Call 1 (866) 610-7472 or email recoversupport@storcom.net to declare an event or open a ticket, any hour of the year.

Why set recovery objectives by tier?

Tight objectives cost money. Setting them per application tier puts the spend where downtime hurts most, instead of paying for the tightest target across the board.

Why set recovery objectives by tier?
TierTypical applicationsRecovery approach
Tier 1: criticalERP, order entry, clinical systems, core databasesFrequent or continuous replication, pre-staged capacity, tested most often
Tier 2: importantEmail, file services, internal line-of-business appsScheduled replication or fast restore from backup
Tier 3: deferrableArchives, development and test, reportingRestore from backup once tiers 1 and 2 are running

Your tiers come from a business impact analysis, not from a template. We set them with you.

Technology we deploy for this

  • Veeam logo

    Veeam

    Veeam backup and replication for virtual, physical, cloud and Microsoft 365 workloads, plus Veeam-based cloud backup and DRaaS that Storcom runs for you.

  • Zerto logo

    Zerto

    Zerto, an HPE company, provides the continuous replication and orchestrated failover Storcom uses for disaster recovery when recovery points need to be close to the moment of an outage.

Frequently asked questions

What does a service delivery manager do?

Your service delivery manager is a named Storcom contact who owns your recovery program. They coordinate tests, keep runbooks current, run the failover with your team during a real event, and review the results with you afterward.

Does Managed Recovery replace our IT team during a disaster?

No. Your team stays involved and makes the business decisions, such as when to declare a disaster. Storcom carries out the runbook, coordinates the technical steps and keeps everyone informed, so your people are not working from memory in the middle of the night.

Which DR platforms does the program cover?

The program is built around Storcom DRaaS on Veeam or Zerto replication, and it covers restores from backup for lower-tier applications. If you run other recovery tools today, we review them during discovery and tell you what can be managed as it is.

How often are failover tests run?

The test schedule is agreed at the start and written into the program, usually with tier 1 applications tested more often than lower tiers. We also recommend a test after any major change, such as a migration or a new core application.

What evidence do auditors get from the program?

You get written records: the recovery objectives for each application, the runbooks, dated test reports with timings against those objectives, and the remediation of any issues found. That is the kind of evidence auditors and examiners typically ask to see when they review disaster recovery.

How do we get started?

Start with a discovery call. From there we size your environment, review your current backup and recovery setup, and show you the gap between the recovery times you expect and what your setup can deliver today.

Start with a discovery call.

Tell us what you run today, what is changing and what worries you. We listen, ask questions and tell you plainly whether and how we can help. No cost, no commitment.

We value your privacy

We use cookies to enhance your browsing experience, analyse our traffic and identify the companies that visit us. By clicking “Accept All”, you consent to our use of cookies. Read our Cookie Policy.