We are running TSM version 8.1.11.0 on rhel 8.4. We have a primary storage pool and a copy storage pool which are both on disk. The underlying storage for our primary storage pool will be out of support soon and I need to move all of the data in the primary storage pool to newly allocated storage and then reclaim all of the underlying storage that will be out of support.
Is this the most efficient method to accomplish this task with minimal impact on existing daily backups?
1. Allocate sufficient new storage for the primary storage pool to accommodate all of the existing data in the pool.
2. Change the device class for the primary storage pool to only include directories for the new storage.
3. Issue the "move data volume_name" command to move data to one of the new directories.
4. Wait until the reuse delay period for the storage pool has expired.
5. Reclaim all of the LUNs for the unsupported storage.
Are these steps correct and/or are there more efficient methods to replace the unsupported storage with new storage? I currently have about 150 TB of storage allocated on 5,000 TSM allocated volumes that would need to be moved to new storage.
Is this the most efficient method to accomplish this task with minimal impact on existing daily backups?
1. Allocate sufficient new storage for the primary storage pool to accommodate all of the existing data in the pool.
2. Change the device class for the primary storage pool to only include directories for the new storage.
3. Issue the "move data volume_name" command to move data to one of the new directories.
4. Wait until the reuse delay period for the storage pool has expired.
5. Reclaim all of the LUNs for the unsupported storage.
Are these steps correct and/or are there more efficient methods to replace the unsupported storage with new storage? I currently have about 150 TB of storage allocated on 5,000 TSM allocated volumes that would need to be moved to new storage.