Managing WPARs

After you have a WPAR created and configured, you might want to perform tasks such as removing, restoring, and listing WPARs.

Listing WPARs
You can list summary data for system WPARs and application WPARs using the lswpar command.
Listing WPAR identifiers
You can list the identifiers for a WPAR using the lparstat command or the uname command.
Logging in to a WPAR
After you configure and activate a system WPAR that does not have a network connection, you can log in to it locally using the clogin command.
Backing up WPARs
You can back up a WPAR using the savewpar command, the mkcd command, or the mkdvd command.
Recovering incompatible shared WPAR
System software in a shared Workload Partition (WPAR) might be incompatible with the level of system software of the global WPAR. This incompatibility occurs when the updated filesets are in the APPLIED state in both the global WPAR and the shared WPAR, but not in the COMMITTED state.
Managing software of the shared WPAR
The shared form (shared /usr) of a system WPAR has the /usr file and the /opt file systems mounted from the global system hosting the WPAR.
Restoring WPARs
You can restore a WPAR using the restwpar command.
Removing WPARs
You can remove a WPAR using the rmwpar command.
Stopping WPARs
You can stop a WPAR from the global environment using the stopwpar command.
Recovering detached WPARs that are incompatible
It is possible that the system software in a detached workload partition (WPAR) might become incompatible with the levels of system software in the global environment. This occurs if software installation and maintenance tasks are performed independently in the global environment and the WPAR, or if a WPAR backup image from an incompatible system level was installed.
Managing software with detached WPARs
System WPARs exist in two basic forms as either shared or detached (non-shared /usr) workload partitions, though the file system characteristics can vary.

Parent topic: IBM Workload Partitions for AIX