DRaaS with Veeam Cloud Connect

By Style Sync

| Published on

April 20, 2017

For the last two years, I have been working closely with many service providers across Australia and New Zealand to build Backup as a Service (BaaS) and Disaster Recovery as a Service (DRaaS) as an offering using Veeam Cloud Connect.

Veeam Cloud Connect introduces a great new opportunity for many service providers to become an off-site backup target for customers data and workload in the event of a complete Production site disaster.

In this blog, I want to share with you my experience building and configuring the Veeam Cloud Connect to offer a DRaaS.

Veeam says that their products are easy to deploy, but many service providers fail to correctly configure their Veeam Cloud Connect DRaaS installations through misunderstanding the network configurations required in the DRaaS offering. In my experience, the deployment is still easy, but quite involved. As you move toward configuring at a DRaaS level, you quickly find that you need to manage multiple moving parts of your data centre to build your solution, starting from your virtual infrastructure, storage, networking, firewalls, and more.

Before we start, let’s introduce the following scenario to make our discussion simple and to the point:

A service provider wishes to extend his offering of a DRaaS. After extensive market research, he came across a unique product, Veeam Cloud Connect. Veeam Cloud Connect will allow the service provider to “multi-tenant” a hypervisor and storage, and then share them with several customers. In the event of a disaster strikine, the service provider, or the tenant, is able to failover the environment or the workload to the service provider’s infrastructure and can do this without having to go through network reconfiguration, application connectivity, etc.

Let’s take a quick look at the Architecture of the proposed solution in the figure below.

In the following videos, you don’t need to watch them all to deploy the DRaaS offering based on Veeam Cloud Connect. Each video was recorded to discuss a single subject independently, and the length of each is kept below ten minutes.

Step 1: CloudCast Introduction