Re: Expanding ADSM DB Using Raw Logical Volumes. help please
TSM development recommedns using JFS, not raw - but Jack's right, it sure is quiker using raw. Anybody have a summary of the pros and cons? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Palmadesso Jack Sent: Monday, April 16, 2001 4:36 PM To: [EMAIL PROTECTED] Subject: Re: Expanding ADSM DB Using Raw Logical Volumes. help please Thanks to everybody who helped out today. The Db extend went great and was actually quicker than doing this with a jfs file system because you don't have to do a dsmfmt. Here are the steps I took: chose 2 stg vols on different disks. made sure no sessions or processes were active that could affect those vols performed a move data on both vols varied both vols offline matched vols in ADSM with those in AIX and took note deleted both vols from ADSM In Smitty I was able to rename both vols instead of deleting them Added the new vols back into ADSM if you ever do this make sure you name the new vol with a leading "r" This is nessasary to let ADSM know that it is a raw volume. example: /dev/radsm_db4 performed an extend DB :-) -Original Message- From: Cook, Dwight E [mailto:[EMAIL PROTECTED]] Sent: Monday, April 16, 2001 11:15 AM To: Palmadesso Jack Cc: '[EMAIL PROTECTED]' Subject: RE: Expanding ADSM DB Using Raw Logical Volumes. help please actually you should be able to vary offline a storage volume... if you have clients currently accessing your server (pushing data) the proper way to set a stg volume to readonly so you may move data off it and delete it would be vary offline some_stg_vol upd some_stg_vol acc=reado vary online some_stg_vol move data some_stg_vol (when done) delete some_stg_vol then do the smitty voodoo magic to delete the logical volume and redefine it with the new name of your choice, followed up with define dbvol xxx define dbcopy xxx yyy extend db then :-) :-) :-) -Original Message- From: Palmadesso Jack [mailto:[EMAIL PROTECTED]] Sent: Monday, April 16, 2001 9:03 AM To: 'Cook, Dwight E' Cc: '[EMAIL PROTECTED]' Subject: RE: Expanding ADSM DB Using Raw Logical Volumes. help please Thank you. I have not went ahead with anything yet. I was suspicious of the dsmfmt command because there is no filname to specify with raw volumes! I inherited 2 old ADSM servers that are using all raw vols for ADSM. I've never had to work directly with the volumes before and the admin V3 manuals really don't say much about them. So now would this be the correct proceedure? Database backup already performed by the way. 1. Move Data from chosen storage pool vols 2. Vary off the volumes I have already chosen from ADSM Storage pool vols cannot be varied off so I guess move to the next step? 3. Delete the vols from ADSM 4. In Smitty rename the volumes to reflect new status of DB vols instead of stg vols 5. Define db vol and copy 6. Extend DB And it should all be happy? Jack -Original Message- From: Cook, Dwight E [mailto:[EMAIL PROTECTED]] Sent: Monday, April 16, 2001 9:02 AM To: Palmadesso Jack; [EMAIL PROTECTED] Subject: RE: Expanding ADSM DB Using Raw Logical Volumes. help please OOOPPPSss with raw logical volumes you can't run dsmfmt against them... you just do a define dbvol & define dbcopy with the /dev/rblah I've used raw volumes in the past for db & log vols, that works... now though, I tend to go ahead and use JFS files for db & log and raws for storage volumes but I went through a wave of improper handling of raw volumes in AIX 4.2, you should still be OK in aix 4.1 DWight -Original Message- From: Palmadesso Jack [mailto:[EMAIL PROTECTED]] Sent: Monday, April 16, 2001 7:39 AM To: [EMAIL PROTECTED] Subject: Expanding ADSM DB Using Raw Logical Volumes. help please One of our older ADSM servers DB hit 98% over the weekend. I am putting together a proceedure to grow its DB. As far as I can tell these are the steps I need to take. First here is the hardware and software levels. RS6k F30 ADSM 3.1.2 level 40 (has been running smooth as silk for years)upgrade to 4 in progress AIX 4.1.5 (I know its old) Breece Hill Q47 w/3 DLT 4000 (attached as standard SCSI Library) All Storage pools and DB vols are on Raw Logical Volumes. We use ADSM mirroring for DBs These are the steps I've come up with. 1. Move Data from chosen storage pool vols 2. Vary off the volumes I have already chosen from ADSM 3. Delete the vols from ADSM 4. In Smitty rename the volumes to reflect new status of DB vols instead of stg vols 5. Peform DSMFMT for DB on newly renamed vols. 6. Add vols (1 primary and 1 mirror) to ADSM DB 7. Extend DB Anybody see anything wrong with these steps? Jack Palmadesso Siemens Westinghouse Power Corp.
Re: Expanding ADSM DB Using Raw Logical Volumes. help please
Thanks to everybody who helped out today. The Db extend went great and was actually quicker than doing this with a jfs file system because you don't have to do a dsmfmt. Here are the steps I took: chose 2 stg vols on different disks. made sure no sessions or processes were active that could affect those vols performed a move data on both vols varied both vols offline matched vols in ADSM with those in AIX and took note deleted both vols from ADSM In Smitty I was able to rename both vols instead of deleting them Added the new vols back into ADSM if you ever do this make sure you name the new vol with a leading "r" This is nessasary to let ADSM know that it is a raw volume. example: /dev/radsm_db4 performed an extend DB :-) -Original Message- From: Cook, Dwight E [mailto:[EMAIL PROTECTED]] Sent: Monday, April 16, 2001 11:15 AM To: Palmadesso Jack Cc: '[EMAIL PROTECTED]' Subject: RE: Expanding ADSM DB Using Raw Logical Volumes. help please actually you should be able to vary offline a storage volume... if you have clients currently accessing your server (pushing data) the proper way to set a stg volume to readonly so you may move data off it and delete it would be vary offline some_stg_vol upd some_stg_vol acc=reado vary online some_stg_vol move data some_stg_vol (when done) delete some_stg_vol then do the smitty voodoo magic to delete the logical volume and redefine it with the new name of your choice, followed up with define dbvol xxx define dbcopy xxx yyy extend db then :-) :-) :-) -Original Message- From: Palmadesso Jack [mailto:[EMAIL PROTECTED]] Sent: Monday, April 16, 2001 9:03 AM To: 'Cook, Dwight E' Cc: '[EMAIL PROTECTED]' Subject: RE: Expanding ADSM DB Using Raw Logical Volumes. help please Thank you. I have not went ahead with anything yet. I was suspicious of the dsmfmt command because there is no filname to specify with raw volumes! I inherited 2 old ADSM servers that are using all raw vols for ADSM. I've never had to work directly with the volumes before and the admin V3 manuals really don't say much about them. So now would this be the correct proceedure? Database backup already performed by the way. 1. Move Data from chosen storage pool vols 2. Vary off the volumes I have already chosen from ADSM Storage pool vols cannot be varied off so I guess move to the next step? 3. Delete the vols from ADSM 4. In Smitty rename the volumes to reflect new status of DB vols instead of stg vols 5. Define db vol and copy 6. Extend DB And it should all be happy? Jack -Original Message- From: Cook, Dwight E [mailto:[EMAIL PROTECTED]] Sent: Monday, April 16, 2001 9:02 AM To: Palmadesso Jack; [EMAIL PROTECTED] Subject: RE: Expanding ADSM DB Using Raw Logical Volumes. help please OOOPPPSss with raw logical volumes you can't run dsmfmt against them... you just do a define dbvol & define dbcopy with the /dev/rblah I've used raw volumes in the past for db & log vols, that works... now though, I tend to go ahead and use JFS files for db & log and raws for storage volumes but I went through a wave of improper handling of raw volumes in AIX 4.2, you should still be OK in aix 4.1 DWight -Original Message- From: Palmadesso Jack [mailto:[EMAIL PROTECTED]] Sent: Monday, April 16, 2001 7:39 AM To: [EMAIL PROTECTED] Subject: Expanding ADSM DB Using Raw Logical Volumes. help please One of our older ADSM servers DB hit 98% over the weekend. I am putting together a proceedure to grow its DB. As far as I can tell these are the steps I need to take. First here is the hardware and software levels. RS6k F30 ADSM 3.1.2 level 40 (has been running smooth as silk for years)upgrade to 4 in progress AIX 4.1.5 (I know its old) Breece Hill Q47 w/3 DLT 4000 (attached as standard SCSI Library) All Storage pools and DB vols are on Raw Logical Volumes. We use ADSM mirroring for DBs These are the steps I've come up with. 1. Move Data from chosen storage pool vols 2. Vary off the volumes I have already chosen from ADSM 3. Delete the vols from ADSM 4. In Smitty rename the volumes to reflect new status of DB vols instead of stg vols 5. Peform DSMFMT for DB on newly renamed vols. 6. Add vols (1 primary and 1 mirror) to ADSM DB 7. Extend DB Anybody see anything wrong with these steps? Jack Palmadesso Siemens Westinghouse Power Corp.
Re: Expanding ADSM DB Using Raw Logical Volumes. help please
actually you should be able to vary offline a storage volume... if you have clients currently accessing your server (pushing data) the proper way to set a stg volume to readonly so you may move data off it and delete it would be vary offline some_stg_vol upd some_stg_vol acc=reado vary online some_stg_vol move data some_stg_vol (when done) delete some_stg_vol then do the smitty voodoo magic to delete the logical volume and redefine it with the new name of your choice, followed up with define dbvol xxx define dbcopy xxx yyy extend db then :-) :-) :-) -Original Message- From: Palmadesso Jack [mailto:[EMAIL PROTECTED]] Sent: Monday, April 16, 2001 9:03 AM To: 'Cook, Dwight E' Cc: '[EMAIL PROTECTED]' Subject: RE: Expanding ADSM DB Using Raw Logical Volumes. help please Thank you. I have not went ahead with anything yet. I was suspicious of the dsmfmt command because there is no filname to specify with raw volumes! I inherited 2 old ADSM servers that are using all raw vols for ADSM. I've never had to work directly with the volumes before and the admin V3 manuals really don't say much about them. So now would this be the correct proceedure? Database backup already performed by the way. 1. Move Data from chosen storage pool vols 2. Vary off the volumes I have already chosen from ADSM Storage pool vols cannot be varied off so I guess move to the next step? 3. Delete the vols from ADSM 4. In Smitty rename the volumes to reflect new status of DB vols instead of stg vols 5. Define db vol and copy 6. Extend DB And it should all be happy? Jack -Original Message- From: Cook, Dwight E [mailto:[EMAIL PROTECTED]] Sent: Monday, April 16, 2001 9:02 AM To: Palmadesso Jack; [EMAIL PROTECTED] Subject: RE: Expanding ADSM DB Using Raw Logical Volumes. help please OOOPPPSss with raw logical volumes you can't run dsmfmt against them... you just do a define dbvol & define dbcopy with the /dev/rblah I've used raw volumes in the past for db & log vols, that works... now though, I tend to go ahead and use JFS files for db & log and raws for storage volumes but I went through a wave of improper handling of raw volumes in AIX 4.2, you should still be OK in aix 4.1 DWight -Original Message- From: Palmadesso Jack [mailto:[EMAIL PROTECTED]] Sent: Monday, April 16, 2001 7:39 AM To: [EMAIL PROTECTED] Subject: Expanding ADSM DB Using Raw Logical Volumes. help please One of our older ADSM servers DB hit 98% over the weekend. I am putting together a proceedure to grow its DB. As far as I can tell these are the steps I need to take. First here is the hardware and software levels. RS6k F30 ADSM 3.1.2 level 40 (has been running smooth as silk for years)upgrade to 4 in progress AIX 4.1.5 (I know its old) Breece Hill Q47 w/3 DLT 4000 (attached as standard SCSI Library) All Storage pools and DB vols are on Raw Logical Volumes. We use ADSM mirroring for DBs These are the steps I've come up with. 1. Move Data from chosen storage pool vols 2. Vary off the volumes I have already chosen from ADSM 3. Delete the vols from ADSM 4. In Smitty rename the volumes to reflect new status of DB vols instead of stg vols 5. Peform DSMFMT for DB on newly renamed vols. 6. Add vols (1 primary and 1 mirror) to ADSM DB 7. Extend DB Anybody see anything wrong with these steps? Jack Palmadesso Siemens Westinghouse Power Corp.
Re: Expanding ADSM DB Using Raw Logical Volumes. help please
Thank you. I have not went ahead with anything yet. I was suspicious of the dsmfmt command because there is no filname to specify with raw volumes! I inherited 2 old ADSM servers that are using all raw vols for ADSM. I've never had to work directly with the volumes before and the admin V3 manuals really don't say much about them. So now would this be the correct proceedure? Database backup already performed by the way. 1. Move Data from chosen storage pool vols 2. Vary off the volumes I have already chosen from ADSM Storage pool vols cannot be varied off so I guess move to the next step? 3. Delete the vols from ADSM 4. In Smitty rename the volumes to reflect new status of DB vols instead of stg vols 5. Define db vol and copy 6. Extend DB And it should all be happy? Jack -Original Message- From: Cook, Dwight E [mailto:[EMAIL PROTECTED]] Sent: Monday, April 16, 2001 9:02 AM To: Palmadesso Jack; [EMAIL PROTECTED] Subject: RE: Expanding ADSM DB Using Raw Logical Volumes. help please OOOPPPSss with raw logical volumes you can't run dsmfmt against them... you just do a define dbvol & define dbcopy with the /dev/rblah I've used raw volumes in the past for db & log vols, that works... now though, I tend to go ahead and use JFS files for db & log and raws for storage volumes but I went through a wave of improper handling of raw volumes in AIX 4.2, you should still be OK in aix 4.1 DWight -Original Message- From: Palmadesso Jack [mailto:[EMAIL PROTECTED]] Sent: Monday, April 16, 2001 7:39 AM To: [EMAIL PROTECTED] Subject: Expanding ADSM DB Using Raw Logical Volumes. help please One of our older ADSM servers DB hit 98% over the weekend. I am putting together a proceedure to grow its DB. As far as I can tell these are the steps I need to take. First here is the hardware and software levels. RS6k F30 ADSM 3.1.2 level 40 (has been running smooth as silk for years)upgrade to 4 in progress AIX 4.1.5 (I know its old) Breece Hill Q47 w/3 DLT 4000 (attached as standard SCSI Library) All Storage pools and DB vols are on Raw Logical Volumes. We use ADSM mirroring for DBs These are the steps I've come up with. 1. Move Data from chosen storage pool vols 2. Vary off the volumes I have already chosen from ADSM 3. Delete the vols from ADSM 4. In Smitty rename the volumes to reflect new status of DB vols instead of stg vols 5. Peform DSMFMT for DB on newly renamed vols. 6. Add vols (1 primary and 1 mirror) to ADSM DB 7. Extend DB Anybody see anything wrong with these steps? Jack Palmadesso Siemens Westinghouse Power Corp.
Re: Expanding ADSM DB Using Raw Logical Volumes. help please
OOOPPPSss with raw logical volumes you can't run dsmfmt against them... you just do a define dbvol & define dbcopy with the /dev/rblah I've used raw volumes in the past for db & log vols, that works... now though, I tend to go ahead and use JFS files for db & log and raws for storage volumes but I went through a wave of improper handling of raw volumes in AIX 4.2, you should still be OK in aix 4.1 DWight -Original Message- From: Palmadesso Jack [mailto:[EMAIL PROTECTED]] Sent: Monday, April 16, 2001 7:39 AM To: [EMAIL PROTECTED] Subject: Expanding ADSM DB Using Raw Logical Volumes. help please One of our older ADSM servers DB hit 98% over the weekend. I am putting together a proceedure to grow its DB. As far as I can tell these are the steps I need to take. First here is the hardware and software levels. RS6k F30 ADSM 3.1.2 level 40 (has been running smooth as silk for years)upgrade to 4 in progress AIX 4.1.5 (I know its old) Breece Hill Q47 w/3 DLT 4000 (attached as standard SCSI Library) All Storage pools and DB vols are on Raw Logical Volumes. We use ADSM mirroring for DBs These are the steps I've come up with. 1. Move Data from chosen storage pool vols 2. Vary off the volumes I have already chosen from ADSM 3. Delete the vols from ADSM 4. In Smitty rename the volumes to reflect new status of DB vols instead of stg vols 5. Peform DSMFMT for DB on newly renamed vols. 6. Add vols (1 primary and 1 mirror) to ADSM DB 7. Extend DB Anybody see anything wrong with these steps? Jack Palmadesso Siemens Westinghouse Power Corp.
Expanding ADSM DB Using Raw Logical Volumes. help please
One of our older ADSM servers DB hit 98% over the weekend. I am putting together a proceedure to grow its DB. As far as I can tell these are the steps I need to take. First here is the hardware and software levels. RS6k F30 ADSM 3.1.2 level 40 (has been running smooth as silk for years)upgrade to 4 in progress AIX 4.1.5 (I know its old) Breece Hill Q47 w/3 DLT 4000 (attached as standard SCSI Library) All Storage pools and DB vols are on Raw Logical Volumes. We use ADSM mirroring for DBs These are the steps I've come up with. 1. Move Data from chosen storage pool vols 2. Vary off the volumes I have already chosen from ADSM 3. Delete the vols from ADSM 4. In Smitty rename the volumes to reflect new status of DB vols instead of stg vols 5. Peform DSMFMT for DB on newly renamed vols. 6. Add vols (1 primary and 1 mirror) to ADSM DB 7. Extend DB Anybody see anything wrong with these steps? Jack Palmadesso Siemens Westinghouse Power Corp.
