Not all virtual environments are alike, the default out-of-the-box configuration of the virtual appliance is not necessarily best suited to environments of all sizes, and those particularly large environments may want to consider adjusting some of those default settings for optimal performance.  To take advantage of the features that have been added to VMAN over the last several releases requires Orion integration, which makes correctly configuring VMAN extremely important for performance and scalability. The VMAN Sizing Guide was created to assist with the preliminary setup and configuration of both the Virtualization Manager appliance and the integrated Orion server. 

 

To access the guide click here.

 

The the following items are addressed based on the number of VMs to be polled.

 

·       Memory, CPU, and storage considerations for the VMAN appliance

·       Memory, CPU, and storage considerations for the Orion server when integration is enabled

·       Identify when federated pollers are needed

·       Identify when to deploy Orion APEs to distribute the workload when integration is enabled

·       Advanced fine tuning of the VMAN appliance for Optimal performance

·       Necessary hotfix install version to solve integration issues

·       Fixes for database size issues

 

 

The guide is organized into small, medium, and large deployment recommendations to help you determine the starting configuration size for your VMAN and Orion deployment. Not all possible scenarios are included in this document, so consider the recommendations in this document as guidelines.  This is not an exhaustive list of all the fine tuning and performance tweaks that can be made, if you are still having performance issues than please reach out to your sales engineer or support contact.  They should be able to walk you through some advance tuning recommendations that would be specific to your virtual environment. 

 

Click the following  button for the VMAN Sizing Guide.

VMAN Sizing Guide.png