central operations console, such as HP Operations Manager software, paging a system operator, or taking automated remedial action to resolve the problem.
Table 13 ARM functionality
Transaction description | Additional data logged to | Usage |
(ARM 1.0) | ARM (ARM 2.0) |
|
|
|
|
Backup specification session | Processed data [MB] | Availability and recovery |
duration |
| planning. Chargeback. |
|
|
|
Object backup session | Processed data [MB] | Availability and recovery |
duration |
| planning. Chargeback. |
|
|
|
Restore session duration | Recovered data [MB] | Availability and recovery |
|
| planning |
|
|
|
IDB check duration | IDB size [MB] | Data Protector architecture |
|
| management |
|
|
|
IDB purge duration | IDB size after purge and | Data Protector architecture |
| number of purged records | management |
As Data Protector is already ARM equipped, it is a fairly simple task to integrate Data Protector with an application like PA that supports the ARM API. On Windows platforms, this is completely automatic. If Data Protector is installed on a system where PA is already present or vice versa, the transaction data will immediately show up in PA and HP Performance Manager (PM). On
Another way to interface PA with Data Protector is the Data Source Integration (DSI). This is important if the application that you use for transaction tracking is not ARM
2.0compliant. ARM 1.0 permits you to log
Concepts guide | 209 |