Cloud Manager

Cloud Manager panel control lets you to manage your entire infrastructure of cloud computing

Email Services

Access to your corporate e-mail securely and guaranteed:

      Webmail correu POP i IMAP   WebMail
      Correu OWA Exchange   OWA Exchange


Access your data from any device, always under your control.

Custom Search 1

RaaS - Disaster Recovery as a Service
Recovery as a Service (RaaS)
Minimize the amount of data lost between system crash and recovery
hosting server
Benefits RaaS Benefits
Implementation RaaS Implementation
Infrastructure Recovery as a Service Infrastructure
Packages RaaS Packages

Cloud-based disaster recovery service

RaaS, recuperasión de sistemas ante desastres

Prolonged system downtime can lead to major losses in time, resources and money for your business. Nexica's Recovery as a Service (RaaS) minimizes the amount of data lost between crash and recovery, guaranteeing the reliable restoration of critical IT services.

backup de sistemas

Designed as a pay-per-use (Cloud) service, it offers the option of paying only for the resources you consume, making it a more affordable option than traditional replication technologies (DRS). By replicating the physical and virtual servers hosted at our Barcelona IDC in our Madrid IDC, we can guarantee optimal recovery (RTO) and retention (RPO) times.


Features  Suitable for
  • Keeps a consistent copy (mirror) of the images of client servers.

  • Performance of regular recovery tests (simulations) to ensure that the recovery plan is functioning correctly.

  • If necessary, restoration of the replica on the available hardware platform and restoration of the server in an environment accessible by the client based on set conditions.

The Raas service is particularly suited to:


  • Companies that are highly dependent on their ICT platform business processes.

  • Organizations with highly concentrated resources and technology systems. In these cases, the risk is concentrated at the headquarters housing the ICT resources. Any incident that shuts down service at this location will paralyze the entire organization.

  • Need for geographical distribution of information to comply with corporate policy.

  • Cases where copies of information must be kept by law for a set period of time.

Examples of use: Banks, local government, Research and Development, consultancies (including legal/technology/business, etc.), software factories/development, etc.

Benefits RaaS
Implementation RaaS
Infrastructure Recovery as a Service
Packages RaaS


  •  Protection of critical systems for your business. Covers all leading operating systems (Windows and Linux) and applications.

  • Unlike data backups, it allows you to retrieve both the data and the applications that manage it.

  • Cost savings associated with disaster recovery plans. Eliminates the need for purchasing hardware, reserving physical space, and human resources for preparing and conducting tests.

  • Geographical separation (Barcelona/Madrid) between the original information source and the disaster recovery system, with secure hosting. With two data centers in Spain, it supports compliance with the Spanish Data Protection Act.

  • Reduced risk and costs associated with unavailable information.

  • The higher frequency of testing as part of the recovery plans directly translates into greater security and hence, reduced risk.

  • Scalable scope for the services covered. This means that it can be adapted to suit any condition covered by the corporate contingency plan. You can start by protecting only the most critical servers for your business and gradually migrate additional services or even complement them with an existing backup system on other sites.

  • Reduced Recovery Time Objective (RTO).

  • Recovery Point Objective (RPO) aligned to business needs, allowing you to tailor the service to the aims set down in the corporate Business Continuity Plan (BCP).

  • Service Level Assurance (SLA) based on the contracted RPO.

  • Service and resources management by highly trained technical/qualified staff.

Implementation phases


Preliminary phase of the project. In this phase, we analyze the needs and set the conditions of the service (RTO, replication mechanisms, etc). The assessment determines:

  • The best replication mechanism for each application (hypervisor, agent, mechanisms of the application itself).
  • The minimum consistency for all applications to begin their services on the contingency site (crash, file, application).
  • The expected RTO of the whole plan based on the applications and volumes of data that make up the protected platform.
Installation and launch

This phase covers the configuration of hypervisor-based replications, the cabinet and, if necessary, the installation of servers for the specific replication of any application that so requires (e.g., Exchange 2010 replication). This phase also includes:

  • Creation of scripts and necessary reconfigurations (network, nomenclature, DNS) for proper operation of the recovery plan.
  • Performance of first recovery tests and setting of reference RTO.
  • Drafting of a Disaster Recovery Plan. This document is agreed with the client and sets down:

o    The protocol for the formal declaration of a disaster and procedure for activating the contingency site. This includes contact telephone numbers, authorized persons, etc.
o    The results of the first recovery tests, which will determine the RTO and RPO to be used in future tests (and which will be recorded in the SLA of the service).
o    If third parties are involved (developers, client application managers), the protocols for service delivery will be set to determine the responsibilities of each party in the periodic tests and in the event of a disaster.

Service management

After the project has begun, periodic tests will be performed to ensure an optimal response in case of disaster.

  • By using virtualization on the contingency site, we can perform recovery simulations without involving the protected site.
  • This reduces the risk of failures during the necessary recoveries. The test simulates the total recovery of the services and detects any discrepancy between the recovery plan and the changes made on the protected site. This ensures that the recovery plan is always up to date.
  • The recovery tests are conducted bimonthly, unless additional testing is required.
  • Regular tests help us to detect changes in the RTO and take corrective action.


The service is based on Site Recovery Manager. Compatible with:

  • Linux
  • Windows

Both for the replication of virtual servers (at hypervisor level) and for the replication of physical servers (specific agents for each operating system) housed in our IDC in Barcelona, it allows all changes to applications to be replicated on Nexica's contingency site in Madrid.

For peak performance of applications hosted on the contingency site, in addition to the replicated servers, Nexica provides the necessary supporting infrastructure services of the Nexica ecosystem:

  • DNS service.
  • Perimeter firewall.
  • Network devices.Load balancer.
  • Shared storage.
  • Connectivity from Barcelona/Madrid and to the Internet.


Virtual Raas
  • All devices on the primary site to be protected are virtualized (NEXICA VMWare platform).
  • There are no dedicated network devices, or these can be omitted in the replication.
  • The minimum consistency required is crash consistency.
  • The RPO can be just hours.
Cloud RaaS

Same features as the Virtual RaaS, but on the vCloud Director platform and when additional settings are required to replace non-replicated Cloud features (network isolation, NATs, etc.).

Hybrid Raas
  • Physical servers or network devices must be protected.
  • Site Recovery Manager is always used for replication (there is no application-level replication).
  • The minimum consistency required is crash consistency (although the guarantee often extends to files or applications).
  • The RPO can be just hours (i.e. the client agrees to the loss of a few hours of data).
Hybrid Raas

Any scenario in which replications are required at application level to ensure consistency at application level and an RPO of minutes or seconds. for example:

  • Exchange 2010 (native replication).
  • Oracle RAC (Data Guard).
  • Active Directory (native replication).


  Virtual Cloud Hybrid Complex
VPS ok   ok ok
Cloud Servers   ok ok ok
Physical servers     ok ok
Application replication       ok
RPO Hours Hours Hours Minutes**
RTO* Hours Hours Hours Minutes**
Implementation time 1 week 1-2 week 2-3 week 1 month**

*The RTO will depend on numerous factors, including the number of protected servers, the volume of information to recover, the time taken to report the disaster, etc.
**For applications replicated by their own mechanisms, the RPO is minutes or seconds. For the rest of the platform, it will be hours.