Use the cpdumps command to copy dump files from a nonconfiguration
node onto the configuration node.
Note: In the rare event that the /dumps directory on the
configuration node is full, the copy action ends when the directory is full and provides no
indicator of a failure. Therefore, clear the /dumps directory after
migrating data from the configuration node.
Syntax
cpdumps -prefix { directory | file_filter } { node_name | node_id }
Parameters
- -prefixdirectory | file_filter
- (Required) Specifies the directory, or files, or both to be retrieved. If a directory is
specified with no file filter, all relevant memory dump or log files in that directory are
retrieved. You can use the following directory arguments (filters):
- /dumps (retrieves all files in all subdirectories).
- /dumps/audit
- /dumps/cimom
- /dumps/cloud
- /dumps/configs
- /dumps/elogs
- /dumps/easytier
- /dumps/enclosure
- /dumps/feature
- /dumps/iostats
- /dumps/iotrace
- /dumps/mdisk
- /home/admin/update
In addition to the directory, you can specify a file filter. For example, if you
specified /dumps/elogs/*.txt, all files in the
/dumps/elogs directory that end in .txt are
copied.
Note: The following rules apply to the use of wildcards with the CLI:
- node_id | node_name
- (Required) Specifies the node from which to retrieve the memory dumps. The variable that
follows the parameter can be one of the following:
- The node name, or label that you assigned when you added the node to the system.
- The node ID that is assigned to the node (not the worldwide node name).
If the node specified is the current configuration node, no file is copied.
Description
This command copies any
memory dumps that match the directory or file criteria from the given node to the current
configuration node.
You can retrieve memory dumps that were saved to an old configuration
node. During failover processing from the old configuration node to another node, the memory
dumps that were on the old configuration node are not automatically copied. Because access from
the CLI is only provided to the configuration node, system files can only be copied from the
configuration node. This command enables you to retrieve files and place them on the
configuration node so that you can then copy them.
You can view the contents of the
directories by using the lsdumps command. You can track the status of a copy
using the lscopystatus command.
An invocation
example
cpdumps -prefix /dumps/configs nodeone
The resulting
output:
No feedback
An invocation
example
cpdumps -prefix /dumps/easytier node_2
The resulting
output:
No feedback