Moving database to replacement logical volume

[kielhurley]

Our TSM database resides on an oddly configured disk setup with an even odder RAID configuration (a Volume Group spanning a RAID 1 and RAID 17). The database is nearing capacity and we'd rather not just add additional disks to that array, so were considering using a new (larger) array presented as one mount point.

Wondering if the below will work, or whether it will blow up on us:

1. Halt TSM
2. Mount the replacement array for the database to a temporary directory
3. Copy all files from the database directory to the temporary (replacement) directory
4. Unmount both the existing and temporary database mount points
5. Mount the replacement database directory to the database's existing path
6. Start TSM

I've found similar threads where the database was being migrated to another system or OS, and it was not recommended, however, this will be on the same system with no other changes (RHEL6, TSM 7.1.6).

Thanks

 

[marclant]

so were considering using a new (larger) array presented as one mount point.

I don't recommend using a single mountpoint. For performance reasons, the tuning section recommends 4 database directories for smaller databases and up to 8 directories for larger ones.

source: https://www.ibm.com/support/knowled...com.ibm.itsm.perf.doc/r_chklist_srvdbdsk.html

So if you are going to the trouble of carving out new space, best to do it right or else you might be in the same spot later. Therefore, you should follow this procedure instead:
https://www.ibm.com/support/knowled...bm.itsm.srv.doc/t_move_db_logs_same_srvr.html