9.1.1 Information that needs to be backed up
- Organization of this subsection
(1) Types of information
The following table lists the types of information related to Performance Management that need to be backed up.
|
Information requiring backup |
Description |
|
|---|---|---|
|
Definition information |
Definition information required for Performance Management to operate |
|
|
Report definition information |
Definition information required to display reports. |
|
|
Alarm definition information |
Definition information required to generate alarms. |
|
|
Business group definition information |
Definition information required to set business groups. |
|
|
Service definition information |
Definition information required to start Performance Management. |
|
|
Bookmark definition information |
Bookmark definition information set for individual users. |
|
|
Definition information for process monitoring templates |
Definition information required to use definition templates for process monitoring. |
|
|
Port number information |
Information of port numbers set for various services. |
|
|
Operation monitoring data |
Operation monitoring data collected by Performance Management |
|
|
Event data |
Data that records the events that occurred in Performance Management. Event data is stored in the Store database and managed in PFM - Manager. |
|
|
Performance data |
Data that records performance information collected by PFM - Agent or PFM - RM for a monitored program on a monitored agent. Performance data is stored in the Store database and managed in PFM - Agent or PFM - RM. |
|
(2) Information requiring backup on each host
The following table lists the information that needs to be backed up on each Performance Management host.
|
Information requiring backup |
Host |
|||||
|---|---|---|---|---|---|---|
|
PFM - Manager |
PFM - Web Console |
PFM - Base |
PFM - Agent |
PFM - RM |
||
|
Definition information |
Report definition information |
Y |
-- |
-- |
-- |
-- |
|
Alarm definition information |
Y |
-- |
-- |
-- |
-- |
|
|
Business group definition information |
Y |
-- |
-- |
-- |
-- |
|
|
Service definition information |
Y |
Y |
Y |
Y |
Y |
|
|
Bookmark definition information |
-- |
Y |
-- |
-- |
-- |
|
|
Definition information for process monitoring templates |
-- |
Y |
-- |
-- |
-- |
|
|
Port number information |
Y |
-- |
Y |
Y |
Y |
|
|
Operation monitoring data |
Event data |
Y |
-- |
-- |
-- |
-- |
|
Performance data |
-- |
-- |
-- |
Y |
Y |
|
- Legend:
-
Y: Requires backup.
--: Not applicable.
(3) When to back up data
When planning backup operations, you need to consider the timing with which each type of data is updated. The following table describes when each type of data is updated, and when it is appropriate to back up the data.
|
Information requiring backup |
Update timing |
Backup timing |
|
|---|---|---|---|
|
Definition information |
Report definition information |
When the system is set up When definition information is changed |
When the system is set up, when changes are made to the system configuration, and when changes are made to definition information. |
|
Alarm definition information |
When the system is set up When definition information is changed |
||
|
Business group definition information |
When the system is set up When changes are made to the system configuration |
||
|
Service definition information |
When the system is set up When changes are made to the system configuration When definition information is changed |
||
|
Bookmark definition information |
When the system is set up When definition information is changed |
||
|
Definition information for process monitoring templates |
When the system is set up When definition information is changed |
||
|
Port number information |
When the system is set up When definition information is changed |
||
|
Operation monitoring data |
Event data |
Continuously while the system is running |
Back up the data regularly, at an appropriate interval. |
|
Performance data |
Continuously while the system is running |
||