9.3.3 Backing up and restoring the performance data
- Organization of this subsection
(1) Backing up the performance data
-
Log on to the PFM - Manager host.
-
Execute the jpctool service list command, and make sure that the services have started.
Make sure that the Name Server, Master Manager, and Agent Store or Remote Monitor Store services, which manage the performance data to be backed up, have started.
For further details on the jpctool service list command, see the chapter that describes the command in the manual JP1/Performance Management Reference.
-
Execute the jpctool db backup command.
When Running on a Non-Cluster System:
For example, execute the following command when you want the performance data in the Store database of PFM - Agent for Oracle on the host02 host to be backed up:
jpctool db backup -id OS* -host host02
When Running on a Cluster System:
For example, execute the following command when you want the performance data in the Store database of PFM - Agent for Oracle on the jp1-ha2 logical host to be backed up:
jpctool db backup -id OS* -lhost jp1-ha2
By default, executing the command creates a backup file named database-ID.DB in the backup directory.
Table 9‒34: Performance data backup files Conditions
Files to be backed up
Non-cluster system
PFM - Agent or PFM - RM host
In Windows
installation-folder\xxxx#1\store\instance-name#2\backup\generation-number#3\database-ID#4.DB
In UNIX
/opt/jp1pc/xxxx#1/store/instance-name#2/backup/generation-number#3/database-ID#4.DB
Cluster system
Shared disk
In Windows
environment-directory\jp1pc\xxxx#1\store\instance-name#2\backup\generation-number#3\database-ID#4.DB
In UNIX
environment-directory/jp1pc/xxxx#1/store/instance-name#2/backup/generation-number#3/database-ID#4.DB
- #1
-
xxxx indicates the service key of each PFM - Agent or PFM - RM. For details on the PFM - Agent or PFM - RM service keys, see the description of the naming rules in an appendix of the JP1/Performance Management Planning and Configuration Guide.
- #2
-
Created when PFM - Agent or PFM - RM is in the instance environment.
- #3
-
The generation number is assigned in ascending order from 01. The maximum generation number is the value specified in the Backup Save in the jpcsto.ini file. By default, the maximum generation number is 05.
- #4
-
The following are the database IDs:
PI: Database for records of the PI record type
PD: Database for records of the PD record type
PL: Database for records of the PL record type
However, you can also back up the performance data on a host where PFM - Agent or PFM - RM is installed. To perform backup on a host where PFM - Agent or PFM - RM is installed, specify the -alone or -direct option in the jpctool db backup command.
For further details on the jpctool db backup command, see the chapter that describes the command in the manual JP1/Performance Management Reference.
- Note:
-
If you execute the jpctool db backup command while any of the following commands or processes are underway, the jpctool db backup command might fail if it targets the same Master Store service, Agent Store service, or Remote Monitor Store service as the other command or process:
-
jpctool db backup
-
jpctool db dump
-
jpctool db clear
-
jpctool db import
-
jpctool db restore
-
Data storage by the Agent Store service or Remote Monitor Store service
-
Displaying a historical report
In this scenario, try executing the jpctool db backup command again.
-
(2) Restoring the performance data
-
Log on to the PFM - Agent or PFM - RM host that stores the backup file.
-
Execute the jpcspm stop command to stop the PFM - Agent or PFM - RM service.
For details on how to stop the PFM - Agent or PFM - RM service, see 1.3 Stopping services. For further details on the jpcspm stop command, see the chapter that describes the command in the manual JP1/Performance Management Reference.
-
Check the storage location for the backup file.
For details on the default backup destinations for performance data, see Table 9-34 Performance data backup files.
-
Execute the jpctool db restore command.
When Running on a Non-Cluster System:
For example, execute the following command when you want the performance data in the oracleA instance of PFM - Agent for Oracle on the installation-folder\agto\store\oracleA\backup\01 to be restored: Oracle indicates the service key for PFM - Agent.
jpctool db restore -key Oracle -d "installation-folder\agto\store\oracleA\backup\01" -inst oracleA
When Running on a Cluster System:
For example, execute the following command when you want the performance data in the oracleA instance of PFM - Agent for Oracle on the environment-directory\jp1pc\agto\store\oracleA\backup\01 of the jp1-ha2 logical host to be restored (Oracle indicates the service key for PFM - Agent):
jpctool db restore -key Oracle -d "installation-folder\agto\store\oracleA\backup\01" -lhost jp1-ha2 -inst oracleA
For further details on the jpctool db restore command, see the chapter that describes the command in the manual JP1/Performance Management Reference. For details on the service key for each PFM - Agent or PFM - RM instance, see the section that describes naming rules in an appendix of the JP1/Performance Management Planning and Configuration Guide.
-
Execute the jpcspm start command to start the PFM - Agent or PFM - RM service.
For details on how to start the PFM - Agent or PFM - RM service, see 1.2 Starting services.
For further details on the jpcspm start command, see the chapter that describes the command in the manual JP1/Performance Management Reference.
- Note 1:
-
Restoring performance data sometimes causes a delay in restarting the services, because the index of the database has to be rebuilt when the services are started up again.
- Note 2:
-
Backup data cannot be restored to a Store database that uses different Store version. You can only restore backup data acquired from a database set up to use Store 2.0 to a database that uses Store 2.0. Similarly, you can only restore backup data acquired from a database set up to use Store 1.0 to a database that uses Store version is 1.0.