Running multiple sessions on clients for a restore
To use multiple sessions, data for the client must be on multiple sequential access volumes in a file or tape storage pool. Or the data can be contained in a random disk storage pool (with a device class with a device type of DISK). The data for a client usually becomes spread out over some number of volumes over time.
To potentially benefit from multi-session restores, consider collocating client data by group. Collocation by group can cause data for a node to be distributed on more than one volume. The distribution happens while the group's total data is kept on as few volumes as possible.
Restore operations can be restricted on mount points. The MAXNUMMP parameter in the REGISTER NODE or UPDATE NODE command applies to restore operations. The client can restrict the number of sessions, which are based on the combination of the MAXNUMMP value and the client RESOURCEUTILIZATION value. Unlike tape, you can mount FILE volumes in multiple sessions simultaneously, for restore or retrieve operations.
Set the client option for resource utilization to one greater than the number of sessions that you want. Use the number of drives that you want that single client to use. The client option can be included in a client option set.
Issue the restore command so that it results in a no-query restore process.