Product tabs

Overview

What is Disaster Recovery as a Service?
DRaaS is a managed, cloud-based Disaster Recovery (DR) service that builds upon a standard backup and restore solution, enabling complete replication and re-enablement of your ICT operations during a business affecting outage.

Why do I need a Cloud DRaaS solution?
With so many businesses reliant upon internal and external access to and transfer of data, a disaster situation such as a major building fire can cause crippling damage to providers and end-users alike. A simple restoration of your most recent data snapshot will not be sufficient to resume business operations; a complete replication of your compute resource will be required.

What is 6DG DRaaS?
6DG DRaaS is a fully managed, DR service which utilises a cloud-based resource model. Your ICT estate is replicated and hosted in a dedicated DR environment within a virtual 6DG resource pool. We use the latest enterprise grade equipment located in one of our geographically diverse and secure UK data centres. Our expert team of in-house cloud engineers work directly with you to assess and plan bespoke Recovery Time and Recovery Point Objectives (RTO and RPO), ensuring timely, responsive and compliant hosting is available when you need it most.

Features Benefits
Off-site Deployment - Your data is protected in geographically diverse locations
Resource Reservation - Reservation of Disk, CPU and Memory capacity to be used in the event of a disaster
Scalable Resource - Ability to scale your reservation in line with the demands of your business
RPO - Definable RPOs allowing key data to be saved more frequently
RTO - Understand your business RTOs and react accordingly
Workload Protection - Protect the parts of your infrastructure that are required to operate your business
DR Plan & Test - Understand and test how your DR will be invoked and how resources will be made available to your users
Disaster Recovery - Restoration of agreed replicated compute resource

Protected Workload
Using enterprise grade software, the workload that needs to be protected can be defined along with the requirements for backup frequency and data retention. When handling large datasets, the same tools can be used to transfer data to a seeding disk drive; this encrypted data can then be sent by courier and imported into our cloud platforms to significantly reduce the time taken to protect your business.

DR Plan & Test
Tools are installed in your primary compute environment, whether on-premise, in colocation racks or hosted in a cloud. These are then configured to backup servers in our privately owned, geographically diverse UK data centres. The correct and appropriate technology is then chosen and deployed to ensure your agreed RTO, RPO, and commercial demands are all met. Data is routinely backed up to a secondary location with a defined and reserved amount of CPU, memory and disk space. Regular DR invocation testing can be undertaken in alignment with your agreed and approved Business Continuity plans.

Disaster Recovery
When an event takes place that requires the invocation of your DR plan, resources within our data centre alongside our highly skilled engineers can be used to bring your business online at full or partial capacity. Our engineers can be available to assist in the turning up of services and any agreed work to ensure end-user availability. We believe that a successful DR invocation is measured by user experience and not just infrastructure availability

Ask a question

Get in touch. Complete the form below.

Resources

Fill in the form to download the Disaster Recovery as a Service information pack.

*We will not sell your data, but we may market to you

Download Now

  • RTO determines how quickly you expect full compute resources to be restored.
  • An RTO of 4 hours is standard practice, though 1 hour recovery, or “live/live’ real-time restore, can be achieved if required
  • The agreed RTO is aligned with the RPO to provide a Service Level Agreement (SLA) for full Disaster Recovery.
  • A 24 hour RPO and a 4 hour RTO would drive a 4 hour restoration of compute services and a restoration of data no more than 24 hours old.
  • Some companies may choose to pay a higher fee for more frequent synchronisation which allows a shorter RPO window, e.g. a recovery point objective of 4 hours.
  • RPO determines how far back you wish to go when you restore data from a backup.
  • The RPO cannot be a timeframe more frequent than the actual backup schedule. For example, if the managed backup is scheduled for every 24 hours, the best-case RPO will be 24 hours.