I'm not sure whether this is exactly what you need or not, but check this out:
(Pay special attention to the "Preview = Yes" option you can specify with the command)
Syntax
>>-RESTORE STGpool--primary_pool_name--------------------------->
>--+--------------------------------+--------------------------->
'-COPYstgpool--=--copy_pool_name-'
>--+--------------------------------------+--------------------->
'-NEWstgpool--=--new_primary_pool_name-'
.-MAXPRocess--=--1------. .-Preview--=--No------.
>--+-----------------------+--+---------------------+----------->
'-MAXPRocess--=--number-' '-Preview--=--+-No--+-'
'-Yes-'
.-Wait--=--No------.
>--+------------------+----------------------------------------><
'-Wait--=--+-No--+-'
'-Yes-'
Parameters
primary_pool_name (Required)
Specifies the name of the primary storage pool that is being restored.
COPYstgpool
Specifies the name of the copy storage pool from which the files are to
be restored. This parameter is optional. If this parameter is not
specified, files are restored from any copy pool in which copies can be
located.
NEWstgpool
Specifies the name of the new storage pool to which to restore the
files. This parameter is optional. If this parameter is not specified,
files are restored to the original primary storage pool (the pool being
restored).
MAXPRocess
Specifies the maximum number of parallel processes that are used for
restoring files. Using multiple, parallel processes may improve
throughput for the restore. This parameter is optional. You can specify
a value from 1 to 999. The default is 1.
When determining this value, consider the number of mount points
(logical drives) and physical drives that can be dedicated to this
operation. To access a sequential access volume, Tivoli Storage Manager
uses a mount point, and, if the device type is not FILE, a physical
drive. The number of available mount points and drives depends on other
Tivoli Storage Manager and system activity and on the mount limits of
the device classes for the sequential access storage pools that are
involved in the restore.
Each process needs a mount point for copy storage pool volumes, and, if
the device type is not FILE, each process also needs a drive. If you
are restoring files in a sequential storage pool, each process needs an
additional mount point for primary storage pool volumes and, if the
device class is not FILE, an additional drive. For example, suppose you
specify a maximum of 3 processes to restore a primary sequential
storage pool from a copy storage pool of the same device class. Each
process requires two mount points and two drives. To run all three
processes, the device class must have a mount limit of at least 6, and
at least 6 mount points and 6 drives must be available.
To preview a restore, only one process is used and no mount points or
drives are needed.
Preview
Specifies if you want to preview but not perform the restore. The
preview lets you identify volumes required to restore the storage
pool.The preview displays:
o A list of primary storage pool volumes that contain damaged files.
o The number of files and the number of bytes to be restored,
assuming that the access mode of the required copy storage pool
volumes is READWRITE or READONLY when the restore operation is
performed.
o A list of copy storage pool volumes containing files to be
restored. These volumes must be mounted if you perform the
restore.
o A list of any volumes containing files that cannot be restored.
Note:
For only a list of offsite copy storage pool volumes to be mounted
during a restore, change the access mode of the copy pool volumes
to UNAVAILABLE. This prevents reclamation and move data processing
of the volumes until they are moved onsite for the restore.
This parameter is optional. The default is NO. Possible values are:
No
Specifies that the restore is done.
Yes
Specifies that you want to preview the restore but not do the
restore.
Wait
Specifies whether to wait for the server to complete processing this
command in the foreground. This parameter is optional. The default is
NO. Possible values are:
No
Specifies that the server processes this command in the
background.
You can continue with other tasks while the command is being
processed.
Messages created from the background process are displayed either
in the activity log or the server console, depending on where
messages are logged. To cancel a background process, use the
CANCEL PROCESS command. If you cancel this process, some files may
have already been restored prior to the cancellation.
Yes
Specifies that the server performs this operation in the
foreground. The operation must complete before you can continue
with other tasks. The server then displays the output messages to
the administrative client when the operation completes.
Note:
You cannot specify WAIT=YES from the server console.
Regards
Thomas