Data collection is at the heart of Capacity Advisor
and a task is created during configuration to automatically collect utilization
data from all licensed VSE resources added to HP SIM. (See “First Data Collection (or the Automated Nightly Collection)”.)
HP recommends that once you have become familiar
with using Capacity Advisor, you should review this scheduled task
to understand what it is doing and make sure that it fits your needs. This automated data collection task gathers historical data from
all your systems so that the data is available when you need it for
analysis.
Data Collection Infrastructure |
 |
In the data collection infrastructure, each component
plays a role, as shown in Figure 2-1. It all begins with data collection.
| 1 | Use the web browser to work with Capacity Advisor
and exploit its features. |
| 2 | Scenario data is stored automatically in the scenario
database. |
| 3 | Use the scenario editor to identify workloads
and systems for which to collect data. |
| 4 | Use the Report Generator to create reports to
examine. |
| 5 | The Utilization Calculator uses historical data
collected over time to create reports. |
| 6 | You can import data (HP OVPA and HP PMP) into
the historical database for analysis. |
| 7 | Automatic data conversion occurs when importing data
into the Capacity Advisor database. |
| 8 | Historical data is kept on the managed systems
for 30 days and for two years on the Central Management Server (CMS). |
| 9 | VSE data on systems of interest is available to
the Capacity Advisor Data Collector. |
| 10 | The Data Collector gathers data from the VSE database
and includes it in the historical database. |
| 11 | The Utilization Provider enables use of the Data Collector. |
Collecting Data for a Workload with a HP
Serviceguard Package
Starting with VSE Management Software version
3.0, you can associate a VSE-monitored workload with a Serviceguard
package. This association will allow VSE Virtualization Manager to
show workloads moving from one system to another within minutes of
the Serviceguard migration. It will also allow Capacity Advisor to
show an uninterrupted history of utilization data for a workload across
these migrations.
Associating VSE monitored workloads and Serviceguard
packages requires that Virtual Vault has been installed on the Central
Management Server (CMS) and that the corresponding version of the
Utilization Provider has been installed on all member systems of the
Serviceguard cluster. All nodes of the cluster must be running the
appropriate version of the Utilization Provider. For specific version
information, see the HP Systems Insight Manager screen: Help About HP Systems Insight Manager.