Disaster Recovery and Backup solutions
Automatic geo-replication
- Protect your data in our data centers in Amsterdam and Madrid. Guaranteed continuity for your critical applications by SLA.
- Deploy backup and Disaster Recovery solutions easily in our technical infrastructure — either Private Cloud or Bare Metal.
- Enjoy the peace of mind of relying on an Automatic Disaster Recovery solution.
Disaster Recovery made easy
Benefit from a tailored Disaster Recovery solution, that meets your business’ needs. You define the objectives, we help you achieve them efficiently.
Besides our automatic solution based on snapshots at storage level, we apply a snapshot policy of one snapshot every 2 hours in our data centers where the physical volumes are located. This allows a really quick recovery inside the data center in the event of a failure.
RPO adapted to your business’ needs
“Point-in-time” recovery
Predictable and guaranteed recovery time
Automated backup solution
Where Disaster Recovery sits in your architecture
At storage level. This is where our platform works by default. Every network storage tier — Flash Premium, Flash Plus and Standard — is fully geo-replicated between our Madrid and Amsterdam data centres, with the snapshot policy described above. Recovery does not depend on the operating system or the application being in a healthy state.
At hypervisor level. On top of your virtualisation platform, whether VMware vSphere or Proxmox VE, using its native replication and failover features. We deploy and operate both, so the DR design follows the platform you already run rather than forcing a migration.
At application level. Database replication, clustering or application-native mechanisms. This is the layer with the lowest RPO and also the one with most work on your side; we provide the infrastructure it needs, geo-distributed and sized to your objectives.
And the recovery target itself. Independently of the level you choose, the environment you recover into can be a cold spare — remote, dedicated infrastructure reserved for Disaster Recovery, sized independently from production and only paid for as reserve capacity. That is the piece that turns a written plan into a measurable recovery time.
Non-invasive to the current infrastructure
Low consumption of resources
Disaster Recovery for mission critical applications
Predictable monthly costs
Moreover, at infrastructure level, we maintain a spare node pool available for all our customers at no extra cost, so that they do not need to save a hot spare node within their cluster for HA.
In terms of efficiency, our modern backup architectures and controlled automation, among other features, lower the consumption of resources and guarantee a predictable monthly cost.
Network Storage’s basic backup schedule
Data durability guarantees are key in any project, that is why a full storage replica and basic backup schedule is not an option but included always by default (except for Archive, intended for backup purposes).
In addition to our basic set up, the backup schedule can be customized to meet individual needs.
In the main system
- One snapshot taken every hour (last one copy kept).
- One snapshot taken every 2 hours (last 2 copies kept).
- One snapshot taken every 6 hours (last one copy kept).
In the replica system
- One snapshot taken every 6 hours (last 16 copies kept; 4 days).
European infrastructure, European law
our Disaster Recovery copy is a complete copy of your production data. Where it physically sits, and which law governs it, is part of the design.
Both our data centres are inside the European Union — Madrid and Amsterdam — and the replica never leaves European soil. Stackscale is part of Grupo Aire, a European group, so ownership and control of the infrastructure stay under the same legal framework as the data.
Within the group, Aire Networks del Mediterráneo S.L. holds ISO 22301 (business continuity), ISO 27001 (information security) and ISO 27017 / 27018 (cloud security and personal data in the cloud), along with ENS Alta. You can consult the group’s certifications at airetech.es/certificaciones.
GDPR by design. Data processing agreement and sub-processor list available on request — with the certificate scope that applies to your service, in writing.
Contact us for further information about our Disaster Recovery and backup solutions
Disaster Recovery FAQ
What RTO and RPO can I expect?
Both are set per project, because they are what the architecture gets sized against rather than a fixed feature. As a reference point, the baseline snapshot policy on network storage takes one copy every hour, so an RPO of one hour is the starting point with no additional configuration; tighter objectives are met with continuous replication. RTO depends above all on whether the recovery environment is already running: dedicated infrastructure held in reserve recovers in a different order of magnitude than one provisioned on the day. Tell us the figures your business needs and we size the infrastructure against them.
What is the difference between backup and Disaster Recovery?
A backup is a copy you can restore from. Disaster Recovery is the commitment that a complete environment will be running again within an agreed time. Every one of our storage services includes a full replica and a basic backup schedule by default; Disaster Recovery adds the destination infrastructure, the action protocol and a measurable recovery time.
Do I need to migrate my infrastructure to contract Disaster Recovery?
No. The design is non-invasive to your current infrastructure and follows the virtualisation platform you already run.
Can I test the Disaster Recovery plan?
Yes, and it should be tested periodically — a plan that has never been run is an assumption, not a plan. The frequency and depth of each drill are agreed per project, together with what each one verifies: a full failover, a partial restore of a specific service, or simply measuring the real recovery time against the committed one. The test plan is defined alongside the DR design, not afterwards.
Where is my recovery copy stored?
In our own data centres in Madrid and Amsterdam, both inside the European Union. Network storage is geo-replicated between them by default.
What does the SLA guarantee?
Availability is committed contractually and depends on the configuration you choose: a single-site deployment is not the same as geo-replication between our Madrid and Amsterdam data centres, nor is reserved capacity the same as provisioning on demand. The SLA sets out what is guaranteed, over which components, and what happens if it is not met. We put the applicable figure in writing before you sign, not after.
How is it priced?
As predictable, reserved capacity rather than per recovery event. Cost scales with the tolerance you need: the lower the RTO and RPO, the more infrastructure has to be waiting. We size it against the business losses an outage would cause, so the figure is arguable rather than arbitrary.