Converting a primary storage pool to a container storage pool

Convert a primary storage pool that uses a FILE device class, a tape device class, or a virtual tape library (VTL) to a container storage pool. Data that is stored in a container storage pool can use both inline data deduplication and inline compression.

Before you begin

To ensure that volumes in a source storage pool and associated copy storage pools are not reused during a conversion process, specify a value for the REUSEDELAY parameter on the UPDATE STGPOOL command. Specify a value for the REUSEDELAY parameter that is greater than the conversion duration. You might have to delay reuse of volumes for the following reasons:

You inadvertently delete the data during storage pool conversion.
You need source storage pool functionality that is not available in container storage pools.

Tip: When you specify the REUSEDELAY parameter and a conversion operation is in progress, some storage space is unavailable in the source storage pool until the value of the parameter expires.

Create a container storage pool where data will be moved by completing the following steps:

On the Storage Pools page of the Operations Center, click + Storage Pool.
Complete the steps in the Add Storage Pool wizard. Select the type of container-based storage that you require.

About this task

By converting a storage pool to a container storage pool, you remove the need for volume reclamation. The omission of volume reclamation operations can help to improve server performance and reduce the amount of required storage hardware.

As files are converted, any copies that are stored in copy pools or active-data pools are deleted.

Restrictions:

If the source pool is specified as a backup, archive, or migration destination in an active policy set that has pending changes, you must activate those changes before you can convert the pool.
To ensure that the destination specifies a storage pool that is not converted or undergoing conversion, you must update all policies that reference the source storage pool.
If the source storage pool is specified as a next storage pool, you must update the NEXTSTGPOOL parameter on the UPDATE STGPOOL command to specify a random-access or sequential-access storage pool that is not being converted.
The following data types are not eligible for conversion: table of contents (TOC) backups, virtual volumes, and Network Data Management Protocol (NDMP) data. Before you start the conversion process, manually delete these data types from the storage pool, move the data types to a different primary storage pool, or allow the data types to expire based on policy settings.
When you convert a storage pool with a FILE device class to a directory-container pool, the target storage pool should be approximately 30% larger than the source storage pool. Additional space is not typically required when you convert other storage pool types.
For more information about best practices for storage pool conversion, see Best practices for IBM Spectrum Protect storage pool conversion.
If the source storage pool is used to store TOC backups, ensure that another primary storage pool is available to store new TOC backups. Existing TOC backups are not moved during conversion.
The TOC pool must use a NATIVE or NONBLOCK data format and a device class other than Centera. To avoid mount delays, use a DISK or FILE device class.

Procedure

On the Storage Pools page of the Operations Center, select a storage pool that uses a FILE device class, a tape device class, or VTL.
Click More > Convert and complete the steps in the Convert Storage Pool wizard.

Tip: Schedule conversion for at least 2 hours for a storage pool that uses a FILE device class and at least 4 hours for VTL.

What to do next

When the conversion process is complete, the source storage pool might contain damaged data or data that is incompatible with container storage pools. Clean up the source storage pool by completing the steps in Cleaning up objects after storage pool conversion.