Job Management Partner 1/Performance Management Planning and Configuration Guide

[Contents][Glossary][Index][Back][Next]


4.2.7 Flow of Store 2.0 installation

The following figure shows the flow of the installation process in preparation for using Store 2.0.

Figure 4-22 Flow of Store 2.0 from installation to operation

[Figure]

Organization of this subsection
(1) When performing a new installation of PFM - Agent version 08-11 or later or PFM - RM
(2) When migrating from Store 1.0
(3) Beginning normal operation
(4) Backing up data
(5) Acquiring data in the event of an error

(1) When performing a new installation of PFM - Agent version 08-11 or later or PFM - RM

To perform a new installation and begin operation with Store 2.0:

  1. Estimate system resource requirements and plan the retention periods.
    Make sure that the execution environment can provide the system resources required to install Store 2.0. The system resources you need to estimate are as follows:
    • Hard disk space
    • Number of files
    • Number of files opened by each process
    Specific resource requirements depend on the retention period settings. Consider the resources available in the execution environment when planning the retention periods. For details on estimating system resource requirements, see the section about system estimates in the appendixes of each PFM - Agent or PFM - RM manual.
  2. Set up directories.
    Set up the directories used by the Agent Store and Remote Monitor Store services, such as the Store directory. This step is only necessary if you intend to use a directory other than the default. Use the jpcconf db define command to specify the directories used by the Agent Store and Remote Monitor Store services.
  3. Set the retention periods.
    Set the retention periods you arrived at when estimating resource requirements in step 1. To set the value with PFM - Web Console, start the Agent Store or Remote Monitor Store service.

(2) When migrating from Store 1.0

To migrate from Store 1.0 and begin operation with Store 2.0:

  1. Estimate system resource requirements and plan the retention periods.
    Make sure that the execution environment can provide the system resources required for installation of Store 2.0. The system resources you need to estimate are as follows:
    • Hard disk space
    • Number of files
    • Number of files opened by each process
    Specific resource requirements depend on the retention period settings. Consider the resources available in the execution environment when planning the retention periods. For details on estimating system resource requirements, see C.4 Exclusively occupied disk space when using the Store database in PFM - Agent 08-00 or later (Store 2.0).
  2. Back up the performance data.
    Back up the data from Store 1.0.
  3. Set up directories.
    When you migrate to Store 2.0, the Agent Store service might not start if the original directory settings for Store 1.0 are retained. For this reason, you will need to review the directory settings used by the Agent Store service. You can use the jpcconf db define command to display and change the directory used by the Agent Store service.
    With Store 2.0, the maximum path length of the directories in which the Store database is created and in which backup files are stored is different from Store 1.0. If a relative path is used in the directory settings for Store 1.0, make sure that it does not exceed the maximum path length allowed by Store 2.0 (214 bytes) when converted to an absolute path. If a directory does not meet this condition, modify the directory settings for the Agent Store service before proceeding to step 4.
  4. Execute the setup command.
    To transfer to Store 2.0, execute the jpcconf db vrset -ver 2.0 command.
  5. Set the retention periods.
    Set the retention periods you arrived at when estimating resource requirements in step 1. Set the retention periods through PFM - Web Console after starting the Agent Store service.

(3) Beginning normal operation

Start the Agent Store or Remote Monitor Store service and begin using the Store database. This step is the same for Store 1.0.

(4) Backing up data

Because Store 2.0 is capable of managing large volumes of operation monitoring data, it is more efficient to perform partial backups on a regular basis than full backups. Establish a backup plan that performs partial backups at regular intervals, such as once a week.

If you intend to reference backup data by using the import function, Hitachi recommends that you change the directory used for partial backups so that the data you want to import in one go will be backed up in one directory. Hitachi recommends that you change the directory around once a month.

(5) Acquiring data in the event of an error

The larger size of the Store database means that data collection will take longer when Store 2.0 is used. In this case, execute both of the following commands to perform data collection of all data except that in the database.

If the database is not particularly large, you can include data in the database in the data collection by executing the command as follows:

When you execute this command, the database data is collected from the Store directory. If the environment variable JPC_COLIMPORT is defined, the database data in the import directory is also collected.

[Contents][Back][Next]


[Trademarks]

All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.