vRealize Business for Cloud provides end-user transparency in the costs that are associated with operating workloads. vRealize Business shows provisioning costs 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 according to the requirements of an organization. See Logical Design of vRealize Automation and Physical Design of vRealize Automation.

Table 1. Resource Requirements for vRealize Business per Virtual Machine
Attribute Specification
Number of vCPUs 4
  • 8 GB for a server
  • 2 GB for a data collector
vRealize Business function Server or data collector
Table 2. Design Decision on vRealize Business
Decision ID Design Decision Design Justification Design Implication
SDDC-CMP-047 Deploy vRealize Business as part of the Cloud Management Platform and integrate it with vRealize Automation. You introduce tenant and workload costings. You must deploy more appliances: for the vRealize Business server and for data collectors.
SDDC-CMP-048 Use the default vRealize Business appliance size of 8 GB. For the vRealize Business data collectors, select a reduced memory size of 2 GB. The default appliance size of vRealize Business supports the design objective of 10,000 VMs.

Data collectors do not run server service, and can run on 2 GB of RAM.

SDDC-CMP-049 Use the default vRealize Business reference costing database. The default reference costing is based on industry information and is periodically updated. Default reference costing might not accurately represent actual customer costs. The vRealize Business server requires Internet access to periodically update the reference database.
SDDC-CMP-050 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 must be regionally local to the resource which they are configured to collect data from. Because this design supports disaster recovery, the data collectors can reside in Region A and Region B. If the environment does not have disaster recovery support, you must deploy an additional appliance for the remote data collector, although the vRealize Business server can handle the load on its own.
SDDC-CMP-051 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 migrates with vRealize Automation. None.
SDDC-CMP-052 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 extra Layer 3 hop through an NSX Edge device.