Page tree

Unsupported content


This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Infrastructure Management can be installed and run on a VMware virtual machine (VM).

When deploying the product on VMs, be aware that additional overhead exists because resources are shared across VMs. The same performance that is possible running applications on a physical computer is not possible on VMs. However, VMs offer more flexibility and ease of administration for some aspects, such as high availability and backups. 

Consider the following VMware best practices:

  • The Integration Service node(s) should be excluded from VMware HA if you are using the out-of-the-box active/active configuration, because PATROL Agents will automatically switch to their secondary location if the primary location is interrupted for any period of time.
  • Use only two to three virtual machine snapshots in a chain. BMC recommends that you avoid using the single snapshot for more than 72 hours. You can either delete the snapshot or consolidate it. For more information, see

  • Enable NIC teaming.

  • Use a VMware paravirtual NIC adapter for optimized performance.

  • For ESX storage, ensure that you use dedicated disk storage all virtual machines; avoid sharing disk storage. See Hardware requirements to support small, medium, and large environments for storage requirements.

  • Configure Jumbo frames for the storage adapter.

  • Reserve the resources that are allocated for the virtual machine on which the BMC applications are installed.
  • Periodically monitor the CPU usage of the host.

Infrastructure Management high availability deployment and best practices