Services that support cpd-cli
export-import
The following table identifies which services support the IBM Cloud Pak® for Data data export and import utility (cpd-cli export-import command).
You can use the Cloud Pak for Data data export and import utility to export service data, including metadata, from one Cloud Pak for Data installation and import the service data to another Cloud Pak for Data installation.
The Exceptions column lists any assets that do not support the cpd-cli export-import command.
The Notes column provides details on services that need more steps to be done when you use the data export and import utility. The column also provides information for services that use a different data migration strategy.
Service | Supports cpd-cli export-import command | Notes |
---|---|---|
IBM Cloud Pak for Data control plane | Not applicable | The only data that is associated with the control plane is user data.
|
Common core services | No | Assets are exported and imported through projects. For details, see Exporting a project (Watson Studio). |
Scheduling service | Not applicable | The scheduling service does not store any data. |
AI Factsheets | No | No alternative method is available. |
Analytics Engine Powered by Apache Spark | No | No alternative method is available. |
Cognos® Analytics | No | Cognos Analytics uses another method to export and import data and metadata. For details, see Backing up and restoring Cognos Analytics |
Cognos Dashboards | No | Cognos Dashboards uses a different method for exporting dashboards. You can export dashboards from the Cognos Dashboards user interface. |
Data Privacy | ✓ | You can use the export-import commands to export
masking flow metadata. |
Data Refinery | Not applicable | |
Data Replication | No | No alternative method is available. |
DataStage® | No | The data and metadata for DataStage are included in analytics projects. For details, see Exporting an analytics project (Watson Studio). |
Db2® | No | Db2 uses a different method for exporting data. For details, see Backing up and restoring Db2. |
Db2 Big SQL | No | No alternative method is available. |
Db2 Data Gate | No | No alternative method is available. |
Db2 Data Management Console | No | No alternative method is available. |
Db2 Warehouse | No | Db2 Warehouse uses a different method for exporting data. For details, see Backing up and restoring Db2 Warehouse. |
Decision Optimization | No | Decision Optimization assets are exported and imported through projects. For details, see Exporting a project (Watson Studio). |
EDB Postgres | No | EDB Postgres uses a
different method for exporting data. For details, see pg_dump in the EDB Postgres documentation. |
Execution Engine for Apache Hadoop | Not applicable | |
IBM® Match 360 with Watson | No |
|
Informix® | No | Informix uses a different method for exporting data. For details, see Data migration utilities in the Informix documentation. |
MongoDB | No | MongoDB uses a different method for
exporting data. For details, see mongodump in the MongoDB documentation. |
OpenPages® | No | OpenPages uses a different method for exporting data. For details, see Migrating OpenPages environments in the OpenPages documentation. |
Planning Analytics | No | Planning Analytics uses a different method for exporting data. You can export data from the Planning Analytics user interface. |
Product Master | No | Product Master uses a different method for exporting data. For details, see Import Environment in the Product Master documentation. |
RStudio® Server Runtimes | No | Data and assets for RStudio Server Runtimes are included in analytics projects. For details, see Exporting a project (Watson Studio). |
SPSS® Modeler | No | The data and assets for SPSS Modeler are included in analytics projects. For details, see Exporting an analytics project (Watson Studio). |
Voice Gateway | No | No alternative method is available. |
Watson Assistant | No | Watson Assistant uses a different method for exporting data. For details, see Backing up and restoring data in the Watson Assistant documentation on IBM Cloud. |
Watson Discovery | No | Watson Discovery uses a different method for exporting data. For details, see Backing up and restoring data in Cloud Pak for Data in the Watson Discovery documentation on IBM Cloud. |
Watson Knowledge Catalog | ✓ |
For the list of governance artifacts that can be imported and exported, see Migrating governance artifacts. For the list of catalog assets that can be imported and exported, see Migrating catalog assets. 4.6.04.6.14.6.2You cannot export:
4.6.3 or laterYou
cannot export:
|
Watson Knowledge Studio | No | Watson Knowledge Studio uses a different method for exporting data. For details, see Backing up and restoring data in the Watson Knowledge Studio documentation on IBM Cloud. |
Watson Machine Learning | No | Watson Machine Learning uses a different method for exporting assets. For details, see Exporting space assets. |
Watson Machine Learning Accelerator | ✓ | Additional setup is required importing and exporting data. For more information, see Importing and exporting Watson Machine Learning
Accelerator
data. You can export the following data from your Watson Machine Learning Accelerator installation:
|
Watson OpenScale | No | No alternative method is available. |
Watson Pipelines | No | Watson
Pipelines uses the cpdctl command-line interface to export and import
data. |
Watson Query | No | No alternative method is available. |
Watson Speech services | No | Watson Speech services uses service-specific utilities. For details, see Importing and exporting Watson Speech services data. |
Watson Studio | No | Watson Studio assets are exported and imported through projects. For details, see Exporting a project (Watson Studio). |
Watson Studio Runtimes | Not applicable | Watson Studio
Runtimes is stateless. The data that Watson Studio Runtimes works with is included in analytics projects. For details, see Exporting a project (Watson Studio). |