I've used migratepv to move oracle DBs around with no problems. I would not expect any issues with using LVM mirroring or migratepv to move the TSM DB. That is what I would do in your situation.
But your comments about taking days to backup and restore your TSM DB worries me. How long does it take to backup your DB? I have a 600G allocated/415G used TSM DB. It backs up in under an hour and restore time is about the same. David Ehresman University of Louisville -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Roger Deschner Sent: Thursday, March 20, 2014 11:35 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Moving the TSM DB2 database (AIX) Now that TSM V5 is gone from our shop and we're all TSM V6.2, it's time to move some things around. Such as the TSM DB2 database. The manual says to do a full database backup and restore. That could take days of downtime with our 150-300GB databases, and a lot of angst, so that is not really acceptable. What I'm planning to do instead, is what I've always done on AIX. It's one of the reasons I like AIX for hosting something like TSM. That is, to basically walk the database over to the new location using AIX LVM mirroring. All this with TSM up and running, albeit with a performance impact. (It's Spring Break, so the performance impact is acceptable.) The end result will be that the database has exactly the same Unix filesystem names, path names, and file names as before, except that it will be on a nice new faster disk subsystem. Other than the obvious performance impact while AIX LVM is doing the mirroring, is there anything wrong with moving a TSM DB2 database by this method? Anybody done this and had problems? Roger Deschner University of Illinois at Chicago rog...@uic.edu ======I have not lost my mind -- it is backed up on tape somewhere.=====