In my previous article, I provided an overview of How to Select Scopes from Other Domains. Today, we'll be exploring the use of shared data locations to improve collection times.
Each discovery cluster can be configured to access an optional shared location for discovery data. If you have a lightly-loaded SQL Server that is physically close to your Enterprise Reporter nodes, you may find that a shared data location is not required. On the other hand, if network traffic is high and your SQL server is under a heavy load, or is physically distant from the nodes in the cluster, a shared data location will produce faster results.
As data is collected by each of the cluster’s nodes, it is compared to previously-collected data and only changed data is subsequently stored. If you do not use a shared data location, the comparison is done directly on the SQL Server. If you use a shared data location, the comparison occurs in temporary files on the share. So, if the comparison of the existing data is close to where new data is being collected and stored, your discoveries will be faster.
When creating the cluster, you can select your shared data location. Ensure the node credentials have read and write access to this file share.
So the answer to the question is yes, you might want to try using a shared data location to see if your discoveries can run faster.
For more information on discoveries, see the Enterprise Reporter Configuration Manager User Guide.
In my next installment, I will discuss collecting group members in discoveries other than the Active Directory discovery.