9.3.4 Partially backing up performance data (Store 2.0)

(1) Range of data subjected to backup

When backing up data, you need to specify the beginning and end of the backup period based on Greenwich Mean Time as a number of days relative to the execution date of the backup command. For example, if you want to perform a partial backup of the performance data from three days prior to the execution date (the backup date) up to the day before the execution date, specify 3 as the start of the backup period and 1 as the end. In this case, the backup operation applies to the data from three days to one day prior to execution of the backup command. When the backup command is executed, the data from the specified backup period is backed up to the backup directory.

Because the PD and PL databases and the per-minute and hourly records in the PI database are stored in multiple files that each contains the performance data for a particular day, the unit databases for the specified dates are backed up. The daily, weekly, monthly, and yearly records in the PI database are included in the backup data even when they contain data from outside the period defined by the specified start and end dates.

To Page Top

(2) Partially backing up performance data

1. Log on to the PFM - Manager host.

2. 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 Job Management Partner 1/Performance Management Reference.

3. Execute the jpctool db backup command.

   When Running on a Non-Cluster System:

   For example, execute the following command when you want to perform a partial backup of the performance data from three days ago until yesterday in the Store database of PFM - Agent for Oracle on the host02 host:

   jpctool db backup -id OS* -host host02  -partial 3,1

   When Running on a Cluster System:

   For example, execute the following command when you want to perform a partial backup of the performance data from three days ago until yesterday in the Store database of PFM - Agent for Oracle on the logical host jp1-ha2:

   jpctool db backup -id OS* -lhost jp1-ha2  -partial 3,1

   By default, the command creates backup files with the following names in the backup directory.

   Table 9‒35: Partial backup files for performance data

   Conditions			Files to be backed up
   Non-cluster system	PFM - Agent or PFM - RM host	In Windows	Contents of installation-folder\xxxx#1\store\instance-name#2\partial\stdatabase-ID#3
   		In UNIX	Contents of /opt/jp1pc/xxxx#1/store/instance-name#2/partial/stdatabase-ID#3
   Cluster system	Shared disk	In Windows	Contents of environment-directory\jp1pc\ xxxx#1\store\instance-name#2\partial\stdatabase-ID#3
   		In UNIX	Contents of environment-directory/jp1pc/ xxxx#1/store/instance-name#2/partial/stdatabase-ID#3

   #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 Job Management Partner 1/Performance Management Planning and Configuration Guide.

   #2

   Created when PFM - Agent or PFM - RM is in the instance environment.

   #3

   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

   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 Job Management Partner 1/Performance Management Reference.

The following table describes the directories and file structure used for the files produced by a partial backup:

Table 9‒36: Directories and file structure for partial backups

Directory or file	Record type			Format	Min.	Max.	Description
	PI	PD	PL
STXX	Y	Y	Y	n/a	n/a	n/a	n/a
Summary block	Y	N	N	n	1	6	Summary block (for PI records) 1: Minute 2: Hour 3: Day 4: Week 5: Month 6: Year
Year	Y	Y	Y	YYYY	1900	2027	Year
Month and day	Y	Y	Y	MMDD	0101	1231	Month and day
Generation number	Y	Y	Y	nnn	001	002	Generation number
record-type.DB	Y	Y	Y	n/a	n/a	n/a	Database file for each record type

To Page Top

(3) Minimizing duplicate backup data as much as possible

The Store 2.0 database is composed of multiple unit databases each covering a specific time period. Only the most recent unit database is updated. For example, when using unit databases that each contains the performance data for a specific day, the Agent sequentially writes data to the unit database for that day. However, the unit database from the previous day remains unchanged from its status at 23:59 GMT until its retention period expires and the file is deleted. Accordingly, by performing a partial backup of the data from the date when the previous backup was made to the day before the current backup date, you can back up data without acquiring the same day's unit database more than once.

Example: When the previous backup was acquired n days ago

jpctool db backup -id DS1inst1[host1] -d d:\backup01# -partial (n+1),1

# D:\backup01 indicates the backup directory.

To Page Top

(4) Backing up the most recent data possible

To back up the latest database, use the following command:

Example: Backing up the latest version of the database

jpctool db backup -id DS1inst1[host1] -d d:\backup01# -partial 0,0

# D:\backup01 indicates the backup directory.

To Page Top

(5) Example of performing a partial backup

The following is an example of performing a partial backup in the JST (Japan Standard Time, GMT + 9:00) time zone.

At 3 AM each day, an overnight batch job is executed that executes the following backup command targeting the instance inst1 of the multi-instance Agent Store and Remote Monitor Store services with the product ID Z.

jpctool db backup -id DSinst1[host1] -partial 1,1

In this case, the unit database that covers the time that is the same as the backup command execution time on the date in the specified range is backed up. Now, suppose that the backup command is executed at 03:00 on October 15, in a week that begins on October 12.

1. The command is executed at 03:00 (JST) on October 15.

2. Taking into account the 9-hour difference, 03:00 JST on October 15 is 18:00 GMT on October 14.

3. Because the command specifies -partial 1,1 (one day ago), the partial backup applies to the data between 00:00 AM and 23:59 PM (GMT) on October 13.

4. Again, taking into account the 9-hour difference, the backup range from 00:00 GMT to 23:59 GMT on October 13 is from 09:00 JST on October 13 to 09:00 JST on October 14.

Therefore, in the case of per-minute records, the data from 09:00 on October 13 until 09:00 on October 14 JST is backed up. If the backup command is executed again at the same time on the following day, you can start backing up from where you stopped on the previous day. The following figure shows the backup range for per-minute records.

Figure 9‒2: Backup range for per-minute records

In the case of weekly records, because the unit database that covers the specified period is backed up, this results in the data from 09:00 on October 12 to 03:00 on October 15, including the latest data, being backed up. If the backup command is executed again at the same time on the following day, all of the data from the beginning of the week (October 12) onward is backed up again. The following figure shows the backup range for weekly records.

Figure 9‒3: Backup range for weekly records

To Page Top