Migrating Data Virtualization data

You can use cpd-cli commands or Git-based Data Virtualization APIs to export and import your Data Virtualization assets.

About the migration methods

Data Virtualization provides two methods to migrate your assets across environments: using the cpd-cli tool or by using Git-based Data Virtualization APIs. Both approaches enable administrators to move Data Virtualization objects, but they differ in scope and workflow.
Migrating Data Virtualization data by using the cpd-cli

The export and import functions in Cloud Pak for Data on-premises enables you to migrate Data Virtualization connections, objects, and associated governance artifacts between Cloud Pak for Data instances of the same version or between Data Virtualization instances of the same Cloud Pak for Data instance by using the cpd-cli. You can also migrate governance artifacts separately by using the IBM® Knowledge Catalog export-import module.

Migrating Data Virtualization objects by using Git-based Data Virtualization APIs
You can export and import your Data Virtualization assets across different environments from your Git repository through Data Virtualization APIs. By using Git, Admin users can quickly synchronize assets by promoting Data Virtualization objects from a Data Virtualization instance to a Git branch, and by pulling updates from Git back into Data Virtualization.
The following table describes the key differences between each migration method:
Table 1. Differences between migrating objects by using the cpd-cli and Git
  cpd-cli Git
What type of objects can you migrate?

Data Virtualization objects and governance artifacts. However, governance artifacts are migrated separately.

 Data Virtualization objects only.
What is the workflow? Export and import commands. Using Git-based Data Virtualization migration APIs.
What is this method ideal for? Bulk migrations in on-premise environments. CI/CD pipelines and incremental updates.

Get started