7.6.2 Specifying the number of store data file generations

(1) Store data file output when the eztool export command is executed

When you use the eztool export command to export data, you normally omit the store data file key. In this case, the command execution date and time become the store data file key, as shown below:

eads_YYYYMMDDhhmmss_EADS-server-ID.esd

Legend:

YYYYMMDDhhmmss: Command execution date and time

YYYY: year, MM: month, DD: day, hh: hour (00 through 23), mm: minute, ss: second

The prefix eads_ and the suffix _EADS-server-ID.extension (where the extension is .esd) are added automatically to the store data file key.

When the store data file key is in the format shown above and the eztool import command is executed, the store data file with the most recent command execution date and time is imported.

All data maintained by the EADS server is output to the store data file. This includes copies of data created for redundancy. The cache name and the key, update date, and value are output for each data item.

For details about the output destinations of store data files, see 7.4.2 Specifying the file output destinations.

If the output destination already contains a store data file with the same name, the eztool export command results in an error; the existing file is not overwritten.

To Page Top

(2) Management of store data file generations

Store data files that have the same command execution date and time are treated as belonging to the same group, and their generations are managed in the entire cluster until the maximum number of generations specified in the eads.admin.backup.exportCommand.generation.maxNum parameter in the shared properties is reached. This prevents a disk capacity shortage, which can occur when store data files increase.

The following example specifies two (the default value) as the maximum number of store data file generations to be retained in the entire cluster.

Figure 7‒4: Specifying the number of store data file generations

If more than this maximum number of generations of store data files are output, the eztool export command results in an error. Execute the eztool deleteesd command to delete any unneeded store data.

For details about how to check and delete store data files, see 11.7 Managing store data files.

Important note

Generation management of store data files is not performed in the following cases:

• The value 0 is specified for the maximum number of generations (in the eads.admin.backup.exportCommand.generation.maxNum parameter in the shared properties)

• The -s or --single option is specified in the eztool export command

To Page Top

(3) Store data file output when the eztool stop command is executed

When the eztool stop command is executed to terminate the EADS server, data is exported to files and then the EADS server is terminated.

A store data file key cannot be specified in this case; instead, the command's execution date and time become the store data file key, as shown below.

The prefix eads_stop_ and the suffix _EADS-server-ID.extension (where the extension is .esd) are added automatically to the store data file key:

eads_stop_YYYYMMDDhhmmss_EADS-server-ID.esd

Legend:

YYYYMMDDhhmmss: Command execution date and time

YYYY: year, MM: month, DD: day, hh: hour (00 through 23), mm: minute, ss: second

eads.admin.backup.stopCommand.generation.maxNum parameter in the shared properties, specify the maximum number of store data file generations that can be output when the eztool stop command is executed.

If more than this maximum number of generations of store data files are output, the most recent store data files are output and the oldest store data files are deleted.

Important note

If the --no_export option is specified in the eztool stop command, no data is output to a file when the EADS server is terminated.

To Page Top