3.2.6 Functions specific to Store 2.0

Organization of this subsection

(1) Backup of the Store database
(2) Viewing historical operation monitoring data

(1) Backup of the Store database

By regularly backing up the operation monitoring data, you can reduce the risk of data loss in the event of an error. In addition to these regular backup operations, Store 2.0 allows partial backup of data in smaller units.

Figure 3‒20: Partial backup of operation monitoring data

With partial backup, you can specify the target of the backup operation, such as the data collected over a specific time period, data of a specific record type, or data collected during a specific month or year. For example, as shown in the figure above, you can carry out a partial backup of only the PD_PDI records in the PD database that were stored yesterday and the day before, or only monthly records in the PI database that contain data associated with yesterday and the day before. By performing a partial backup, you can reduce the time taken by the backup process and manage data files more efficiently.

For details about how to perform a partial backup, see the chapter that describes backups and restoration operations in the JP1/Performance Management User's Guide.

To Page Top

(2) Viewing historical operation monitoring data

When using Store 2.0, you can view operation monitoring data whose retention period has elapsed by importing it from backup data.

Figure 3‒21: Viewing operation monitoring data

As the figure shows, the Store database can store the imported backup data parallel with the current operation monitoring data, allowing both the data in the database and the imported data to be viewed. Because the imported data is managed independently of the data in the Store database, it will not be deleted even when the retention period specified in the Store database configuration is exceeded. This means that the imported data is available for reference at any time.

Importing backup data differs from restoring it in the following ways:

Importing data does not delete the data already stored in the Store database.
Imported data is retained past the specified retention period.

Use the jpctool db import command to import backup data, specifying either a full or additional import.

Full import:

Use the jpctool db import command to perform a full import of backup data.
Additional import:

Use the jpctool db import command with the -add option specified to perform an additional import. This process adds the backup files to the files already in the import directory. However, if you perform an additional import of backup data that is older than the data already in the import directory, the imported data overwrites the newer data and is reflected from that point in summary records. Therefore, when using the additional import option, import older data first.

For details about how to import data, see the chapter that describes management of operation monitoring data in the JP1/Performance Management User's Guide.

You can change the import directory by using the jpcconf db define command while the Agent Store and Remote Monitor Store services are stopped. You can also delete the data in the import directory by executing the jpctool db import command with the -clear option specified.

You cannot import backup data with a different product ID or Store version. If the data model of the backup data is an older version than that used by the Store database, you can use the jpctool db dmconvert command to upgrade the data model of the backup data, and then you can import it.

To Page Top