Configuring Operations Manager agent

KB ID: 1026
Product: Veeam Management Pack for Microsoft System Center | Veeam Management Pack 6.0 | Veeam Management Pack 6.5 | Veeam Management Pack 7.0 | Veeam Management Pack 8.0 | Veeam Management Pack 9.0
Published: 2011-07-14
Last Modified: 2020-11-17
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Challenge

No performance data regarding VMware objects is available in SCOM or gaps or dotted lines are visible in Performance views.

Cause

If the collection is properly configured, but performance data is missing from the Operations Manager console, the issue may be related to the Health Service's configuration. The collector sends a significant amount of data to the Health Service - more than it normally receives when configured to monitor just the node where the Health Service is deployed. As a result, it is necessary to configure the Health Service to have additional space set aside to receive the incoming data from the collector. Without these adjustments, the Health Service can become overwhelmed and the cache may need to be cleared.

Solution

There are two ways to configure the agent: automated (available since version 5.5) and manual. Below are the steps to configure either option:

Automated configuration of the Health Service

Run the task for each collector system in your environment. This task is included in Veeam Management Pack and sets the registry entries for OpsMgr agent  or Management Server to maximize efficiency when processing large data volumes as a proxy. The task name and location have changed between versions of the Management Pack, so the instructions are specific to the version that you have installed:

 

Version 6.x and later

After discovery of collector services is complete in Ops Mgr, you should see the collector servers listed under the Veeam Collector s > _Veeam Collectors view. The task should run automatically when the collector is installed, but to run it again at any time later with the following instructions:

  1. Open the Monitoring pane of OpsMgr console
  2. Select the Veeam for VMware > Veeam Collectors >  _Veeam Collectors view
  3. Select the collector system
  4. From the Actions pane, select task Veeam VMware Collector Service Tasks > Configure Health Service
  5. Run this task against each collector system

Note: The task will cause the Health Service to restart. Also, the values (listed below) are the default base values. If they values in the registry are already higher than the ones associated with the task, they will not be lowered by the task. In addition, you have may increase these values by editing the parameters before running the task, if it is necessary to increase these values beyond the default.


Manual configuration of the agent

To configure the agent manually, it is necessary to create/change certain keys in the registry on the collector system. All of the settings below as DWORD values with the data expressed in decimal format (please note that the registry editor defaults to hexadecimal).

Registry Key: HKLM\SYSTEM\CurrentControlSet\Services\HealthService\Parameters\

Registry Key: HKLM\SYSTEM\CurrentControlSet\Services\HealthService\Parameters\Name Value
Persistence Cache Maximum 102400
Persistence Checkpoint Depth Maximum 104857600
Persistence Version Store Maximum 20480
State Queue Items 20480

Note: If the State Queue Items entry does not already exist, it should be created as a 32-bit DWORD value.


Registry Key: HKLM\SYSTEM\CurrentControlSet\Services\HealthService\Parameters\Management Groups\<GroupName>

MaximumQueueSizeKb 204800


The changes to the registry will take effect when the Health Service on the collector system is restarted.

More information

Please note that if the OpsMgr agent on any Collector server is repaired or reinstalled, then the above task should be run again.
Click here to send feedback regarding this KB, or suggest content for a new KB.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.