HelpSystems Blog

What is Live Partition Mobility for IBM i?

Demands for system uptime have consistently risen over the years, and while technology features such as high availability have largely minimized unplanned downtime, servers still have to come down for routine maintenance to keep operations running smoothly. This is one of the key benefits of Live Partition Mobility for IBM i, which allows IT to migrate a partition from one physical machine to another.

Requirements for Live Partition Mobility

Live Partition Mobility is available on PowerVM Enterprise Edition hardware. The active partition mobility functionality enables users to transfer AIX, IBM i, and Linux logical partitions between systems, while inactive partition mobility enables the migration of partitions that are powered down.

LPM does have several requirements, including that the system runs IBM i 7.1 or later, and the source and destination must both leverage external storage. In addition, both environments must utilize virtualization configured with VIOS.

Benefits of Live Partition Mobility

As IBM notes in its Live Partition Mobility redbook, the feature allows businesses to eliminate outages caused by hardware maintenance. Prior to running such tasks on a server, users can move critical data and software to another machine. Other potential advantages include:

  • Minimized downtime for hardware upgrades
  • No downtime if the system predicts an upcoming hardware failure
  • Ability to move workloads between servers to optimize performance

These features allow IT staff to keep key systems running as they conduct their typical maintenance tasks, and it is not too difficult to utilize Live Partition Mobility as long as the environment meets the requirements. While advantageous, it is important not to confuse LPM with high availability technology—LPM is not designed to mitigate unplanned downtime.

What to Check before Using LPM

The first thing to do before leveraging partition mobility is to ensure that both systems are configured appropriately. This can be done through the hardware management console (HMC). In addition, it is important to evaluate the resources available on the target server to ensure there is enough storage space, memory, and processing power to handle the partition. If the partition that will be migrated utilizes shared memory, the memory pool will need to be created on the target machine. Finally, IBM recommends ensuring that both servers can communicate with each other so that the migration process is not interrupted.