Items to be designed
|
Item to be designed |
Description |
|---|---|
|
Metrics to be collected |
Of the metrics for LDEVs, MPUs, ports, parity groups, and the top 20 resources with the highest MP usage, determine which metrics are to be collected. |
|
Metric collection scope |
Determine the metric collection scope.#1
|
|
Metric collection interval |
Determine the metric collection interval from the following viewpoints:
|
|
I/O destination devices |
I/O destination devices are required for each storage system for which performance information is to be collected. Consider the following when determining the I/O destination devices:
|
|
Scan scope of the storage system |
Scan the collection range of LDEVs (excluding Non Gen'ed volumes) and I/O destination devices. |
|
Prefix of the disk configuration definition file |
Determine a prefix for each operation.#2 Prefix: 25 or fewer characters prefix |
|
SMF record type |
If you do not use the default value that is set by the system symbol &RSRTYPE, determine the SMF record type. |
|
Required memory size and dataset disk space |
Calculate the required memory size and the required disk space for the SMF dataset and for the disk configuration definition file dataset. |
- #1
- For details on how to determine the metric collection scope, see About scope of metric collection.
- #2
-
If you want to install and use MAR in the same system as Business Continuity Manager or Tiered Storage Manager for Mainframe, specify a character string different from the prefix of Business Continuity Manager or Tiered Storage Manager for Mainframe as the prefix of the disk configuration definition file. If the same prefix is used, the product might operate abnormally.
- Acquiring disk configuration information