Search This Blog

Sunday, May 15, 2016

Building Backup as a Service (BaaS) Using Veeam

(click on picture to view in large mode)

Backup as a Service (BaaS) provides backup and recovery operation from the cloud. Service Provider/Reseller will need to maintain the infrastructure in their data center.

Meanwhile, customer will use Veeam Backup and Replication to transfer their backup data offsite without need to buy servers, storage or maintain an offsite datacenter.

With Cloud Connect features, customer able to transfer the data to service provider.

The following are the components require to build BaaS:

Reseller/Service Provider - provide BaaS

  • Veeam Backup and Replication v9
  • Veeam Repository to store tenant backup data. Act as Cloud Repository
  • Cloud Gateway - from Veeam
  • WAN Accelerator  from Veeam
  • SSL Certificate
  • Cloud Connect Replication license
  • Create tenant account and pass to tenant
If you do not has a datacenter, you can leverage on Microsoft Azure infrastructure. Start BaaS by deploying VCC for Service Provider appliance from Azure MarketPlace. Check out here.

Tenant (Customer)
  • Must use Veeam Backup and Replication at least v8 to backup virtualization infrastructure
  • Veeam Backup Repository
  • WAN Accelerator from Veeam
  • Veeam Cloud Connect features which allow tenant to transfer backup data to Service Provider : Cloud Repository

Communication channel

With Veeam Cloud Connect, the connection will happen directly over the Internet, using a single TCP port (TCP/6180), protected by SSL encryption. The Cloud Gateway, responsible for the transfer of all the backup traffic over the single port connection.

WAN accelerators are optional components that can be deployed at the service provider & tenant side to improve the bandwidth utilization of remote backups sent by customers.

Backup Data

Backup Hyper-V / Vmware hypervisor using Veeam Backup to Veeam repository. 
Use Backup Infrastructure to add Service Provider. 
Lastly, configure Backup Copy Job to transfer backup data to Cloud Repository (@Service Provider)

Now your customer has backup archive transfer to offside without require to invest on secondary datacenter.