VMware Data Services Manager requires access to a vCenter Server system and one or more clusters or ESXi hosts. Each host running VMware Data Services Manager must meet certain hardware and software requirements.
Refer to the Release Notes for information about the server platforms, browsers, and data services supported by this release of VMware Data Services Manager.
VMware Data Services Manager is supported on VMware vSphere 6.7 and later. The following table lists information about the components of vSphere required and the versions supported.
|vCenter||6.7 and 7.0|
|ESXi||6.7 and 7.0|
|VMFS||5 and 6|
|PostgreSQL||10.18.0, 10.19.0, 11.13.0, 11.14.0, 12.8.0, and 12.9.0|
|MinIO/AWS S3||Not Applicable|
|VMC||SDDC Version 1.14v6|
The type of environment in which it will run, and the volume of services that it will manage, will determine the amount of resources that are configured for a Provider VM or an Agent VM. The default configuration for the VMs follows:
|Provider VM||Default configuration||16 GB||8 vCPU||736 GB (thin provisioning)|
|Agent VM||Default configuration||16 GB||8 vCPU||668 GB (thin provisioning)|
The provisioning user specifies the amount of memory and CPU resources for any database that they deploy. These amounts may be bounded by the VM Configuration Mode in place for the organization to which the user belongs.
VMware Data Services Manager has no specific storage requirement for its deployments. The environment admininstrator can choose to configure the number and types of datastores. A VMware Data Services Manager deployment uses the datastores available.
VMware Data Services Manager requires an S3-compatible local and a cloud object storage solution (for example, AWS or MinIO).
If all of the six repositories - Provider Repo, Provider Log Repo, Provider Backup Repo, and Agent Local Storage and Cloud Storage - are on the same server, a minimum of 100GB capacity of S3-compatible local and a cloud object storage is required. The recommended size of the S3-compatible local and a cloud object storage depends on the size of data backups and retention policy.
Before you deploy VMware Data Services Manager, configure and deploy S3-compatible local and a cloud object storage and create the following buckets:
These endpoints must be resolvable by the DNS server specified at the time of Provider VM deployment.
You can deploy a basic configuration of one Provider and one VMware Data Services Manager Agent in a single vCenter cluster. One VMware Data Services Manager Agent can manage one vSphere entity, such as a vCenter cluster or Resource pool. Neither can multiple VMware Data Services Manager Agents manage the same vSphere entity nor can a single VMware Data Services Manager Agent manage multiple vSphere entities.
Secure, reliable operation of VMware Data Services Manager depends on a secure, reliable network that supports DHCP, a network time service, and other services.
VMware Data Services Manager requires a minimum of two dedicated subnets that have access to DHCP, DNS, and NTP services. DNS resolution is required for application network of database VMs. DNS resolution is mandatory only for database clusters. If not already available, ensure that you have installed a DHCP server on a VM in the vSphere cluster or VMC cluster. Configure the two subnets so that IP addresses are assigned by DHCP for each provisioned database.
If you are deploying in an environment with internet connectivity, ensure that your network is able to access VMware Tanzu Network and cloudfront.net. Tanzu net uses Cloudfront.net for storage purposes. Your environment must meet the following network requirements before you begin installing VMware Data Services Manager.
VDS and N-VDS port groups that should be available to host components of VMware Data Services Manager are:
The choice of port group type depends on the appliance to which it is connected:
Though the Control Plane network and the Application network for databases get their IP addresses from the DHCP server, the IP addresses for Management network and the Control Plane network for Provider and Agent VMs are static and configured manually.
You must use the NTP network time service to synchronize the clocks of all VMware Data Services Manager deployed VMs.
The Provider VM requires two networks, one for UI or management traffic and one for control plane traffic. Route both the networks.
The Management Network and the Control Plane Network are configured when you deploy the Provider VM, and cannot be changed after deployment.
An Agent VM requires:
The Control Plane Network is configured when you deploy an Agent VM, and cannot be changed after deployment.
A database requires:
Two networks, one for management traffic, and one for access by client applications:
Access to an external network for cloud object storage.
Each NIC in a database must be configured to obtain its IP address from DHCP.
The Control Plane Network and the Application Network for a specific Onboarded Cluster are configured when you onboard the Agent with VMware Data Services Manager. When a user provisions a database that specifies the associated cluster Environment, the deployed database utilizes those networks.
VMware Data Services Manager expects that databases that it deploys reside in their own subdomain under a corporate domain. For example:
VMware Data Services Manager hosts a DNS server on every Provider VM. The Provider VM acts as a DNS for all databases provisioned in the associated Onboarded Cluster.
You can use your existing corporate DNS server to resolve database addresses by configuring the server to forward all DNS requests in the subdomain to the Provider VM DNS server.
If there is another DNS configured in your vCenter for VMware Data Services Manager, this DNS must have Forward Lookup Zone and Conditional forwarding set for each DB FQDN Suffix so that an Provider VM handles all DNS resolution for its databases.
VMware Data Services Manager assigns the IP address of a database that is provisioned by an Organization using DHCP. Agent VM generates and creates a DNS entry for a database FQDN based on the DB FQDN Suffix specified when a Provider creates the Organization.
The following diagram provides a representation of a sample network topology where:
The following ports are opened for incoming/outgoing traffic during Provider VM deployment:
|TCP (RabbitMQ Cluster)||4369||eth1|
|TCP (RabbitMQ Cluster)||25672||eth1|
The following ports are opened for incoming and outgoing traffic during Agent VM deployment:
The following ports are opened for incoming and outgoing traffic during database deployment:
|TCP (PostgreSQL)||5432||eth0 and eth1|
External Network Requirements:
|Connection From||Connection To||Type||Protocol||Port Number||NIC|
|Provider VM||S3-compatible Provider storage||http/https||TCP||eth0|
|Provider VM||VMware Tanzu Network||https||TCP||443||eth0|
|Corporate DNS||Provider VM||DNS||TCP/UDP||53||eth0|
|Agent VM||S3-compatible Agent storage (local)||http/https||TCP||eth0|
|Agent VM||S3-compatible Agent storage (cloud) (external)||http/https||TCP||eth0|
|Database||S3-compatible Agent storage||http/https||TCP||eth0 or eth1|
|Agent Onboarding UI Client||Agent VM||https||TCP||443||eth0|
|VMware Data Services Manager Console Client||Provider VM||https||TCP||443||eth0|
|End User (Terminal)||Provider VM||SSH||TCP||22||eth0|
|End User (Terminal)||Agent VM||SSH||TCP||22||eth0|
|End User (Terminal)||Database||SSH||TCP||22||eth1|
Internal Network Requirements:
|Connection From||Connection To||Type||Protocol||Port Number||(From/To) NIC|
|Provider VM||Provider VM||RabbitMQ||TCP||443||eth1|
|Provider VM||Provider VM||PostgreSQL||TCP||5432||eth1|
|Provider VM||Provider VM||RabbitMQ Cluster||TCP||4369||eth1|
|Provider VM||Agent VM||RabbitMQ Cluster||TCP||25672||eth1/eth0|