Disaster recovery
Replicate your Veeam environment to a recovery site we manage
DRaaS for Veeam uses Veeam Cloud Connect to replicate your virtual machines from your own Veeam Backup & Replication console to a recovery site run by a service provider. Storcom, based in Geneva, Illinois, manages that target, builds the failover plans and runbooks, tests failover on a schedule, and handles failback.
Last updated
Practice: Backup and disaster recovery
- Built for
- For organizations already running Veeam Backup & Replication on VMware or Hyper-V.
- What you get
- Works from the Veeam console you know
- Encrypted connection, no VPN required
- Failover plans with boot order
- Tested failover and planned failback
- 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.
Production running. Replication healthy.
- 1Primary site lost
- 2Failover started from the runbook
- 3Systems up in dependency order
- 4Users reconnected at the recovery site
Illustration only. Your recovery time is the RTO we design and test with you.
How does Veeam Cloud Connect replication work?
Veeam Cloud Connect lets a service provider host the replication target for your Veeam environment. You add Storcom as a service provider in your Veeam Backup & Replication console and create replication jobs as you would for any other target. Replicas of your VMware vSphere or Hyper-V virtual machines travel over an encrypted connection to a cloud gateway, so you do not need a VPN or a second data center.
Storcom runs the provider side. We size the compute, storage and network capacity your replicas need to run during a failover, keep that environment patched and monitored, and give you 24×7×365 support when something goes wrong.
Replication runs on a schedule you set for each VM or group of VMs, so critical systems can have tight recovery points while everything else replicates less often. Application-aware processing keeps databases such as SQL Server and Exchange consistent in the replica.
What’s included
Failover plans
Groups of VMs that fail over together, with boot order and delays so domain controllers, databases and application servers start in the right sequence.
Full or partial failover
Fail over the whole site, or only the VMs that are affected. In a partial failover, a network extension appliance keeps the failed-over VMs talking to systems still running on premises.
Network mapping
Recovery networks can mirror your production IP ranges, so VMs come up without re-addressing. Public IP rules can be set for services that must stay reachable from the internet.
Written runbooks
Each failover plan is backed by a runbook that names the steps, the owners, and the checks that prove an application is working.
Scheduled failover tests
We test in an isolated network so production is not touched, time each step against your RTO, and send you a report.
Planned failback
When your primary site is ready, changes made during the outage replicate back and you return to production in a window you choose.
What does onboarding look like?
Discover
A discovery call, then sizing of the VMs you need to protect, their change rate, and the RTO and RPO each application needs.
Design
We map failover plans, recovery networks and target capacity, and agree what Storcom manages and what your team keeps.
Seed and replicate
Initial replicas are seeded to the recovery site, then incremental replication runs on the agreed schedule.
Test and hand over
We run the first failover test, fix what it finds, and hand you the runbook and the test report.
DRaaS for Veeam or Veeam cloud backup?
Both run from the same Veeam console. They solve different problems.
| Topic | Veeam cloud backup | DRaaS for Veeam |
|---|---|---|
| What leaves your site | Backup copies of VMs, files and applications | Ready-to-run replicas of virtual machines |
| How you recover | Restore data back to your own hardware | Power on replicas at the recovery site and keep working |
| Retention | Long, with immutable off-site copies | Short, a set number of recent restore points |
| Use it for | Deleted data, ransomware rollback, compliance retention | Site loss, hardware failure, extended outages |
Many Veeam customers run both: cloud backup for history, replication for fast recovery.
What to ask any Veeam DRaaS provider?
Use these questions to compare providers, including us.
- What RTO and RPO will you commit to for each of our applications?
- How often do you run failover tests, and what evidence do we get afterward?
- How does failback work, and who schedules it?
- Where is the recovery site, and how far is it from our primary site?
- How are networks and IP addresses handled when replicas power on?
- Who runs the failover at 2 a.m. on a holiday, and how do we reach them?
- What does support cover during a real disaster, and what costs extra?
Technology we deploy for this
Veeam backup and replication for virtual, physical, cloud and Microsoft 365 workloads, plus Veeam-based cloud backup and DRaaS that Storcom runs for you.
Sources
- Veeam Cloud Connect, Veeam Backup & Replication User Guide Veeam Help Center. Accessed .
- Using Cloud Hosts, Veeam Cloud Connect Guide Veeam Help Center. Accessed .
Frequently asked questions
Do we need to replace our Veeam setup to use DRaaS?
No. DRaaS for Veeam works with your existing Veeam Backup & Replication server. You add Storcom as a service provider in the console and create replication jobs that point at the Storcom-managed target.
Which hypervisors does DRaaS for Veeam support?
Veeam Cloud Connect replication supports VMware vSphere and Microsoft Hyper-V virtual machines. Physical servers and other platforms need a different approach, which we cover on the discovery call.
Does Veeam replication need a VPN or a dedicated circuit?
No. Veeam Cloud Connect sends replication traffic over an encrypted connection to a cloud gateway, so a VPN is not required. If your change rate is high or you already have private connectivity, we factor bandwidth into the design.
Can we fail over just one application?
Yes. A partial failover brings up only the affected VMs at the recovery site, and a network extension appliance lets them keep communicating with systems still running in your data center. Full-site failover is there for when the whole site is down.
How is failback handled?
While you run at the recovery site, changes are tracked. When production is ready, Veeam replicates those changes back to your environment, you switch over in a window you choose, and then commit the failback. Storcom plans the steps with you and runs them alongside your team.
Who runs the failover during a real disaster?
You can trigger it yourself from the Veeam console, or have Storcom run it. In the Managed Recovery Program, a named service delivery manager owns the failover and follows your documented runbook.
Related services
- DRaaS OverviewDisaster recovery as a service from Storcom: Veeam or Zerto replication, a stated RTO and RPO per application,…
- Managed RecoveryManaged disaster recovery from Storcom: documented runbooks, failover tests against your RTO and RPO, and a…
- Veeam cloud backupVeeam-based cloud backup with off-site, immutable copies, scheduled restore tests and reporting.
- Cloud backup overviewCloud backup as a service with off-site, immutable copies and tested restores.
- Business Continuity ConsultingBusiness continuity consulting from Storcom: business impact analysis, recovery objectives by tier, BC/DR…
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.