Skip to content

Latest commit

 

History

History
77 lines (41 loc) · 4.17 KB

data-portability.md

File metadata and controls

77 lines (41 loc) · 4.17 KB
copyright lastupdated keywords subcollection
years
2025
2025-01-17
data portability, power virtual server
power-iaas

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

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

{: #data-portability}

{{site.data.keyword.off-prem-fname}} in [{{site.data.keyword.off-prem}}]{: tag-blue}

{{site.data.keyword.on-prem-fname}} in [{{site.data.keyword.on-prem}}]{: tag-red}

By using data portability for {{site.data.keyword.powerSysFull}}, you can perform tasks such as transferring data and processing the data, either in your data center location or on a service provider location. You can port the data by using a set of tools and procedures. {: shortdesc}

You can accomplish the following tasks by using data portability:

  • Export the digital artifacts that are needed to implement similar workloads.

  • Process the data on the {{site.data.keyword.powerSys_notm}} or on a service provider location that supports the Power architecture.

{{site.data.keyword.powerSys_notm}} is an Infrastructure as a Service (IaaS) offering. As a {{site.data.keyword.powerSys_notm}} user, you own the data, operating system images, and configuration parameters. {{site.data.keyword.powerSys_notm}} architecture follows a typical on-premises Power deployments to facilitate data portability. The infrastructure design enables {{site.data.keyword.powerSys_notm}} to maintain key enterprise software certification and support as the {{site.data.keyword.powerSys_notm}} architecture replicates a certified private cloud infrastructure.

Defining the responsibilities

{: #data-port-respon}

{{site.data.keyword.powerSys_notm}} provides interfaces and instructions to guide you to copy and store your content on your selected location. The content can include data that is stored on the logical volumes, operating system images, and configuration parameters.

You are responsible for the use of the exported data and setting up the configuration for data portability to other infrastructures. You are responsible for planning and execution for setting up an alternative infrastructure. The alternative infrastructure must provide similar capabilities to that of {{site.data.keyword.powerSys_notm}} services.

For more information about the responsibility assignment (RACI) matrix for {{site.data.keyword.powerSys_notm}}, see High-level architecture.

Migrating the data

{: #data-port-export-proc}

Refer to the following topics that are related to the migration of your Power workloads to {{site.data.keyword.powerSys_notm}}:

{{site.data.keyword.powerSys_notm}} provides the capability to capture full or point-in-time copies of the logical volumes or data sets. By using IBM FlashCopy feature and {{site.data.keyword.powerSys_notm}} APIs, you can create delta snapshots, volume clones, and restore your disks. For more information, see Snapshots, cloning, and restoring.

Capturing and exporting a virtual machine (VM)

{: #data-port-export-data}

{{site.data.keyword.powerSys_notm}} provides mechanisms to capture and export a virtual machine. For more information, see Capturing and exporting a virtual machine (VM).

Ownership of the data

{: #data-port-data-owner}

The exported data is classified as customer content. For more information about Compliance with Laws, see IBM Cloud Service Agreement{: external}.