OPERATIONAL DEFECT DATABASE
...
...
BugZero found this defect 2047 days ago.
Decrease the OpsMgr Health Service load caused by datastore monitoring process.
Since the datastore monitoring job currently cannot be split among several Veeam VMware Collectors, the amount of processed data may overload the Health Service in large VMware environments. Tip: To track the number of workflows running in the OpsMgr Health Service, you can use the Veeam MP for VMware > Veeam Collectors > Performance Views > Workflow Count view in the OpsMgr console. The number of workflows will be also displayed in the description of the Veeam VMware Collector: Health Service recommended workflow load monitor fired as soon as the recommended maximum number of OpsMgr Health Service workflows is exceeded.
To resolve the issue, configure Veeam MP for VMware discovery rules in OpsMgr in a way that will allow you to split the datastore monitoring job among several Health Services. To do that, deploy an additional Veeam MP for VMware instance (the Veeam Virtualization Extensions Service, Veeam Virtualization Extension UI and Veeam VMware Collectors). Before you apply the solution, mind the following: 1. The version of the Veeam Virtualization Extensions Service (VE Service), Veeam Virtualization Extension UI (Veeam UI), Veeam VMware Collector (Collector) and Veeam Management Packs must be the same for both the existing and new Veeam MP for VMware deployments. 2. The accounts used to install and use Veeam MP for VMware must be granted the same privileges in both deployments. For more information, see the Veeam MP for VMware Installation Guide, section Accounts and Privileges. 3. The solution described below must not affect any setup or patching procedures. 4. If you want to use some of your existing Collectors for the new Veeam MP for VMware deployment, you must reinstall these Collectors and connect them to the new VE Service during the setup. Case #1. There are several large vCenter Servers in your VMware environment. In this case, deploy an additional Veeam MP for VMware instance (the VE Service, Veeam UI and Collectors) and assign a number of vCenter Servers to the new Collectors. This solution will decrease the load on the OpsMgr Health Service. For more information on how to install Veeam MP for VMware, see the Veeam MP for VMware Installation Guide, section Installing Veeam MP for VMware. Case #2. There is a large number of datastores on one vCenter Server. In this case, deploy an additional Veeam MP for VMware instance and manually split datastores processed by the datastore monitoring job between several Health Services. Note that this solution will decrease only the OpsMgr Health Service load — it does not affect the load on Collectors. 1. Deploy the 2nd instance of Veeam MP for VMware (the VE Service, Collector and Veeam UI components). For more information, see the Veeam MP for VMware Installation Guide, section Installing Veeam MP for VMware. 2. In the Veeam UI, set the EnableVMDiscovery parameter value to False for all Collectors installed in the 2nd deployment. For more information, see the Veeam MP for VMware Operations Guide, section Collector Settings. 3. In the OpsMgr console, create 2 groups for Collectors and 2 groups for Veeam VMware datastore containers. Add members to each group explicitly, or configure rules to enable dynamic membership. If you decide to add members to groups explicitly, it is highly recommended to set the VE Service LoadBalanceOnCollectorRecovery parameter value to False. For more information, see the Veeam MP for VMware Operations Guide, section Extension Service Settings. a. [For Collector groups with dynamic membership] Create 2 groups for the Veeam VMware Collector Service object. Configure a rule that will automatically distribute Collectors between these groups based on the name of the VE Service to which each Collector is connected. Specify the required VE Service name as the Extension Service property value in the Create Group Wizard – Query Builder. Alternatively, use the following formula to populate membership in each group: ( Object is Veeam VMware Collector Service AND ( Extensions Service Equals {VE Service name} ) AND True ). Note: If you later add a new Collector to your infrastructure, no additional actions are required. The new Collector will be automatically included in one of the created groups according to the configured rule. b. [For Collector groups with explicit members] Create 2 groups for the Veeam VMware Collector Service object. In the Create Group Wizard – Object Selection, manually add objects to these groups based on the name of the VE Service to which each Collector is connected. Note: If you later add a new Collector to your infrastructure, you will have to manually add the new Collector to one of the created groups. c. [For datastore container groups with dynamic membership] Create 2 groups for the Veeam VMware Datastore Container object. Configure a rule that will automatically distribute datastore containers between these groups based on the name of the VE Service to which each Collector gathering statistics on the containers is connected. Specify the Veeam VMware Collector Service object and the required VE Service name as the Extension Service property value in the Create Group Wizard – Query Builder. Alternatively, use the following formula to populate membership in each group: ( Object is VMware Datastore Container AND ( Display Name Contains datastore ) AND True ) AND ( Object is Veeam VMware Collector Service AND ( Extensions Service Equals {VE Service name} ) AND True ) ). Note: If the number of datastores managed by the vCenter Server exceeds 100, the Collector that monitors datastores will create a new datastore container, and this container will be automatically included in one of the created groups according to the configured rule. d. [For datastore container groups with explicit members] Create 2 groups for Veeam VMware Datastore Container object. In the Create Group Wizard – Object Selection, manually add objects to these groups based on the name of the VE Service to which each Collector gathering statistics on the containers is connected. Note: If the number of datastores managed by the vCenter Server exceeds 100, the Collector that monitors datastores will create a new datastore container, and you will have to manually add this container to one of the created groups. 4. In the OpsMgr console, configure the following overrides. For more information on how to work with overrides, see Microsoft Docs. To specify datastore names explicitly, use a comma-separated list (for example: Datastore01, Datastore02). To exclude a group of datastores, use the asterisk character (for example: ds1*, ds2*). a. For the datastore container group created for the 1st VE Service, override the ExcludeDatastoreByDatastoreName parameter value for the Veeam Stage 2 - Datastore discovery rule. Provide names of datastores that you want to exclude from monitoring for the 1st deployment. b. For the Collector group, created for the 1st VE Service, override the ExcludeDSRelByDSName parameter value for the Veeam Stage 2 - Virtual Machine discovery rule. Provide names of datastores that you want to exclude from monitoring for the 1st deployment. c. For the datastore container group, created for the 2nd VE Service, override the ExcludeDatastoreByDatastoreName parameter value for the Veeam Stage 2 - Datastore discovery rule. Provide names of datastores that you want to exclude from monitoring for the 2nd deployment. d. For the Collector group, created for the 2nd VE Service: o Override the ExcludeDSRelByDSName parameter value for the Veeam Stage 2 - Virtual Machine discovery rule. Provide names of datastores that you want to exclude from monitoring for the 2nd deployment. o Set the Enabled parameter value to False for the Veeam Stage 2 – Host components discovery rule. o Set the Enabled parameter value to False for the Veeam Stage 2 - Virtual Machine discovery rule. Important! The list of datastore names must be the same for both the Veeam Stage 2 - Datastore discovery and Veeam Stage 2 - Virtual Machine discovery rules. 5. To verify whether you configured the overrides correctly, open Veeam Stage 2 – Host components discovery properties, switch to the Overrides tab and check that all parameters in the Overrides Summary list are set to False. Note: If you later add a new datastore to the vCenter Server, you will have to reconfigure the Veeam Stage 2 - Datastore discovery and Veeam Stage 2 - Virtual Machine discovery rules to exclude this datastore from monitoring for one of the deployments. 6. On the VMware Servers tab of the Veeam UI, for the 1st deployment, clear the check box next to the vCenter Server in the server hierarchy and wait until its objects disappear from the VMware topology in the OpsMgr console. Then select the check box again. 7. On the VMware Servers tab of the Veeam UI, for the 2nd deployment, select the check box next to the vCenter Server.
After you apply the solution, Veeam MP for VMware analysis and performance reports will have the following issue: each datastore included in both deployments will have a duplicate in the report scope list. This is a known issue that does not affect report functionality.
