Disaster Recovery as a Service

the Opportunity

The advent of cloud computing has presented an opportunity to dramatically reduce the costs and improve the effectiveness of disaster preparation and recovery. If any of these situations apply to you, then please call us about DRaaS:

  • Our business users have no idea what RPO and RTO mean and they have no idea what their DR service levels are.

  • You are still using old equipment in a cold or warm site as a back-up.

  • You haven’t tested your DR strategy in over a year.

  • Your back-up equipment does not have the capacity to run full production.

  • You’re not sure if all your data is available at the back-up site or whether all your applications will run.

here’s how Qi’s dr as a service works

How Disaster Recovery as a Service Works

Jump start DRaaS with a workshop

  • We work with IT and business users to look at the business impact of their choices of RTO (recovery time objective) and RPO (recovery point objective).

  • We translate business requirements into IT service levels and help assess the type of data replication and back-up needed for each application.

  • We define tiers of applications based on RPO/RTO service levels and help map DR architecture options to each tier.

cloud backup.jpg

Implement cloud-based DR

  • Qi supports public and private cloud options.

  • We can tailor different cloud replication and back-up technologies to your needs, including virtual machine replication, disk replication and database replication.

  • Our subject matter experts will implement the replication environment, test it and set up monitoring instrumentation to ensure that replication keeps running.

  • We’ll also map out the emergency DR environment and test it to ensure that it’s ready for you when you need it.

steady state.png

Let us manage your steady state replication

  • Once the replication services are in production, Qi’s network operations centre continuously monitors the health of the system to ensure that any issues (e.g. replication failure, queue build-up) are dealt with quickly without loss of data or failure to meet service levels.

  • Our ticketing system captures any changes to your production environment over and above those that are automatically captured by data replication. These changes are applied to the DR environment (e.g. addition virtual machines) and the recovery environment.


We can help with your DR testing

  • During the initial DRaaS workshop, we’ll ask you to decide on the frequency of DR testing (quarterly, semi-annually or annually).

  • Once the replication system is placed into production, we’ll work with your team to do the first DR test to ensure that all data is being captured, the emergency DR environment can handle your production needs, and that your RPO/RTO service levels can be met for each application tier.

  • We also ensure that you can switch back to your production environment and capture any data changes made in the emergency DR environment.

  • After each DR test, we’ll review the results with your team and make any adjustments to the replication environment and the emergency DR environment necessary.


when you have an emergency, we’ll be here

  • Should there be an actual emergency for any reason, we work with you to formally declare the emergency, assess its extent (i.e. does it impact all applications) and cut over to the emergency DR environment.

  • We offer war room facilities that you can use for the duration of your emergency.

  • We continue to ensure that your production needs are met for the duration of your emergency.

  • Once the situation has passed, we assist you in restoring your production environment and migrating back.