We're slowly building out the reporting infrastructure for more detailed analytics of our environment. To the best of my current knowledge, we've setup the requisite bits and bobs for the IndexServer, so that we can perform the types of scans/monitoring.
Today, when trying to set things up so that the Inferred Ownership Report could run, I'm getting the following message back: "No cores available for selected policies" and I can't find anything that gives me a good idea where I might need to increase the cores (presuming that I actually do need more cores): The Windows file server in question? The CommServ? the Index Server?
Some background - CV 11, SP 17.16 on Windows 2012 R2
The IndexServer has the following roles: Data Analytics, Log Monitoring, Review Set, NAS Array Reporting, NFS Index, Filesystem Index, Virtual Machine, ActiveDirectory Index (we may add more as we explore the features and react to corp. needs).
The monitoring policy was created to monitor a single Windows File server (and yes, CollectStreamStats is enabled, and Catalog ACL is set for the subclients of the defaultBackupSet for this client system). The basic scan of the fileserver was done as a one off - as I said, we're slowly building this out, so aren't turning everything over to any automatic schedules.
Also: Full disclosure - I have 2+ decades of NetBackup background, and about 1/2 a percent of that time with CommVault, so terminology is something I trip over regularly at the moment.