Oh, I guess it's just my paranoid mind at work again, but DELETE DBVOL scares me. I'm using it to migrate the TSM Database from old disks to new, faster disks. So, I attached the new dbvol and its mi
Author: Kent Monthei <Kent.J.Monthei AT GSK DOT COM>
Date: Thu, 9 May 2002 18:11:16 -0400
IMO, I think this is a moot issue. The 1st thing 'delete dbvol' does is move any db data from the subject dbvol (both mirror-halves, because they are still sync'd) to another dbvol - but not to the o
Author: Zlatko Krastev <acit AT ATTGLOBAL DOT NET>
Date: Fri, 10 May 2002 02:21:46 +0300
You can delete (copy) dbvol even without reducing the DB and having it almost full. If the dbvol to be deleted is a mirror copy TSM LVM breaks the mirror (no any data move) and just deletes volume en
Author: Reinhard Mersch <mersch AT UNI-MUENSTER DOT DE>
Date: Fri, 10 May 2002 10:25:03 +0200
Roger, I agree, I also feel very uncomfortable living without a mirror, even for a limited time. The admin interface should be enhanced to allow for distinguishing between removing a DBCOPY from dele
I think I have found a way, although it's a little cumbersome. First, have AIX mirror one of your TSM mirror volumes. Now DELETE DBVOL the other member of the pair, and you're still mirrored - by AIX
Author: Zlatko Krastev <acit AT ATTGLOBAL DOT NET>
Date: Fri, 24 May 2002 16:44:41 +0300
You are as much as possible close to target. The only issue you have to count is AIX mirroring does not provide the database write consistency TSM mirroring provides. Regarding AIX LVM - it is not so