Reclaiming tape volumes in container-copy storage pools

You can reclaim tape volumes in container-copy storage pools without running a protection operation when you don't have time to allow both protection and reclamation operations.

About this task

When you issue the PROTECT STGPOOL command and the target storage pool is a container-copy storage pool, both protection and reclamation operations run by default. The preferred practice is to allow both protection and reclamation operations to run. However, to save time, you can run only the storage pool protection operation or only reclamation, or you can limit the number of tape volumes that are reclaimed. Use this procedure only when you have to reclaim tape volumes quickly or when you have to reclaim a limited number of tape volumes.

Procedure

To reclaim tape volumes without running a storage pool protection operation, complete the following steps:

Optional: To maximize the amount of space that is reclaimed, start the inventory expiration process by issuing the EXPIRE INVENTORY command.
Determine whether you want reclamation to run to completion or limit the number of tape volumes that are reclaimed.
To run reclamation to completion, issue the PROTECT STGPOOL command and specify the TYPE=LOCAL and RECLAIM=ONLY parameters. For example, to reclaim space in a local container-copy storage pool that is defined as the target protection pool for SPOOL1, issue the following command:
```
protect stgpool spool1 type=local reclaim=only
```
To reclaim a limited number of tape volumes, complete the following steps:
1. Set a reclamation limit for the container-copy storage pool by issuing the UPDATE STGPOOL command and specifying the RECLAIMLIMIT parameter. This parameter limits the number of volumes in the container-copy storage pool that are reclaimed.
2. Issue the PROTECT STGPOOL command and specify the TYPE=LOCAL parameter along with either the RECLAIM=YESLIMITED or RECLAIM=ONLYLIMITED parameter.
  Tip: When you specify RECLAIM=YESLIMITED, both reclamation and storage pool protection operations run when the PROTECT STGPOOL command is issued. When you specify RECLAIM=ONLYLIMITED, reclamation is the only operation that runs. When you specify either of these values, reclamation runs only until it reaches the reclamation limit that is defined for the container-copy storage pool. The reclamation limit is defined with the RECLAIMLIMIT parameter on the DEFINE STGPOOL or UPDATE STGPOOL command.
  
  For example, to reclaim a limit of five tape volumes in a container-copy storage pool that is named CCPOOL1 without running a protection operation on the source directory-container storage pool that is named SPOOL1, issue the following commands:
```
update stgpool ccpool1 reclaimlimit=5
protect stgpool spool1 type=local reclaim=onlylimited
```
  For example, to protect a storage pool that is named SPOOL1 and to reclaim a maximum of 10 tape volumes in the associated container-copy storage pool, issue the following commands:
```
update stgpool spool1 reclaimlimit=10
protect stgpool spool1 type=local reclaim=yeslimited
```

Results

Reclamation processing for the container-copy storage pool is completed. The storage pool protection operation did not run, so data in the directory-container storage pool that was updated since the last protection operation is not protected.

What to do next

Protect the data in the directory-container storage pool to the container-copy storage pool by issuing the PROTECT STGPOOL command and specifying the TYPE=LOCAL parameter. The protection process runs with the default RECLAIM=YES parameter. The protection operation takes less time because reclamation already ran.
For example, to protect the data in a directory-container storage pool that is named SPOOL1, issue the following command:
```
protect stgpool spool1 type=local
```
Alternatively, protect the data in a directory-container storage pool that is named SPOOL1 without running reclamation by issuing the following command:
```
protect stgpool spool1 type=local reclaim=no
```
Back up the server database and run scheduled maintenance operations. For instructions, see Defining schedules for server maintenance activities.