Re: Mirrored DELETE DBVOL, LOGVOL?
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 friendly because is more complex and flexible. Zlatko Krastev IT Consultant Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by:ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject:Re: Mirrored DELETE DBVOL, LOGVOL? 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 - while you DELETE DBVOL the primary half. The AIX Logical Volume Manager is nowhere near as friendly to use as TSM's own database mirroring facility, but it does work. Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED] On Fri, 10 May 2002, Reinhard Mersch wrote: 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 deleting the entire DBVOL including all mirrors (and hence moving the contents while all mirrors are in place). In the past, I have always added the new volume as a mirror first, then deleted an old copy, then added a new mirror, ... Since this procedure does not allow changing the volume size, the volumes on my nearly 8 years old server are now much too small. The necessary consolidation exposes me to the danger described by you, so I'm hesitating ... Roger Deschner [EMAIL PROTECTED] schrieb: 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 mirror, fiddled with EXTEND DB and REDUCE DB to make it right, and did DELETE DBVOL on the old mirror. Then I did DELETE DBVOL on the old primary copy. Oops! Now I'm really exposed! There is only one copy of the old database volume, while this rather lengthly copying process proceeds. Is there any way to do a DELETE DBVOL in a mirrored way - that is delete all mirrored copies of a DBVOL at once, so that if a disk crashes in the middle of it, I will not lose my Database? That's the whole point of Database mirroring, isn't it? I'm starting to think AIX JFS mirroring might have some advantages over TSM Database/Log mirroring. Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED] -- Reinhard MerschWestfaelische Wilhelms-Universitaet Zentrum fuer Informationsverarbeitung - ehemals Universitaetsrechenzentrum Roentgenstrasse 9-13, D-48149 Muenster, Germany Tel: +49(251)83-31583 E-Mail: [EMAIL PROTECTED] Fax: +49(251)83-31653
Re: Mirrored DELETE DBVOL, LOGVOL?
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 - while you DELETE DBVOL the primary half. The AIX Logical Volume Manager is nowhere near as friendly to use as TSM's own database mirroring facility, but it does work. Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED] On Fri, 10 May 2002, Reinhard Mersch wrote: 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 deleting the entire DBVOL including all mirrors (and hence moving the contents while all mirrors are in place). In the past, I have always added the new volume as a mirror first, then deleted an old copy, then added a new mirror, ... Since this procedure does not allow changing the volume size, the volumes on my nearly 8 years old server are now much too small. The necessary consolidation exposes me to the danger described by you, so I'm hesitating ... Roger Deschner [EMAIL PROTECTED] schrieb: 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 mirror, fiddled with EXTEND DB and REDUCE DB to make it right, and did DELETE DBVOL on the old mirror. Then I did DELETE DBVOL on the old primary copy. Oops! Now I'm really exposed! There is only one copy of the old database volume, while this rather lengthly copying process proceeds. Is there any way to do a DELETE DBVOL in a mirrored way - that is delete all mirrored copies of a DBVOL at once, so that if a disk crashes in the middle of it, I will not lose my Database? That's the whole point of Database mirroring, isn't it? I'm starting to think AIX JFS mirroring might have some advantages over TSM Database/Log mirroring. Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED] -- Reinhard MerschWestfaelische Wilhelms-Universitaet Zentrum fuer Informationsverarbeitung - ehemals Universitaetsrechenzentrum Roentgenstrasse 9-13, D-48149 Muenster, Germany Tel: +49(251)83-31583 E-Mail: [EMAIL PROTECTED] Fax: +49(251)83-31653
Re: Mirrored DELETE DBVOL, LOGVOL?
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 deleting the entire DBVOL including all mirrors (and hence moving the contents while all mirrors are in place). In the past, I have always added the new volume as a mirror first, then deleted an old copy, then added a new mirror, ... Since this procedure does not allow changing the volume size, the volumes on my nearly 8 years old server are now much too small. The necessary consolidation exposes me to the danger described by you, so I'm hesitating ... Roger Deschner [EMAIL PROTECTED] schrieb: 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 mirror, fiddled with EXTEND DB and REDUCE DB to make it right, and did DELETE DBVOL on the old mirror. Then I did DELETE DBVOL on the old primary copy. Oops! Now I'm really exposed! There is only one copy of the old database volume, while this rather lengthly copying process proceeds. Is there any way to do a DELETE DBVOL in a mirrored way - that is delete all mirrored copies of a DBVOL at once, so that if a disk crashes in the middle of it, I will not lose my Database? That's the whole point of Database mirroring, isn't it? I'm starting to think AIX JFS mirroring might have some advantages over TSM Database/Log mirroring. Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED] -- Reinhard MerschWestfaelische Wilhelms-Universitaet Zentrum fuer Informationsverarbeitung - ehemals Universitaetsrechenzentrum Roentgenstrasse 9-13, D-48149 Muenster, Germany Tel: +49(251)83-31583 E-Mail: [EMAIL PROTECTED] Fax: +49(251)83-31653
Re: Mirrored DELETE DBVOL, LOGVOL?
create a third mirror. Create it and then delete the other thus you are not exposed -Original Message- From: Roger Deschner [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 09, 2002 3:11 PM To: [EMAIL PROTECTED] Subject: Mirrored DELETE DBVOL, LOGVOL? 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 mirror, fiddled with EXTEND DB and REDUCE DB to make it right, and did DELETE DBVOL on the old mirror. Then I did DELETE DBVOL on the old primary copy. Oops! Now I'm really exposed! There is only one copy of the old database volume, while this rather lengthly copying process proceeds. Is there any way to do a DELETE DBVOL in a mirrored way - that is delete all mirrored copies of a DBVOL at once, so that if a disk crashes in the middle of it, I will not lose my Database? That's the whole point of Database mirroring, isn't it? I'm starting to think AIX JFS mirroring might have some advantages over TSM Database/Log mirroring. Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED]
Mirrored DELETE DBVOL, LOGVOL?
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 mirror, fiddled with EXTEND DB and REDUCE DB to make it right, and did DELETE DBVOL on the old mirror. Then I did DELETE DBVOL on the old primary copy. Oops! Now I'm really exposed! There is only one copy of the old database volume, while this rather lengthly copying process proceeds. Is there any way to do a DELETE DBVOL in a mirrored way - that is delete all mirrored copies of a DBVOL at once, so that if a disk crashes in the middle of it, I will not lose my Database? That's the whole point of Database mirroring, isn't it? I'm starting to think AIX JFS mirroring might have some advantages over TSM Database/Log mirroring. Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED]
Re: Mirrored DELETE DBVOL, LOGVOL?
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 other mirror-half. Both of the mirror-halves be empty when the 1st 'delete dbvol' completes. The primary is defined, but is empty and won't really be part of the DB until another 'extend db' has been performed. Kent Monthei GlaxoSmithKline Roger Deschner [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 09-May-2002 16:10 Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To: ADSM-L cc: Subject:Mirrored DELETE DBVOL, LOGVOL? 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 mirror, fiddled with EXTEND DB and REDUCE DB to make it right, and did DELETE DBVOL on the old mirror. Then I did DELETE DBVOL on the old primary copy. Oops! Now I'm really exposed! There is only one copy of the old database volume, while this rather lengthly copying process proceeds. Is there any way to do a DELETE DBVOL in a mirrored way - that is delete all mirrored copies of a DBVOL at once, so that if a disk crashes in the middle of it, I will not lose my Database? That's the whole point of Database mirroring, isn't it? I'm starting to think AIX JFS mirroring might have some advantages over TSM Database/Log mirroring. Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED]
Re: Mirrored DELETE DBVOL, LOGVOL?
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 entry. Actual data move happens when you move primary/last mirror copy of the dbvol in question. And TSM LVM does not forbid you to have one volume with two (or even three) mirror copies and another one without any redundancy. It is just the same as AIX LVM - you can have one LV with mirrors and another without. Zlatko Krastev IT Consulant Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by:ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject:Re: Mirrored DELETE DBVOL, LOGVOL? 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 other mirror-half. Both of the mirror-halves be empty when the 1st 'delete dbvol' completes. The primary is defined, but is empty and won't really be part of the DB until another 'extend db' has been performed. Kent Monthei GlaxoSmithKline Roger Deschner [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 09-May-2002 16:10 Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To: ADSM-L cc: Subject:Mirrored DELETE DBVOL, LOGVOL? 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 mirror, fiddled with EXTEND DB and REDUCE DB to make it right, and did DELETE DBVOL on the old mirror. Then I did DELETE DBVOL on the old primary copy. Oops! Now I'm really exposed! There is only one copy of the old database volume, while this rather lengthly copying process proceeds. Is there any way to do a DELETE DBVOL in a mirrored way - that is delete all mirrored copies of a DBVOL at once, so that if a disk crashes in the middle of it, I will not lose my Database? That's the whole point of Database mirroring, isn't it? I'm starting to think AIX JFS mirroring might have some advantages over TSM Database/Log mirroring. Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED]
