The App Control Server should be deployed on a single computer that will house both the App Control Server and SQL Server. The following table lists the requirements for this computer.

Endpoints SQL Server Edition Hardware Required Database Storage DAS (Locally attached) PCIe Flash GB / 1K EPTS

Note 2

RAM (GB) CPU Cores

Note 1

SQL 2016 & Earlier SQL 2016 SP1 & Later

Note 4

Disks RAID
Up to 100 Express 4 2 20 GB

Note 3

20 GB

Note3

2 1 n/a
101 – 250 Standard 12 2 55 GB 50 GB 4 1+0 n/a
251 - 500 16 2 100 GB 90 GB 4 1+0 n/a
501 – 1,000 16 4 175 GB 150 GB 6 1+0 n/a
1,001 – 1,500 16 4 300 GB 260 GB 6 1+0 n/a
1,501 – 2,000 16 4 500 GB 440 GB 8 1+0 n/a
2,001 – 5,000 32 6 1 TB 900 GB 8 1+0 n/a
5,001 - 10,000 48 8 1.2 TB 1 TB 12 1+0 n/a
10,001 – 20,000 48 8 2 TB 1.75 TB 14 1+0 50
20,001 – 30,000 128 16 3 TB 2.5 TB 24 1+0 50
10,001 - 40,000 Enterprise 64 12 2 TB 2 TB 12 1+0 20
40,001 - 80,000 96 16 4 TB 4 TB 14 1+0 20
80,001 - 160,000 96 16 8 TB 8 TB 22 1+0 20

Notes:

1 CPU core requirements are based on physical, not hyper-threaded cores. Two CPUs might be necessary to reach required number of cores.

2 PCIe sizing requirement is given in GB per 1K endpoints.

3 Database storage for SQL Express includes 10 GB for data file (maximum limit for SQL Express) and additional 10 GB for the log file.

4 Index compression will only be enabled for new installs. Upgrades should reference the SQL 2016 and Earlier column.

Important: You should test your architecture using the CBPTest Disk Performance Tool available on the user exchange.

Associated with the storage sizes listed above are the following caveats:

  • By default, the App Control Server saves no more than four weeks of events and no more than ten million events. Increasing these defaults will increase the size of the database. Under normal circum­stances, the largest portion of the database will be taken up with storage of instances of files on endpoints.
  • The App Control Server carries out two scheduled database tasks described in the document VMware Carbon Black App Control SQL Server Configuration Guide. Stopping these tasks can cause the database to grow beyond the sizes listed above.

The steps listed under “Database Growth” in the document VMware Carbon Black App Control SQL Server Configuration Guide are being followed.

Notes on SQL Server Edition

Deployments with 10,000 to 30,000 endpoints have a choice of SQL Server editions. When using SQL Server Standard, keep the following points in mind:

  • With over 20,000 endpoints, SQL Server 2014, 2016, 2017, or 2019 must be used. Earlier versions of SQL Server Standard do not support enough RAM or CPU Cores.
  • Unlike SQL Server Enterprise, SQL Server Standard prior to SQL Server 2016 SP1 does not use data compression. This is why it needs more memory and disk space.
  • On SQL Server Standard, App Control achieves equivalent performance processing file inventory compared to SQL Server Enterprise, but the App Control console can be 30% slower and some database maintenance tasks such as rebuilding indexes and statistics will be slower. This can be mitigated by placing the database on faster storage hardware.

Two-tier Deployment Architecture

Here are the requirements for a two-tier installation of App Control where the App Control Server and SQL Server reside on separate hardware:

  1. For the SQL Server hardware, use the single-tier table above.
  2. For the App Control Server hardware, use the following table:
    Endpoints Hardware
    RAM (GB) CPU Cores Note 1
    Up to 1,000 4 2
    1,001 - 80,000 8 4
    Above 80,000 16 8

    Note 1: CPU core requirements are based on physical, not hyper-threaded cores. Two CPUs might be necessary to reach required number of cores.

  3. Make sure that the network latency between the App Control Server and SQL Server is 0.7 ms or lower. The freeware utility hrPing or similar can be used to validate the latency.
  4. The SQL server instance and underlying database storage has to be dedicated to the App Control Server