14.3.15 export (exports data)
- Organization of this subsection
(1) Description
This subcommand exports data from memory caches to store data files.
If there is no memory cache, this subcommand does not execute.
(2) Rules
-
You can execute this subcommand when the cluster's status is AVAILABLE.
-
The target of this subcommand is the EADS servers whose cluster participation status is online. This subcommand cannot be executed if the cluster contains any EADS server whose cluster participation status is standby. You can determine the cluster participation status with the eztool status command.
-
You can execute this subcommand when the target EADS servers are closed.
-
When the -s or --single option is specified, the subcommand can be executed on an EADS server that is in any of the following statuses, regardless of the cluster's status:
-
Initialized
-
Running
-
Closing
-
Closed
-
Isolated
-
-
To prevent a full garbage collection (FullGC) from occurring while operations are underway, each EADS server performs FullGC when this subcommand terminates. If the -s or --single option is specified, FullGC is not performed.
-
While this subcommand has obtained a lock from the EADS server, the EADS server is not isolated. However, if a process is shut down or the EADS server terminates while the subcommand has the lock, the lock is released, and then the EADS server is isolated.
(3) Format
eztool export [-s]
[-d path-name-of-store-data-file-output-destination]
[store-data-file-key]
(4) Options and arguments
(a) -s or --single
Specify this option to export only the data retained by the EADS server that executes the command, not the data that is retained in the entire cluster.
For example, specify this option to back up data from an isolated EADS server.
A lock is not obtained from the EADS server when this option is specified. Operation is not guaranteed if caches are deleted, if data is deleted from caches, or if store data files are deleted during data export processing. Note also that the operation is not displayed by the eztool status command as being underway.
(b) -d path-name-of-store-data-file-output-destination or --directory path-name-of-store-data-file-output-destination
This option specifies the path name of the store data file output destination.
Specify this option if you want to export a store data file to a specified directory.
The path name cannot be a directory that contains an asterisk (*), double quotation mark ("), question mark (?), vertical bar (|), less-than sign (<), or greater-than sign (>).
If you specify a relative path for the path name of the store data file output destination, the path is relative to the management directory of each EADS server.
(c) store-data-file-key
This option specifies the store data file key of a store data file.
A store data file key is expressed as a maximum of 32 single-byte characters. The permitted characters are alphanumeric characters (0 to 9, A to Z, and a to z), underscores (_), and hyphens (-).
The prefix eads_ or eads_single_ and the suffix _EADS-server-ID.extension (where the extension is .esd) are added automatically to the store data file key.
If the store data file key is omitted, the command execution date and time become the store data file key, as shown in the following table:
|
-s or --single option |
Store data file name |
Generation management |
|---|---|---|
|
Omitted |
eads_YYYYMMDDhhmmss_EADS-server-ID.esd |
Enabled |
|
Specified |
eads_single_YYYYMMDDhhmmss_EADS-server-ID.esd |
Disabled |
- Legend:
-
YYYYMMDDhhmmss: Command execution date and time
YYYY: year, MM: month, DD: day, hh: hour (00 through 23), mm: minute, ss: second
(5) Return code
The following table lists the return codes that this subcommand returns.
|
No. |
Return code |
Description |
|
|---|---|---|---|
|
eads.command.compat parameter omitted in the command properties |
0300 specified in the eads.command.compat parameter in the command properties |
||
|
1 |
0 |
0 |
Command execution was successful. |
|
2 |
101 |
101 |
Initialization of the command failed. |
|
3 |
110 |
Connection establishment failed. |
|
|
4 |
111 |
The command failed due to a communication timeout. |
|
|
5 |
120 |
The command failed due to a syntax error. |
|
|
6 |
130 |
The command failed because it could not be executed. |
|
|
7 |
131 |
The command failed because another command was executing. |
|
|
8 |
150 |
The command failed during execution. |
|
|
9 |
200 |
The command failed due to a timeout. |
|
(6) Notes
If a store data file key is specified in either of the formats shown below, the store data file might become subject to generation management. If you do not want to manage store data file generations, specify the store data file key in a different format.
-
Format assumed when the store data file key is omitted
eads_YYYYMMDDhhmmss_EADS-server-ID.esd
-
Format of the store data file name that is output when the eztool stop command is executed
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
Note that if the store data file key is specified in the format of the store data file name that is output when the eztool stop command is executed, the store data file might be deleted. For details, see 7.6.2 Specifying the number of store data file generations.