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 local time as a number of days relative to the execution date of the backup command. 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. On the other hand, in the PI database, different records are stored in the following different files: daily and weekly records in the weekly file, monthly records in the monthly file, and yearly records in the yearly file. This means that the backed-up data contains even the data that falls outside the period defined by the start date and end date of records.

#:

Because the Store database runs on Greenwich Mean Time (GMT), when your system lies outside the GMT zone, you will notice the deviation of the collected data range from the specified date.

To Page Top

(2) Creating a partial backup of data every n day(s)

Because the Store database runs on GMT, data collection must start from n + 1 days before, taking into account the difference between GMT and local time.

Example:

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

# D:\backup01 indicates the backup directory.

To Page Top

(3) 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 ZS1inst1[host1] -d d:\backup01# -partial startday,endday

# D:\backup01 indicates the backup directory.

The recommended values to be specified for startday and endday of the -partial option vary depending on the local time setting.

For example, the table below shows the startday and endday values recommended for three different local time settings (namely, GMT, GMT-9:00, and GMT+9:00) as well as the actual backup data collection period in each case. This example assumes that you are executing the back up command on March 17 (Thursday) to back up data collected during a period from 0:00 to 23:59 on the previous day, March 16 (Wednesday).

Table 9‒35: Recommended values for the -partial option

Local time setting	Recommended values to be specified for the -partial option		Actual backup data collection period (in local time)
	startday	endday
GMT	1	1	From 0:00 on March 16 to 23:59 on March 16
GMT-09:00	1	0	From 15:00 on March 15 to the time at which the command is executed
GMT+09:00	2	0	From 9:00 on March 15 to the time at which the command is executed

Depending on the time at which the backup command is executed, a backup might not be created. The period during which the backup command may be executed is described below.

To Page Top

(4) Location to which to store partial backups, and the directory and structure of the files to be stored

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

Table 9‒36: 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

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

Table 9‒37: 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	2035	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