vRealize Business for Cloud provides end-user transparency in the costs that are associated with operating workloads. A system, such as vRealize Business, to gather and aggregate the financial cost of workload operations provides greater visibility both during a workload request and on a periodic basis, regardless of whether the costs are "charged-back" to a specific business unit, or are "showed-back" to illustrate the value that the SDDC provides.

vRealize Business integrates with vRealize Automation to display costing during workload request and on an ongoing basis with cost reporting by user, business group or tenant. Additionally, tenant administrators can create a wide range of custom reports to meet the requirements of an organization.

Table 1. vRealize Business for Cloud Standard Design Decision

Decision ID

Design Decision

Design Justification

Design Implication


Deploy vRealize Business for Cloud as part of the cloud management platform and integrate it with vRealize Automation.

Tenant and Workload costing is provided by vRealize Business for Cloud.

Additional appliances need to be deployed to handle for vRealize Business for Cloud and remote collectors.


Use default vRealize Business for Cloud appliance size (8GB). For vRealize Business for Cloud remote collector, utilize a reduced memory size of 2GB.

Default vRealize Business for Cloud appliance size supports up to 10,000 VMs

Remote Collectors do not run server service, and can run on 2GB of RAM.



Use default vRealize Business reference costing database.

Default reference costing is based on industry information and is periodically updated.

Default reference costing might not accurately represent actual customer costs. vRealize Business Appliance requires Internet access to periodically update the reference database.


Deploy vRealize Business as a three-VM architecture with remote data collectors in Region A and Region B.

For best performance, the vRealize Business collectors should be regionally local to the resource which they are configured to collect. Because this design supports disaster recovery, the CMP can reside in Region A or Region B.

In the case where the environment does not implement disaster recovery support, you must deploy an additional appliance, the one for the remote data collector, although the vRealize Business server can handle the load on its own.


Deploy the vRealize Business server VM in the cross-region logical network.

The vRealize Business deployment depends on vRealize Automation. During a disaster recovery event, vRealize Business will migrate with vRealize Automation.



Deploy a vRealize Business remote data collector VM in each region-specific logical network

vRealize Business remote data collector is a region-specific installation. During a disaster recovery event, the remote collector does not need to migrate with vRealize Automation.

The communication with vCenter Server involves an additional Layer 3 hop through an NSX edge device.

Table 2. vRealize Business for Cloud Virtual Appliance Resource Requirements per Virtual Machine



Number of vCPUs



8 GB for Server / 2 GB for Remote Collector

vRealize Business function

Server or remote collector