Cloud Disaster Recovery &
Business Continuity
We run your recovery site in Tier III EU data centres: Veeam replication from 15-minute intervals, scheduled test restores, and RPO/RTO fixed in the SLA, with an RTO of 1 to 2 hours for critical systems.





Which of these sounds familiar?
What the solution includes
Together with you we define critical systems, target RPO/RTO for each tier of systems, and the disaster scenarios you protect against. The output is a continuity plan, not just copies.
Capacity in Baltneta’s Tier III data centres in Lithuania (ISO 27001, PCI DSS). Replicas are transmitted and stored encrypted; the site is geographically separate from your primary infrastructure, with EU data residency.
Virtual-machine replication from a 15-minute interval, via Veeam Cloud Connect over an encrypted TLS/SSL channel. Managed from your existing Veeam console or entirely on our side.
Regular failover tests in an isolated environment, with no impact on production systems. After each test you get a report: what came up, how fast, what to fix.
On the day of a disaster, switchover to the recovery site by a rehearsed scenario; after the primary is restored, failback. Support, RPO and RTO fixed in the SLA.
Three classes of solution: an honest comparison
DRaaS covers the middle: critical systems without the budget for a second data centre of your own.
| APPROACH | WHAT IT GIVES | TYPICAL FIGURES | WHEN IT FITS |
|---|---|---|---|
| Off-site backups | Data is kept, but after a disaster the infrastructure has to be rebuilt from scratch | RPO: hours to a day RTO: days | Non-critical systems, archives |
| DRaaS: this service | A ready site in the EU: systems come up from replicas and run while your primary site is down | RPO from 15 min RTO 1 to 2 h, in the SLA | Critical business systems without the budget for a second data centre |
| Active-active synchronous cluster | Two sites run at once, switchover is almost unnoticeable | RPO ~0 RTO: minutes | When an hour of downtime is already too much; doubles infrastructure and budget |
One contract. Clear responsibilities.
You sign one contract and work with one project lead. Here is who is responsible for what.
An Austrian company with 20+ years in the market. Holds the contract and supplies the hardware under the solution, with EU invoicing, delivery and warranty under European law. A single point of responsibility for the project.
Backup and recovery engineering: DR strategy design, replication setup, test restores and support.
Veeam AuthorizedVMware Premier Partner
EU hosting: Vixen.UNO’s data-centre partner is Baltneta (Lithuania, since 1996, part of Atea group): its own Tier III data centres, ISO 27001, PCI DSS Level 1, EU data residency. balt.net ↗
More about Vixen.UNO ↗How we work, step by step
01free of charge
02free of charge
03paid stage
04
When we are not the right fit
The key questions, answered
How is this different from backup?
Where are the replicas physically stored?
What RPO and RTO do we get?
Can we manage replication ourselves?
How do we know it will actually work?
How do you handle our data during the project?
Who is the contract with, and who is responsible for the result?
From our engineering blog
Why one target for every system is an expensive mistake: tier the systems and pay for fast recovery only where it is justified.
Read the article →Three-node clusters, live migration limits and why a GPU pool should stay homogeneous.
Read the article →Let’s talk about your project
We reply within one business day