Skip to content

data_portability.md

Latest commit

 

History

History
77 lines (37 loc) · 3.88 KB

data_portability.md

File metadata and controls

77 lines (37 loc) · 3.88 KB
copyright
years
2026
lastupdated 2026-02-26
keywords data portability, data management, operations, compliance, disaster recovery, data ownership, responsibilities
subcollection EventStreams-gen2

{{site.data.keyword.attribute-definition-list}}

Understanding data portability for {{site.data.keyword.messagehub}}

{: #data-portability}

[Gen 2]{: tag-purple}

Data Portability{: term} involves a set of tools, and procedures that enable customers to export the digital artifacts that would be needed to implement similar workload and data processing on different service providers or on-prem software. It includes procedures for copying and storing the service customer's content, including the related configuration used by the service to store and process the data, on customer's own location. {: shortdesc}

Responsibilities

{: #data-portability-responsibilities}

{{site.data.keyword.cloud}} services provide interfaces and instructions to guide the customer to copy and store the service customer content, including the related configuration, on their own selected location.

The customer then is responsible for the use of the exported data and configuration for the purpose of data portability to other infrastructures. This can involve:

  • the planning and execution for setting up alternate infrastructure on different cloud providers or on-prem software that provide similar capabilities to the IBM services
  • the planning and execution for the porting of the required application code on the alternate infrastructure, including the adaptation of customer's application code, deployment automation, etc.
  • the conversion of the exported data and configuration to format required by the alternate infrastructure and adapted applications

To find out more about responsibility ownership for using {{site.data.keyword.cloud}} products between {{site.data.keyword.IBM_notm}} and customer see Shared responsibilities for {{site.data.keyword.cloud_notm}} products.

For more information about your responsibilities when using {{site.data.keyword.messagehub}}, see Shared responsibilities for {{site.data.keyword.messagehub}}.

Data export procedures

{: #data-portability-procedures}

{{site.data.keyword.messagehub}} provides mechanisms to export your content that has been uploaded, stored, and processed using the service.

All data available within the service can be accessed using the Apache Kafka APIs as described in Using the Kafka API. Any data that has exceeded the configured retention will have been deleted and will not be available, as per Limits and quotas.

To export the configuration of your topics defined within {{site.data.keyword.messagehub}}, use the Administration REST API. This is not currently available on the Enterprise Gen2 plan.

To export the configuration of your schemas defined within {{site.data.keyword.messagehub}}, use the Schema Registry REST API. This is not currently available on the Enterprise Gen2 plan.

Exported data formats

{: #data-portability-data-formats}

The format of the data exported from the Apache Kafka APIs will be unchanged from when it was submitted.

The format of topic and schema registry configuration is as defined by the respective APIs.

Schema Registry is not currently available on the Enterprise Gen2 plan. {: note}

Data ownership

All exported data are classified as Customer content and therefore apply to them the full customer ownership and licensing rights, as stated in IBM Cloud Service Agreement.