IBM Cloud Docs
Migration strategies for IBM Power Virtual Servers

Migration strategies for IBM Power Virtual Servers

Learn how to migrate your data and workloads to a IBM® Power Systems™ Virtual Server.

IBM i migration strategies

Learn about migration strategies that are specific to IBM i systems.

Recent IBM i migration enhancements:

  1. BRMS enhanced to support software data compression for tape and virtual tape
  2. 90-day software license for BRMS and ICC.

Backup Recovery and Media Services (BRMS) and Cloud Storage (ICC)

BRMS is an IBM i product that can be used to automate activities that help define and process your backup, recovery, and media management operations. The ICC product can be integrated with BRMS to move and retrieve objects from remote locations, including COS (Cloud Object Storage).

The following high-level steps detail how to migrate your OS and data from an on-premises system to the Power Virtual Server environment. Keep in mind that most of these steps can be automated by using BRMS and ICC.

  1. Create your IBM i VM in the Power Virtual Server.
  2. Create a virtual media and IMGCLG on the deployed VM.
  3. Create a virtual optical and IMGCLG on the on-premises system and perform an operating system save.
  4. FTP the images to the Power Virtual Server.
  5. Restore or slip the installation of the OS to get the base OS to the same level as it was on your on-premises system.
  6. Migrate your remaining data.

Refer to this documentation on migrating IBM i to the Cloud by using BRMS and Cloud Storage Solutions with FTP.

For more information, see Data backup and recovery by using BRMS and IBM Cloud Storage Solutions for i and BRMS with Cloud Storage Solutions for i considerations and requirements.

For a complete tutorial on migrating your IBM i workloads to Power Virtual Servers, see Migrating IBM i to IBM Power Virtual Servers.

Logical Replication with Geographic Mirroring and PowerHA SystemMirror for i

GeoMirroring enables IBM i disk mirroring technology on multiple system environments and supports host-based and logical replication across geographically distant sites. Geo mirroring supports synchronous and asynchronous modes. You can integrate PowerHA SystemMirror (Enterprise Edition) for network monitoring and automated failover support.

AIX migration strategies

Learn about migration strategies that are specific to AIX systems.

Migration by using MKSYSB

You can migrate your data by using the mksysb command:

  1. Back up the on-premises OS with the alt_disk_mksysb command and transfer it to COS.
  2. Create a Power Virtual Server and import the image.
  3. Restore the on-premises image.

For more information, see Restoring an AIX mksysb image onto a Power Virtual Server instance.

Logical replication with GLVM and PowerHA SystemMirror for AIX Enterprise Edition

GLVM is an OS-based IP replication strategy. It is based on the AIX LVM and enables data and logical volume mirroring across geographically distant locations. GLVM supports both synchronous and asynchronous modes. You can integrate PowerHA SystemMirror (Enterprise Edition) for network monitoring and automated failover support.

Alternative AIX migration strategies

Some alternative AIX migration strategies include:

  • rsync for nondatabase files
  • The savevg and restvg AIX commands
  • Log shipping for databases

For a complete tutorial on migrating your AIX workloads to Power Virtual Servers, see Migrating AIX to IBM Power Virtual Servers.

Aspera Technologies

IBM Aspera® on Cloud is a hosted service that quickly and reliably moves and shares your data sets across a hybrid cloud environment. IBM Aspera can help transfer data to the IBM Cloud for later retrieval from the Power Virtual Server environment. For more information, see IBM Aspera on Cloud.

Use the Accelerated network transfer migration guide powered by Aspera to accelerate transferring your migration content directly into the workspace of your Power Virtual Server helping you to achieve faster time to value from IBM cloud.

IBM Cloud Object Storage (COS)

COS can be used as an intermediary location to store files from your on-premises environment. You can retrieve and send your files to the Power Virtual Server environment from this location. You must create COS buckets to transfer data over the public internet and or privately secured links. For more information, see IBM Cloud Object Storage: FAQ.

To copy data from COS to your AIX virtual machine (VM), you must install the Amazon Web Services (AWS) CLI by using either the Yellowdog Updater, Modified (yum) or Pip installs Python pip (pip) package managers. If you use the yum package manager, you can install the AWS CLI with the yum install aws-cli command. For the pip package manager, you can use pip install awscli to install the AWS CLI. After the installation, you can use the universal S3 commands that are supported by AWS to copy objects.

You can also find a script that ships (as a sample command) with AIX 7.2 TL3, or later, that simplifies the installation of yum, pip, and the AWS CLI. You can find the script at: /usr/samples/nim/cloud_setup.

For an IBM i VM, you must use the Cloud Storage Solution for IBM i product (5733-ICC) to communicate with COS and transfer data.

PowerVC images and COS

If you have an environment with access to PowerVC, you can capture OVA images to easily migrate your data. The Power Virtual Server offering allows you to provision a new virtual server based on an OVA image. To accomplish this, regardless of the operating system (OS), you must complete the following steps:

  1. Create an OVA image on your local system.
  2. Copy the OVA image to your Cloud Object Storage account.
  3. Deploy the OVA image and provision a new Power Virtual Server.

Replication

You can use various replication mechanisms to migrate and sync environments between your on-premises environment and the Power Virtual Server.

Storage area network (SAN) and hardware-based replication are not currently a migration option.

Host and OS-based logical replication

IBM recommends that you use PowerHA SystemMirror (Enterprise Edition) with Geographic Mirroring (Geo mirroring) and Geographic Logical Volume Manager (GLVM). The following host and OS-based logical replication options exist depending on your OS:

  • AIX - GLVM
  • IBM i - Geo mirroring

Application-specific replication

Applications might have replication mechanisms that can sync multiple environments. These options are commonly used for application-specific replication:

  • Db2 HADR
  • Oracle Data Guard
  • Oracle Goldengate
  • iCluster
  • MIMIX from Syncsort
  • Maxava HA

Back up and restore

You can back up your on-premises environment and restore it to Power Virtual Server. In most cases, COS, and NFS servers serve as an intermediary to back up and restore data. The AIX migration strategies and IBM i migration strategies sections provide information on OS-specific migration strategies.

Third-party vendors and tools

Customers can use third-party tools to perform data migration. The following third-party tools are commonly used for data migration:

FalconStor StorSafe VTL

StorSafe VTL is an IBM-certified solution for migration, backup optimization, archive, and data recovery (DR).

StorSafe VTL is software that emulates physical tape drives and libraries to optimize backup and recovery both on-premises and in the cloud, as well as enable simple and easy migration from on-premises to IBM® Power® Virtual Server. StorSafe VTL can backup IBM i or AIX workloads on-premises, replicate to a cloud-resident StorSafe VTL, and then restore to a Power Virtual Server. Similarly, legacy tapes can be handled. Here are some of the features of StorSafe VTL:

  • Nondisruptive and secure process that can scale to PB-sized workloads.
  • Deduplication and replication improve performance and reduces storage capacity.
  • The same tool for on-premises and cloud that enables both workload and tape migrations.
  • System and application data are deduplicated and compressed before transmitting over the network, thereby accelerating migration, even on the initial baseline transfer.
  • Replicated tapes land in Cloud Object Storage (COS) and can be used by the cloud VTL as a backup baseline without copying the data.
  • Migration uses existing backup processes and tools by using existing environment and knowledge.
  • Data replication can occur over time as part of the backups with final sync replication completed fast during regular backup windows.
  • FalconStor StorSafe VTL for Power Virtual Server can take advantage of IBM low-cost COS storage for its repository.

Migrating an IBM i system

See the video that shows migration of an IBM i system from on-premises to Power Virtual Server - Migration of an IBM i system.

You can access StorSafe VTL from the IBM Cloud Catalog. In the search field, enter FalconStor StorSafe VTL for PowerVS Cloud or FalconStor StorSafe VTL for Power On-Premises.

FalconStor StorSafe VTL for Cloud

FalconStor StorSafe VTL for Power Virtual Server comes bundled with OS and can be deployed from IBM catalogue with one click.

FalconStor StorSafe VTL for On-Premises

FalconStor StorSafe VTL for on-premises provides flexible deployment options for the user:

  • It can be installed on any X86 server that is on Falconstor certification matrix.
  • It can be installed as a VM in Hypervisors such as VMware, HyperV, Xen, and KVM.
  • It can be installed inside Power Virtual Server as an LPAR.

Migration Services

Services to help migration are available from IBM, FalconStor, and Authorized Migration Partners. Reach out if you would like more information about using migration services or becoming a FalconStor Migration Partner at PowerVSMigration@falconstor.com.

If you need any help with deploying FalconStor StorSafe VTL, see FalconStor VTL for IBM Deployment Guide.

For more information on FalconStor StorSafe VTL, see www.falconstor.com.

IBM teams and managed services

You can engage IBM teams and services to assist you throughout the migration lifecycle.