Backup at Master Site
In this scenario, tenant VMs are running at the master site and the backing up of tenant VMs is also performed at the master site.
A service provider runs VMs of customer A and customer B in the service provider’s datacenter. The Service Provider seeks to offer Backup-as-a-Service to both customers. The customers should be able to recover their files and emails through a self-service interface without being able to see each other’s backups.
The deployment diagram for the above scenario is as follows:
To deploy the above scenario, perform the following steps:
- Install the Director in multi-tenant mode at the master site.
- Install at least one Transporter at the master site.
- For each tenant, prepare a separate folder at the master site for creating a Backup Repository.
The implementation of the above scenario requires that the following connections be available:
|A||Connection from the machine on which the Director is installed to the machine on which the Transporter is installed. The port used for communication with the Transporters (9446 by default) is open in firewalls.|
|B||Connection from the machine on which the Director is installed to vCenter servers and ESXi hosts that run source VMs. The port used for communication with vCenter servers and ESXi hosts (443 by default) is open in firewalls.|
|C||Connection from the machine on which the Transporter is installed to vCenter servers and ESXi hosts running source VMs.|
|D||Connection from the machine on which the Transporter is installed to the folders where tenant Backup Repositories will be created.|
For security purposes, a VPN connection should be established between the master site and remote sites.