export-import
import create
Important: IBM Cloud Pak® for Data
Version 4.7 will reach end of support (EOS) on 31 July, 2025. For more information, see the Discontinuance of service announcement for IBM Cloud Pak for Data Version 4.X.
Upgrade to IBM Software Hub Version 5.1 before IBM Cloud Pak for Data Version 4.7 reaches end of support. For more information, see Upgrading IBM Software Hub in the IBM Software Hub Version 5.1 documentation.
Create an IBM® Cloud Pak for Data import.
Syntax
cpd-cli export-import import create <cpd-import-file-name> \
[--arch=<system-cpu-architecture>] \
[--backoff-limit] \
[--cpdconfig=<cpd-configuration-location>] \
[--from-export=<cpd-export-file-name>] \
[--from-schedule=<import-schedule-name>] \
[--instance-name=<cpd-service-instance-name>] \
[--log-level=info|debug|warn|error|panic] \
[--namespace=<namespace-name>] \
--profile=<cpd-configuration-profile-name> \
[--service-type=<cpd-service-type>] \
[--values=<yaml-file-name1,yaml-file-name2,...>] \
[--verbose]
Arguments
| Argument | Description |
|---|---|
<cpd-import-file-name> |
The name of the import to create. |
Table 1: Command arguments
Options
| Option | Description |
|---|---|
--arch |
Provide the CPU architecture
(hardware) of the cluster.
|
--backoff-limit |
The number of retries for an
export or import job before the job is considered a failure. Setting --backoff-limit=0 disables the
retry.
|
--cpdconfig |
The Cloud Pak for Data
configuration location. For example,
$HOME/.cpd-cli/config.
|
--from-export |
The Cloud Pak for Data export file
name from which to import.
|
--from-schedule |
The schedule name from which to
import.
|
|
|
Display command
help.
|
--instance-name |
Specify the Cloud Pak for Data
service instance name.
|
--log-level |
The command log
level.
|
|
|
The namespace name in which the
utility should operate.
|
--profile |
The name of the profile that you
created to store information about an instance of Cloud Pak for Data and your credentials for the
instance.
|
--service-type |
The Cloud Pak for Data service
instance type.
|
|
|
Specify values in one or more YAML
files.
|
--verbose |
Logs include more detailed
messages.
|
Table 2: Command options
Examples
Note: The following examples use the recommended installation environment variables.
Use a script to create environment variables with the correct values for your environment. For more information, see Best practice: Setting up install variables.
- Import Cloud Pak for Data data from
<cpd-export-file-name>in the${PROJECT_CPD_INST_OPERANDS}namespace. - The export must be completed successfully before the import can run. Only
one import job can run at a time. The completed import job must be deleted before starting a new
import.
cpd-cli export-import import create <cpd-import-file-name> \ --from-export=<cpd-export-file-name> \ --namespace=${PROJECT_CPD_INST_OPERANDS} \ --arch=${CPU_ARCH} \ --profile=<cpd-configuration-profile-name> \ --log-level=debug \ --verbose