1-800-691-1991 | 9am - 8pm ET

How to restrict virtual infrastructure scope for data collection


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.


To to restrict or exclude objects from Veeam ONE's collection scope, the objects must be restricted in both Veeam ONE Monitor and Veeam ONE Reporter.

To exclude objects from Veeam ONE Monitor's collection scope:
  1. In the Veeam ONE Monitor Console, select Options > Server Settings.
    User-added image

  2. In the Server Settings window, switch to the Monitored Objects tab then select Virtual Infrastructure and click Expand at the bottom of the window.

  3. With the environment topology expanded, clear check boxes for any hosts that you want to exclude from Veeam ONE Monitor's collection scope.

     User-added image

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.

  1. In Veeam ONE Reporter, open the Configuration view then select the Collection Jobs screen.

  2. Select the collection job from which objects should be excluded and click Edit.

  3. In the Collection Job Wizard, switch to the Servers section, select the entry from which objects should be excluded and click Edit.
    User-added image

  4. In the VMware Server window, click the '...' button next to the Collection Scope field.
    User-added image

  5. 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.
    User-added image

  6. 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.

     User-added image

  7. 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.

     User-added image

  8. 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.

User-added image

More information

If you have any questions or problems, please contact Veeam Support at
Veeam ONE
Last Modified:
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.


error icon

Oops! Something went wrong.

Please go back try again later.