Back up AIX workload partition file systems

Using the backup-archive client on AIX®, you can back up and restore local partition file data within the global partition by using the local partition name space available within the global partition.

Each workload partition (WPAR) has its own security domain, so only the global root user is guaranteed to have access to all of the data.

The WPARs are partitions that are created entirely in software within a single AIX system image, with the following attributes:

Usually the WPAR appears to be a complete stand-alone AIX system
There is no hardware assist or configuration

Workload partitions provide a secure and isolated environment for enterprise applications in terms of process, signal, and file system space. Software running within the context of a workload partition appears to have its own separate instance of AIX.

The following example shows a WPAR configuration from within the global WPAR:

Global partition:: System name: shimla; File system: /home /opt
WPAR #1 configuration:: Name: wpar1; File system: /home; name in global WPAR: /wpars/wpar1/home
WPAR #2 configuration:: Name: wpar2; File system: /data; name in global WPAR: /wpars/wpar2/data

There are two ways to back up WPAR data, as follows:

Back up all WPAR file systems as the file spaces within the global partition. The file space name must be used to identify the WPAR to which it belongs. All of the data is managed on one node by using one schedule. Using the example configuration, here is a sample dsm.sys file with one server stanza for all file systems, both global and local:
```
SErvername  shimla
   TCPPort            1500
   TCPServeraddress   server.example.com
   nodename           shimla
   PasswordAccess     generate
   Domain             /wpars/wpar1/home /wpars/wpar2/data /home /opt
```
Back up each WPAR file system under a different node name. This method provides file space name segregation for each WPAR. Each WPAR must have a separate node name and a scheduler that is running within the global partition. Also, three scheduler services must be set up, each using a different dsm.opt file corresponding to the server stanza name. This method allows each WPAR backup operation to be managed independently of the others. Using the example configuration, here is a sample dsm.sys file with three server stanzas: one for wpar1, one for wpar2, and one for global partition shimla:
```
SErvername  shimla_wpar1
   TCPPort            1500
   TCPServeraddress   server.example.com
   nodename           wpar1
   PasswordAccess     generate
   Domain             /wpars/wpar1/home

SErvername  shimla_wpar2
   TCPPort            1500
   TCPServeraddress   server.example.com
   nodename           wpar2
   PasswordAccess     generate
   Domain             /wpars/wpar2/data

SErvername  shimla
   TCPPort            1500
   TCPServeraddress   server.example.com
   nodename           shimla
   PasswordAccess     generate
   Domain             /home /opt
```