Physical machines can be monitored from multiple sites within a single client engagement. Here is how you should determine whether to deploy a single or multiple instance of the Lanamark Explorer for data collection:
- Create a list of all sites
- Determine the number of physical machines per site
- Sort sites in descending order by the number of machines
- Label sites with more than 25 machines as primary sites and those with fewer than 25 machines as secondary sites
Data Collection Sites
Lanamark Explorer should be deployed at each primary site. Machines at each secondary site should be monitored from a Lanamark Explorer deployed at a primary site over the WAN, provided there is sufficient bandwidth and little latency.
Primary Sites (25 or more machines)
We recommend deploying the Lanamark Explorer at each site containing more than 25 machines to avoid burdening WAN connections with data collection traffic. A separate data feed will be established from each Lanamark Explorer deployment.
Secondary Sites (Fewer than 25 machines)
If a site has fewer than 25 machines and there is network connectivity from a primary site to a secondary site, then the Lanamark Explorer from a primary site can be used to profile workloads on a secondary site.
Each target system generates 250-500 KB of data during collection of inventory data and the number of concurrent inventories is limited to 20. Since each inventory operation can take several minutes, the network load from inventory ranges from 0.5 to 1.0 Mbps.
Lanamark Explorer collects 50-100 KB of data from each target system per monitoring interval. If the monitoring interval is kept at a default of five (5) minutes, data collection will result in the following network load:
- 1 machine: 0.15 to 0.3 Mbps
- 10 machines: 1.5 - 3 Mbps
- 25 machines: 3.75 - 7.5 Mbps
- 100 machines: 15 - 30 Mbps
Suppose you need to monitor sites A, B and C with 50, 200, 10 machines respectively. Let's first sort the sites by the number of machines:
- Site B: 200 machines (primary)
- Site A: 50 machines (primary)
- Site C: 10 machines (secondary)
Sites B and A have more the 25 machines so we would make them primary sites and deploy a Lanamark Explorer instance into each one. Site C has only 10 machines so we can classify it as a secondary site.
Site C can be monitored from either Site A or B. We recommend making this decision based on the network bandwidth between primary and secondary sites. If network bandwidth is the same, then monitoring from the primary site with fewer machines is recommended.
Suppose Sites A and B have the same bandwidth to Site C, we would choose to monitor Site C from site A since it only has 50 machines.
Note: data in the data warehouse cannot be changed. In case of duplicates, which is usually the result of online collection and offline snapshot (with the same data) import,
use Excel spreadsheet to find duplicates and get rid of the duplicated data.