Understanding data portability for Satellite
Data PortabilityThe ability of IT services to recover from rare but major incidents and non-transient, wide-scale failures, such as service disruption that affects an entire geographical area. The impact of such an incident exceeds the ability of the high availability design to handle it. See also high availability, recovery time objective, recovery point objective. involves a set of tools and procedures that enable customers to export the digital artifacts that are needed to implement similar workload and data processing on different service providers or on-premises software. It includes procedures for copying and storing the service customer content, including the related configuration that is used by the service to store and process the data, on the customer’s own location.
Responsibilities
IBM 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 is responsible for the use of the exported data and configuration for data portability to other infrastructures, which includes:
- The planning and execution for setting up alternative infrastructure on different cloud providers or on-premises software that provide similar capabilities to the IBM services.
- The planning and execution for the porting of the required application code on the alternative infrastructure, including the adaptation of customer's application code, deployment automation, and so on.
- The conversion of the exported data and configuration to the format that's required by the alternative infrastructure and adapted applications.
For more information, see Your responsibilities with Satellite.
Data export procedures
Satellite provides mechanisms to export your content that was uploaded, stored, and processed using the service.
When you create a Satellite location, you provide a COS bucket where your data is stored. You can follow the COS documentation to export your data from one COS provider to another.
You can also review the following links for more information about exporting data from Satellite-enabled services.
For more information, see Satellite-enabled services.
| Title | Description |
|---|---|
| Red Hat OpenShift on IBM Cloud | For data portability information, see Understanding data portability for Red Hat OpenShift on IBM Cloud. |
Rclone |
When you create a Satellite location, you provide a COS bucket where your data is stored. You can use rclone to move this data from COS to another s3 storage provider. For an example scenario, see the Migrating Cloud Object Storage (COS) apps and data between IBM Cloud accounts tutorial for steps on using rclone to move data in one COS bucket to another COS bucket in IBM Cloud or in another cloud provider. Also, review Using rclone. |
| OpenShift APIs for Data Protection (OADP) | OADP (OpenShift APIs for Data Protection) is an operator that Red Hat has created to create, backup, and restore APIs for OpenShift clusters. For more information, see Backup and restore Red Hat OpenShift cluster applications with OADP and the OADP documentation |
Exported data formats
Review the product documentation for the services you run on Satellite for information about data export formats.
Data ownership
All exported data is classified as customer content and is therefore applied to the full customer ownership and licensing rights, as stated in IBM Cloud Service Agreement.