Managing MaxDeletedHosts

Products

• Carbon Black App Control

Issue/Introduction

• By default, when an Agent is deleted the Server will still retain some information for this Agent, until the value specified for MaxDeletedHosts is reached.
• During the nightly maintenance, the Server will delete this additional information for any hosts in excess of this value, based on the oldest deleted date.
• Typically it is not necessary to adjust this number, though environments with high machine turnover (such as non-persistent VDI) may benefit from adjusting the value.
• In some instances, the additional pruning may also help slightly reduce database usage/growth.

Environment

• App Control Server: All Supported Versions

Resolution

Finding Machines Eligible For MaxDeletedHosts

The attached script (MaxDeletedHostsPruneScope.sql) can be used to determine the number of hosts that meet current and proposed criteria for MaxDeletedHosts. Additionally, it will include which machines would be pruned under a proposed change.

1. Run SQL Server Management Studio as the Carbon Black Service Account.
2. Paste the contents of the SQL Script into a new query.
3. Edit line 6 accordingly, example:

   DECLARE @ProposedMax INT = 1000;

4. Execute the script and review the results.

Configuring MaxDeletedHosts

1. Log in to the Console and navigate to https://<ServerAddress>/shepherd_config.php
2. Locate the Property MaxDeletedHosts
3. Change the Value accordingly (ex: 1000) and save.
4. Changes will apply during the next nightly maintenance.

Additional Information

• By default, MaxDeletedHosts is 1000000
• Reducing the size or growth of the DAS Database
• Automatically Delete Offline Agents