Table of Contents
Rollup and DA
Data Analytics is configured with processes that can run at scan time, scheduled or real time. There are multiple components that make up Data Analytics. In the case of a rollup, Data Translation Service and Discovery Services are the components that are most affected by a rollup for configuration purposes. Executive Report Pack can also be configured for a multi-core environment with or without a rollup.
It is recommended that Data Analytics be installed on both the rollup and child core. Updates should be kept current on both environments. It is recommended the versions of Data Analytics binaries and the content should be the same on both.
Data Translation Services
Data Translation Services will have the largest impact in a rollup environment. By default DTS will run a series of over 20 rules at scan time. Some of these can take a relatively long time to process, specifically web rules. They make take up to 30 seconds or more to retrieve warranty data. However, with the delta scanning a multi-threaded service, inventory performance on a core server is not normally effected by enabling real time scanning. However, attempting to run these processes on a rollup can take a prohibitively long time. So it is recommended that rules that affect the normal inventory of a computer take place on the child core. Do not schedule or run these rules on a rollup due to performance.
DTS also has the Software Manager service which executes the licensed software rules once a day for software detection. It is recommended that this service be enabled on the child cores and disabled on a rollup core. This automatically happens by default.
All of the inventory data that these DTS rules create will rollup: licensed software, warranty, etc. The distributed processing allowed by the child cores enables the tasks to be completed in a timely manner.
There are certain elements of DTS that are recommended to be executed on a rollup core. These are the B2B connectors and software license imports. B2B connectors will pull data from the vendors you purchase hardware and software from. Typically these purchases will effect machines on multiple cores. One of the features of B2B connectors is to create a device if they do not exist. This enables you to know when a device is ordered and if it never shows up in your environment. Since a device will only report its inventory to one core, running these connectors on multiple cores will result in multiple devices being created, inflating numbers and causing potential confusion.
Software license imports (also part of B2B connectors that include software purchases) also should only be done on rollups. Software licenses do not currently rollup, while inventory based installation information does. Also, purchases may span devices on multiple cores, so assigning licenses out to individual cores may not be the most efficient use of those licenses.
Discovery Services is also significantly affected by rollups. Discovery Services is used for several purposes: discovery of inventory data that a regular inventory scan does not gather, scanning for windows machines and adding them to regular inventory, or scanning for SNMP devices and adding them to Asset Control.
Typically scanning for additional inventory information should be done on the child cores. For example, SQL Server edition information is retrieved. This is then used by the Software Manager service when detecting software and that is recommended to only be done on child cores.
Scanning for additional Windows devices should be done on the child cores. Network scanning can utilize significant resources on the core. Attempting to scan an entire enterprise from one core could take an extremely long time. Also, executing additional DTS rules (such as warranty etc,) could take significant time and resources. Just make sure discovery ranges do not overlap so that cores are not discovering the same devices and creating duplicates in the rollup.
With 9.6, Asset Control data will now rollup, so it is no longer necessary to do all scanning on a single core for reporting purposes. This allows the significant load to be removed from the rollup and distributed to the child cores. The only caveat is to be careful not to overlap discovery ranges as this would then create duplicates on the rollup core.
Executive Report Pack
Executive Report Pack is the Data Analytics reporting engine. It can be configured to run against multiple cores and can be pointed at the rollup db but not run there. The most significant exception is the SLM Expandable Detail. These must be run on the core you wish to report from. Since software licensing is recommended to be used on the rollup core, you must run the SLM Expandable detail reports on the rollup.