In some environments, it may not be necessary to monitor the entire virtual infrastructure. However, Veeam ONE automatically monitors all objects contained within a vCenter Server, ESX(i) host, or Hyper-V host when the server is added to Veeam ONE's scope.
Restricting the virtual infrastructure scope may also be helpful if you receive the error 'License Socketing Exceeded' and do not have enough licenses to cover all monitored virtual infrastructure servers.
In the Veeam ONE Monitor Console, select Options > Server Settings.
In the Server Settings window, switch to the Monitored Objects tab then select Virtual Infrastructure and click Expand at the bottom of the window.
With the environment topology expanded, clear check boxes for any hosts that you want to exclude from Veeam ONE Monitor's collection scope.
To exclude objects from Veeam ONE Reporter's collection scope:
Note: In Veeam ONE Reporter, objects may only be excluded/restricted down to the cluster level.
In Veeam ONE Reporter, open the Configuration view then select the Collection Jobs screen.
Select the collection job from which objects should be excluded and click Edit.
In the Collection Job Wizard, switch to the Servers section, select the entry from which objects should be excluded and click Edit.
In the VMware Server window, click the '...' button next to the Collection Scope field.
In the Select node window, highlight the datacenter or cluster that you want to include in the collection job then click OK. In the VMware Server window, click Update.
Once the first entry has been edited in the Collection Job Wizard, click Add in the Servers section of the wizard and repeat steps 3 - 5 until all required datacenters and/or clusters are added to the collection job, leaving out the datacenters and/or clusters to be excluded from the collection.
If there are individual hosts in a cluster that you also want to include in Veeam ONE Reporter's collection scope, but you do not want to add the entire cluster containing these hosts, you may also add these hosts individually using the hostname/IP of the host and the root user credentials for the host within the same collection job. Simply add the host directly in the same way as the previous clusters or datacenters were added.
If you are receiving licensing warnings in your collection job session logs, open the Configuration > License screen and in the Used Sockets section revoke the license sockets for hosts that you have excluded from the collection scope.
Once the license sockets have been revoked, run the collection job then check the license screen again to ensure no other objects need to be excluded from the collection scope.