July 14, 2017
Delivering BaaS and DRaaS with Multi-Tenancy – DRaaS Configuration
In the past two posts we covered the Multi-tenant functionality of NAKIVO Backup & Replication, as well as looked at Backup-as-a-Service and what this means for tenants. In the final part of the series, we will take this a step further and look at DR-as-a-Service (DRaaS).
DR-as-a-Service (DRaaS) is aimed at providing continuity of business and applications, which is achieved with the replication feature allowing us to failover from a primary location to a DR location. Let’s take a closer look at this.
DRaaS: Setting up Replication in Multi-Tenant Mode
Setting up replication in Multi-tenant mode is very much the same as if we are in a standard, non-tenant environment. Replication for a tenant can either be setup by the global administrator of the NAKIVO Backup & Replication environment or by the tenant admin for each environment. The first thing we do is navigate to our Jobs view and choose the Create >> VMware/Microsoft Hyper-V replication job.
***Note*** The available options are presented based on which environments you have added in the Inventory configuration. As noted below, we have a VMware environment connected in our inventory.
Next, we select the VM(s) that we want to replicate to an offsite DR location.
The Destination would be the target offsite DR cluster where we want the VM to be replicated. In this case, the replicated VMware VM would be exactly copied to the target VMware environment in the DR location.
On our schedule configuration, we can choose to run the job on demand or have it run daily/weekly. Also, we can choose to Run after another job, which we can use to kick off the replication job after the production backup job if we wish.
The Retention configuration allows us to define how many recovery points we want to have available to us for the replication VM. For the VMware VM that is replicated to the target environment, we will see VMware snapshots that represent each recovery point in time.
On the last configuration page, we setup our Options including the job name, app-aware mode, change tracking, network acceleration, screenshot verification, etc.
If we select the Advanced options we have even more configuration selections we can make. We can control or change the default -replica extension if we want, run Pre and Post Actions as well as additional application aware features.
Once the replication job has been run, we will see the resulting replicated VMware VM created in our target DR VMware environment.
Additionally, if we take a look at the resulting VM, we will see the snapshot that has been created for the first recovery point. Once we reach the limit of the retention value we set in the Retention configuration, the oldest snapshot is rolled off to make way for the newest snapshot that gets created.
Using the Replication feature in the Multi-tenant configuration of NAKIVO Backup & Replication, a complete DR-as-a-Service (DRaaS) solution can be provided to multiple tenants. Again, each tenant is unaware of the backups, restores, replications, etc. of other tenants being managed by the NAKIVO Backup & Replication Multi-tenant Director.
NAKIVO Backup & Replication Multi-tenant configuration provides a powerful solution for business units, branch offices, departments, and other compartmentalized business units managed by a central infrastructure hierarchy. Additionally, Managed Services Providers (MSPs) have a powerful solution to provide granular turnkey solutions to tenants who are interested in Backup-as-a-Service (BaaS) or DR-as-a-Service (DRaaS). The NAKIVO Backup & Replication interface is extremely intuitive and powerful. The ease and intuitive nature of the interface will dramatically cut any costs related to training and configuration man hours for businesses using the functionality internally. These same strengths will boost MSP’s revenue who utilize NAKIVO Backup & Replication for Backup-as-a-Service and DR-as-a-Service to provide backup, restore, and disaster recovery services to clients.