Live application mobility allows for planned migrations of workload from one system to another without interrupting the application. This technology can be used to perform a planned firmware installation on the server. Most workloads do not need to be aware of the WPAR relocation. WPAR mobility, also referred to as relocation, applies to both types of WPARs: application and system. The relocation of a WPAR consists of moving its executable code from one LPAR to another one while keeping the application data on the same storage devices. It is therefore mandatory that these storage devices are accessible from both the source and target LPARs hosting the WPAR. The hosting global environment hides the physical and logical device implementations from the hosted WPARs. The WPAR only works with data storage at the file system level. All files that need to be written by the application must be hosted on an NFS file system. All other files, including the AIX operating system files, can be stored in file systems local to the hosting global environment. The NFS server must provide access to both the global environment and the WPAR in order for the WPAR to work at all. In a mobility scenario, access must be provided to the WPAR and all global environments to which the WPAR might be moved.