Planned outage with Live Partition Mobility and Storwize HyperSwap Implementation with IASP: disaster at site 1 IBM PowerVMfi Live Partition Mobility (LPM) allows you to move a running logical partition,  including its operating system and running applications, from one system to another without  any shutdown or without disrupting the operation of that logical partition. For more information  about LPM refer to  IBM PowerVM Virtualization Introduction and Configuration , SG24-7940. In this solution we combine Live Partition Mobility with HyperSwap, to transfer the workload  onto site 2 during the planned outage of site 1. This scenario requires connection with  VIOS_NPIV and all IBM i LUNs as HyperSwap LUNs. For more information about LPM  requirements, refer to  IBM PowerVM Virtualization Introduction and Configuration ,  SG24-7940. Before starting LPM you have to define the host in Storwize with the WWPNs of the second  port of the virtual FC adapters. Specify  site 2  for this host. This way you enable the I/O rate to  transfer to the nodes at site 2 when LPM is transferring the IBM i partition.  After the outage is finished, use LPM to transfer the IBM i partition to site 1. During the  transfer, the I/O rate will automatically move to the nodes at site 1. This scenario requires PowerHA for i software installed, and the corresponding IBM i setup  which consists of two IBM partitions in the cluster, IASP on the IBM i at site 1, cluster  resource group, and PowerHA copy description. The workload is running in the IASP. For  more information about PowerHA for i setup refer to  IBM PowerHA SystemMirror for i:  Preparation (Volume 1 of 4) , SG24-8400. In this scenario, ensure that all IBM i LUNs, not just the IASP LUNs, are HyperSwap volumes. If there is a disaster at site 1, PowerHA for i automatically switches the IASP to the system at  site 2, and the workload can be resumed at site 2.  After the failure at site 1 is fixed, use PowerHA for i to switch IASP back to site 1 and resume  the workload at this site.  Appendix A. IBM i considerations  494