Re: Relocating TSM DB (storage)
We would do that, but we're moving it to a different volume group. -Original Message- From: David Longo [mailto:[EMAIL PROTECTED]] Sent: Friday, November 22, 2002 11:38 AM To: [EMAIL PROTECTED] Subject: Re: Relocating TSM DB (storage) I've followed the comments on this and have a different observation. If you just want to move to different ESS disks without any changes to TSM DB VOLs then here is an alternative, with an assumption that your TSM server is on AIX platform - you didn't say. If say you have 10 ESS disks assigned to the TSM DB, then assign 10 more wherever you want them. Then run cfgmgr to get new disks and assign them to the VG that TSM DB is on. At AIX level, create mirrors from old to new disks, by LV if you want and sync up the mirrors. Check that every thing is o.k., then break the mirror to the old disks and remove them from AIX and delete them at ESS. I haven't done this with TSM DB but have done it on AIX and ESS from a number of systems with running Oracle, Sybase and other stuff. Advantage to this is that it is totally transparent to application and users except for some performance slowness while syncing mirrors. David B. Longo System Administrator Health First, Inc. 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5509 [EMAIL PROTECTED] >>> [EMAIL PROTECTED] 11/22/02 09:30AM >>> I am wanting to move our TSM DB which is currently on ESS, and has 37 1GB dbvolumes, to another set of ESS disk. If I define the new dbvolumes on the new disks, do I then just extend the db, and then do a del dbvol on the old ones? Does the delete make the data migrate over? Do I have to do a reduce db for any reason before I do the delete dbvol? Can I do the delete with the server up and running? Thanks This E-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended only for the use of the Individual(s) named above. If you are not the intended recipient of this E-mail, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination or copying of this E-mail is strictly prohibited. If you have received this E-mail in error, please immediately notify us at (865) 374-4900 or notify us by E-mail at [EMAIL PROTECTED] "MMS " made the following annotations on 11/22/2002 11:39:21 AM -- This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. == This E-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended only for the use of the Individual(s) named above. If you are not the intended recipient of this E-mail, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination or copying of this E-mail is strictly prohibited. If you have received this E-mail in error, please immediately notify us at (865) 374-4900 or notify us by E-mail at [EMAIL PROTECTED]
Re: Relocating TSM DB (storage)
I've followed the comments on this and have a different observation. If you just want to move to different ESS disks without any changes to TSM DB VOLs then here is an alternative, with an assumption that your TSM server is on AIX platform - you didn't say. If say you have 10 ESS disks assigned to the TSM DB, then assign 10 more wherever you want them. Then run cfgmgr to get new disks and assign them to the VG that TSM DB is on. At AIX level, create mirrors from old to new disks, by LV if you want and sync up the mirrors. Check that every thing is o.k., then break the mirror to the old disks and remove them from AIX and delete them at ESS. I haven't done this with TSM DB but have done it on AIX and ESS from a number of systems with running Oracle, Sybase and other stuff. Advantage to this is that it is totally transparent to application and users except for some performance slowness while syncing mirrors. David B. Longo System Administrator Health First, Inc. 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5509 [EMAIL PROTECTED] >>> [EMAIL PROTECTED] 11/22/02 09:30AM >>> I am wanting to move our TSM DB which is currently on ESS, and has 37 1GB dbvolumes, to another set of ESS disk. If I define the new dbvolumes on the new disks, do I then just extend the db, and then do a del dbvol on the old ones? Does the delete make the data migrate over? Do I have to do a reduce db for any reason before I do the delete dbvol? Can I do the delete with the server up and running? Thanks This E-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended only for the use of the Individual(s) named above. If you are not the intended recipient of this E-mail, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination or copying of this E-mail is strictly prohibited. If you have received this E-mail in error, please immediately notify us at (865) 374-4900 or notify us by E-mail at [EMAIL PROTECTED] "MMS " made the following annotations on 11/22/2002 11:39:21 AM -- This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. ==
Re: Relocating TSM DB (storage)
It will not. -Original Message- From: John Wright [mailto:[EMAIL PROTECTED]] Sent: Friday, November 22, 2002 10:46 AM To: [EMAIL PROTECTED] Subject: Re: Relocating TSM DB (storage) Any idea if moving database data between volumes like this will free any fragmented space as it moves the data? Cheers John "Zlatko Krastev/ACIT" To: ADSM-L Sent by: cc: "ADSM: Dist Subject: Re: Relocating TSM DB (storage) Stor Manager" <[EMAIL PROTECTED] IST.EDU> 22-Nov-2002 15:17 Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] IST.EDU> Think for "available" as total space and for "assigned" as maximum used. This is like hot-spare disk you may or may not put in your RAID array. TSM allows a volume to be deleted only if it is smaller than Available minus Assigned, i.e. there is available but unassigned space to move data from volume to be deleted. Zlatko Krastev IT Consultant "Robert L. Rippy" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 22.11.2002 16:49 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Re: Relocating TSM DB (storage) If you don't extend and create more 'available' space, then how is there space available to move the DB's to when you start deleting volumes? Before TSM can use DB space, you must extend and make the space available for use. Thanks, Robert Rippy From: Andy Carlson <[EMAIL PROTECTED]> on 11/22/2002 09:42 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Re: Relocating TSM DB (storage) Do not extend the DB before doing the delete dbvol. The delete command uses the empty, enextended space to move the data from the volumes to be deleted. Andy Carlson|\ _,,,---,,_ Senior Technical Specialist ZZZzz /,`.-'`'-. ;-;;,_ BJC Health Care|,4- ) )-,_. ,\ ( `'-' St. Louis, Missouri '---''(_/--' `-'\_) Cat Pics: http://andyc.dyndns.org/animal.html On Fri, 22 Nov 2002, Robert L. Rippy wrote: > Yes, you are correct. Create the new DB's and extend the DB and then delete > the old DB's. The data will migrate over to the new extended space. Any > reason you had 37 1GB volumes for your DB's. IBM told me not to really go > over 10 volumes on your DB and to be sure they aren't on the same drive if > you can help it. > > I would suggest that if you could, create 5 8GB new volumes for a total of > 40GB and move the DB over to the new 8GB partitions. > > Thanks, > Robert Rippy > > > > From: "Thach, Kevin" <[EMAIL PROTECTED]> on 11/22/2002 09:30 AM > > Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> > > To: [EMAIL PROTECTED] > cc: > Subject: Relocating TSM DB (storage) > > I am wanting to move our TSM DB which is currently on ESS, and has 37 1GB > dbvolumes, to another set of ESS disk. If I define the new dbvolumes on > the > new disks, do I then just extend the db, and then do a del dbvol on the old > ones? Does the delete make the data migrate over? > > Do I have to do a reduce db for any reason before I do the delete dbvol? > Can I do the delete with the server up and running? > > Thanks > > This E-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended only > for the use of the Individual(s) named above. If you are not the intended > recipient of this E-mail, or the employee or agent responsible for > delivering it to the intended recipient, you are hereby notified that any > dissemination or copying of this E-mail is strictly prohibited. If you > have > received this E-mail in error, please immediately notify us at (865) > 374-4900 or notify us by E-mail at [EMAIL PROTECTED] >
Re: Relocating TSM DB (storage)
I/O, I/O, it's all about I/O. and IT DEPENDS on your hardware. The key here is that when you have the DB or a storage pool split into multiple "volumes", TSM will start multiple I/O operations to the DB or storage pool. You can use that to your advantage to improve performance, or carry it to such and extreme that it hurts your performance. If you are talking physical disk: >> when you put many DB or storage pool "volumes" on one disk, you can get multiple I/O's in flight, all trying to access the same physical disk. The disk heads get yanked back and forth from one volume location to another, and that slows you down. If you are talking ESS, that is a whole different animal. >> The "volumes" you create are really split across many physical disks inside the ESS and there is a LOT of cache in the box that buffers I/O and makes it asynchronous, so you don't have to worry much about the performance hit caused by physical head movement. If you are talking non-ESS RAID, that is different still, as every vendor's implementation is a little different. >> With simple RAID implementations on arrays made up of a few disks you can get a performance penalty on WRITE; BUT if the vendor has enough RAM in the box to buffer the I/O, you see less of an impact. In your case, I expect the objective is to get your DB spread across those ESS loops, more than specifically getting you out of a single filesystem. That spreads your I/O out to get the max advantage of the hardware. SO IT DEPENDS, you will get different answers about performance and disk configuration, and there are sometimes multiple ways to do it, depending on your hardware and the problem you are trying to solve. Wanda Prather The Johns Hopkins Applied Physics Lab 443-778-8769 [EMAIL PROTECTED] "Intelligence has much less practical application than you'd think" - Scott Adams/Dilbert -Original Message- From: Thach, Kevin [mailto:[EMAIL PROTECTED]] Sent: Friday, November 22, 2002 9:53 AM To: [EMAIL PROTECTED] Subject: Re: Relocating TSM DB (storage) Funny you should mention that. We have been working with IBM ATS support about poor performance issues with our TSM config, and they say that our problem is because we have all 37 volumes in one AIX logical volume/filesystem. They have had us create 32 new AIX logical volumes/filesystems (don't need 37 because our db is not very full after running CLEANUP BACKUPGROUPS), each with a 1GB TSM DBvol inside, all of which are on separate ESS loops. They said the smaller DB volumes are better! Argghh!! -Original Message- From: Robert L. Rippy [mailto:[EMAIL PROTECTED]] Sent: Friday, November 22, 2002 9:35 AM To: [EMAIL PROTECTED] Subject: Re: Relocating TSM DB (storage) Yes, you are correct. Create the new DB's and extend the DB and then delete the old DB's. The data will migrate over to the new extended space. Any reason you had 37 1GB volumes for your DB's. IBM told me not to really go over 10 volumes on your DB and to be sure they aren't on the same drive if you can help it. I would suggest that if you could, create 5 8GB new volumes for a total of 40GB and move the DB over to the new 8GB partitions. Thanks, Robert Rippy From: "Thach, Kevin" <[EMAIL PROTECTED]> on 11/22/2002 09:30 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Relocating TSM DB (storage) I am wanting to move our TSM DB which is currently on ESS, and has 37 1GB dbvolumes, to another set of ESS disk. If I define the new dbvolumes on the new disks, do I then just extend the db, and then do a del dbvol on the old ones? Does the delete make the data migrate over? Do I have to do a reduce db for any reason before I do the delete dbvol? Can I do the delete with the server up and running? Thanks This E-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended only for the use of the Individual(s) named above. If you are not the intended recipient of this E-mail, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination or copying of this E-mail is strictly prohibited. If you have received this E-mail in error, please immediately notify us at (865) 374-4900 or notify us by E-mail at [EMAIL PROTECTED] This E-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended only for the use of the Individual(s) named above. If you are not the intended recipient of this E-mail, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination or copying of this E-mail is strictly prohibited. If you have received this E-mail in error, please immediately notify us at (865) 374-4900 or notify us by E-mail at [EMAIL PROTECTED]
Re: Relocating TSM DB (storage)
The other guys were right about not extending. If you do, then the 'Maxium
Reduction' will be decreased and you won't be able to move. Moving will not
free up any fragmented space. I've tried it instead of a UNLOAD/LOAD to
see if it would work and no space was free'd.
Thanks,
Robert Rippy
From: John Wright <[EMAIL PROTECTED]> on 11/22/2002 10:46 AM
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Subject: Re: Relocating TSM DB (storage)
Any idea if moving database data between volumes like this will free any
fragmented space as it moves the data?
Cheers
John
"Zlatko
Krastev/ACIT"
To: ADSM-L
Sent by: cc:
"ADSM: Dist Subject: Re: Relocating TSM DB
(storage)
Stor Manager"
<[EMAIL PROTECTED]
IST.EDU>
22-Nov-2002
15:17
Please respond
to "ADSM: Dist
Stor Manager"
<[EMAIL PROTECTED]
IST.EDU>
Think for "available" as total space and for "assigned" as maximum used.
This is like hot-spare disk you may or may not put in your RAID array.
TSM allows a volume to be deleted only if it is smaller than Available
minus Assigned, i.e. there is available but unassigned space to move data
from volume to be deleted.
Zlatko Krastev
IT Consultant
"Robert L. Rippy" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
22.11.2002 16:49
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject:Re: Relocating TSM DB (storage)
If you don't extend and create more 'available' space, then how is there
space available to move the DB's to when you start deleting volumes?
Before TSM can use DB space, you must extend and make the space available
for use.
Thanks,
Robert Rippy
From: Andy Carlson <[EMAIL PROTECTED]> on 11/22/2002 09:42 AM
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Subject: Re: Relocating TSM DB (storage)
Do not extend the DB before doing the delete dbvol. The delete command
uses the empty, enextended space to move the data from the volumes to be
deleted.
Andy Carlson|\ _,,,---,,_
Senior Technical Specialist ZZZzz /,`.-'`'-. ;-;;,_
BJC Health Care|,4- ) )-,_. ,\ ( `'-'
St. Louis, Missouri '---''(_/--' `-'\_)
Cat Pics: http://andyc.dyndns.org/animal.html
On Fri, 22 Nov 2002, Robert L. Rippy wrote:
> Yes, you are correct. Create the new DB's and extend the DB and then
delete
> the old DB's. The data will migrate over to the new extended space. Any
> reason you had 37 1GB volumes for your DB's. IBM told me not to really
go
> over 10 volumes on your DB and to be sure they aren't on the same drive
if
> you can help it.
>
> I would suggest that if you could, create 5 8GB new volumes for a total
of
> 40GB and move the DB over to the new 8GB partitions.
>
> Thanks,
> Robert Rippy
>
>
>
> From: "Thach, Kevin" <[EMAIL PROTECTED]> on 11/22/2002 09:30 AM
>
> Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
>
> To: [EMAIL PROTECTED]
> cc:
> Subject: Relocating TSM DB (storage)
>
> I am wanting to move our TSM DB which is currently on ESS, and has 37
1GB
> dbvolumes, to another set of ESS disk. If I define the new dbvolumes on
> the
> new disks, do I then just extend the db, and then do a del dbvol on the
old
> ones? Does the delete make the data migrate over?
>
> Do I have to do a reduce db for any reason before I do the delete dbvol?
> Can I do the delete with the server up and running?
>
> Thanks
>
> This E-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended
only
> for the use of the Individual(s) named above. If you are not the
intended
> recipient of this E-mail, or the employee or agent responsible for
> delivering it to the intended recipient, you are hereby notified that
any
> dissemination or copying of this E-mail is strictly prohibited. If you
> have
> received this E-mail in error, please immediately notify us at (865)
> 374-4900 or notify us by E-mail at [EMAIL PROTECTED]
>
Re: Relocating TSM DB (storage)
Any idea if moving database data between volumes like this will free any fragmented space as it moves the data? Cheers John "Zlatko Krastev/ACIT" To: ADSM-L Sent by: cc: "ADSM: Dist Subject: Re: Relocating TSM DB (storage) Stor Manager" <[EMAIL PROTECTED] IST.EDU> 22-Nov-2002 15:17 Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] IST.EDU> Think for "available" as total space and for "assigned" as maximum used. This is like hot-spare disk you may or may not put in your RAID array. TSM allows a volume to be deleted only if it is smaller than Available minus Assigned, i.e. there is available but unassigned space to move data from volume to be deleted. Zlatko Krastev IT Consultant "Robert L. Rippy" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 22.11.2002 16:49 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Re: Relocating TSM DB (storage) If you don't extend and create more 'available' space, then how is there space available to move the DB's to when you start deleting volumes? Before TSM can use DB space, you must extend and make the space available for use. Thanks, Robert Rippy From: Andy Carlson <[EMAIL PROTECTED]> on 11/22/2002 09:42 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Re: Relocating TSM DB (storage) Do not extend the DB before doing the delete dbvol. The delete command uses the empty, enextended space to move the data from the volumes to be deleted. Andy Carlson|\ _,,,---,,_ Senior Technical Specialist ZZZzz /,`.-'`'-. ;-;;,_ BJC Health Care|,4- ) )-,_. ,\ ( `'-' St. Louis, Missouri '---''(_/--' `-'\_) Cat Pics: http://andyc.dyndns.org/animal.html On Fri, 22 Nov 2002, Robert L. Rippy wrote: > Yes, you are correct. Create the new DB's and extend the DB and then delete > the old DB's. The data will migrate over to the new extended space. Any > reason you had 37 1GB volumes for your DB's. IBM told me not to really go > over 10 volumes on your DB and to be sure they aren't on the same drive if > you can help it. > > I would suggest that if you could, create 5 8GB new volumes for a total of > 40GB and move the DB over to the new 8GB partitions. > > Thanks, > Robert Rippy > > > > From: "Thach, Kevin" <[EMAIL PROTECTED]> on 11/22/2002 09:30 AM > > Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> > > To: [EMAIL PROTECTED] > cc: > Subject: Relocating TSM DB (storage) > > I am wanting to move our TSM DB which is currently on ESS, and has 37 1GB > dbvolumes, to another set of ESS disk. If I define the new dbvolumes on > the > new disks, do I then just extend the db, and then do a del dbvol on the old > ones? Does the delete make the data migrate over? > > Do I have to do a reduce db for any reason before I do the delete dbvol? > Can I do the delete with the server up and running? > > Thanks > > This E-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended only > for the use of the Individual(s) named above. If you are not the intended > recipient of this E-mail, or the employee or agent responsible for > delivering it to the intended recipient, you are hereby notified that any > dissemination or copying of this E-mail is strictly prohibited. If you > have > received this E-mail in error, please immediately notify us at (865) > 374-4900 or notify us by E-mail at [EMAIL PROTECTED] >
Re: Relocating TSM DB (storage)
I just tried this on our test system, to be sure I wasn't talking out my ass, and I have done this before. To delete a dbvol that has data in it, TSM needs unexteneded space to copy it in to. If you extend the db, that is "used" space to tsm. Try this on your system, please Andy Carlson|\ _,,,---,,_ Senior Technical Specialist ZZZzz /,`.-'`'-. ;-;;,_ BJC Health Care|,4- ) )-,_. ,\ ( `'-' St. Louis, Missouri '---''(_/--' `-'\_) Cat Pics: http://andyc.dyndns.org/animal.html On Fri, 22 Nov 2002, Robert L. Rippy wrote: > If you don't extend and create more 'available' space, then how is there > space available to move the DB's to when you start deleting volumes? > Before TSM can use DB space, you must extend and make the space available > for use. > > Thanks, > Robert Rippy > > > > > From: Andy Carlson <[EMAIL PROTECTED]> on 11/22/2002 09:42 AM > > Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> > > To: [EMAIL PROTECTED] > cc: > Subject: Re: Relocating TSM DB (storage) > > Do not extend the DB before doing the delete dbvol. The delete command > uses the empty, enextended space to move the data from the volumes to be > deleted. > > > Andy Carlson|\ _,,,---,,_ > Senior Technical Specialist ZZZzz /,`.-'`'-. ;-;;,_ > BJC Health Care|,4- ) )-,_. ,\ ( `'-' > St. Louis, Missouri '---''(_/--' `-'\_) > Cat Pics: http://andyc.dyndns.org/animal.html > > > On Fri, 22 Nov 2002, Robert L. Rippy wrote: > > > Yes, you are correct. Create the new DB's and extend the DB and then > delete > > the old DB's. The data will migrate over to the new extended space. Any > > reason you had 37 1GB volumes for your DB's. IBM told me not to really go > > over 10 volumes on your DB and to be sure they aren't on the same drive > if > > you can help it. > > > > I would suggest that if you could, create 5 8GB new volumes for a total > of > > 40GB and move the DB over to the new 8GB partitions. > > > > Thanks, > > Robert Rippy > > > > > > > > From: "Thach, Kevin" <[EMAIL PROTECTED]> on 11/22/2002 09:30 AM > > > > Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> > > > > To: [EMAIL PROTECTED] > > cc: > > Subject: Relocating TSM DB (storage) > > > > I am wanting to move our TSM DB which is currently on ESS, and has 37 > 1GB > > dbvolumes, to another set of ESS disk. If I define the new dbvolumes on > > the > > new disks, do I then just extend the db, and then do a del dbvol on the > old > > ones? Does the delete make the data migrate over? > > > > Do I have to do a reduce db for any reason before I do the delete dbvol? > > Can I do the delete with the server up and running? > > > > Thanks > > > > This E-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended > only > > for the use of the Individual(s) named above. If you are not the > intended > > recipient of this E-mail, or the employee or agent responsible for > > delivering it to the intended recipient, you are hereby notified that any > > dissemination or copying of this E-mail is strictly prohibited. If you > > have > > received this E-mail in error, please immediately notify us at (865) > > 374-4900 or notify us by E-mail at [EMAIL PROTECTED] > > >
Re: Relocating TSM DB (storage)
Think for "available" as total space and for "assigned" as maximum used. This is like hot-spare disk you may or may not put in your RAID array. TSM allows a volume to be deleted only if it is smaller than Available minus Assigned, i.e. there is available but unassigned space to move data from volume to be deleted. Zlatko Krastev IT Consultant "Robert L. Rippy" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 22.11.2002 16:49 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Re: Relocating TSM DB (storage) If you don't extend and create more 'available' space, then how is there space available to move the DB's to when you start deleting volumes? Before TSM can use DB space, you must extend and make the space available for use. Thanks, Robert Rippy From: Andy Carlson <[EMAIL PROTECTED]> on 11/22/2002 09:42 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Re: Relocating TSM DB (storage) Do not extend the DB before doing the delete dbvol. The delete command uses the empty, enextended space to move the data from the volumes to be deleted. Andy Carlson|\ _,,,---,,_ Senior Technical Specialist ZZZzz /,`.-'`'-. ;-;;,_ BJC Health Care|,4- ) )-,_. ,\ ( `'-' St. Louis, Missouri '---''(_/--' `-'\_) Cat Pics: http://andyc.dyndns.org/animal.html On Fri, 22 Nov 2002, Robert L. Rippy wrote: > Yes, you are correct. Create the new DB's and extend the DB and then delete > the old DB's. The data will migrate over to the new extended space. Any > reason you had 37 1GB volumes for your DB's. IBM told me not to really go > over 10 volumes on your DB and to be sure they aren't on the same drive if > you can help it. > > I would suggest that if you could, create 5 8GB new volumes for a total of > 40GB and move the DB over to the new 8GB partitions. > > Thanks, > Robert Rippy > > > > From: "Thach, Kevin" <[EMAIL PROTECTED]> on 11/22/2002 09:30 AM > > Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> > > To: [EMAIL PROTECTED] > cc: > Subject: Relocating TSM DB (storage) > > I am wanting to move our TSM DB which is currently on ESS, and has 37 1GB > dbvolumes, to another set of ESS disk. If I define the new dbvolumes on > the > new disks, do I then just extend the db, and then do a del dbvol on the old > ones? Does the delete make the data migrate over? > > Do I have to do a reduce db for any reason before I do the delete dbvol? > Can I do the delete with the server up and running? > > Thanks > > This E-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended only > for the use of the Individual(s) named above. If you are not the intended > recipient of this E-mail, or the employee or agent responsible for > delivering it to the intended recipient, you are hereby notified that any > dissemination or copying of this E-mail is strictly prohibited. If you > have > received this E-mail in error, please immediately notify us at (865) > 374-4900 or notify us by E-mail at [EMAIL PROTECTED] >
Re: Relocating TSM DB (storage)
I have found out that you hear different things from different TSM people about the same situation. But I know from experience that you must place your DB volumes on seperate filesystems on seperate physical volumes if possible for performance. Also, your 1GB volumes won't be to bad because they will fill up quick and once full, they won't get hit anymore. If you want to consolidate, then start reducing the database and releasing space. That the released space and make larger filesystems for a new Database volume. Do that until you are satisified. thanks, Robert. Rippy From: "Thach, Kevin" <[EMAIL PROTECTED]> on 11/22/2002 09:53 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Re: Relocating TSM DB (storage) Funny you should mention that. We have been working with IBM ATS support about poor performance issues with our TSM config, and they say that our problem is because we have all 37 volumes in one AIX logical volume/filesystem. They have had us create 32 new AIX logical volumes/filesystems (don't need 37 because our db is not very full after running CLEANUP BACKUPGROUPS), each with a 1GB TSM DBvol inside, all of which are on separate ESS loops. They said the smaller DB volumes are better! Argghh!! -Original Message- From: Robert L. Rippy [mailto:[EMAIL PROTECTED]] Sent: Friday, November 22, 2002 9:35 AM To: [EMAIL PROTECTED] Subject: Re: Relocating TSM DB (storage) Yes, you are correct. Create the new DB's and extend the DB and then delete the old DB's. The data will migrate over to the new extended space. Any reason you had 37 1GB volumes for your DB's. IBM told me not to really go over 10 volumes on your DB and to be sure they aren't on the same drive if you can help it. I would suggest that if you could, create 5 8GB new volumes for a total of 40GB and move the DB over to the new 8GB partitions. Thanks, Robert Rippy From: "Thach, Kevin" <[EMAIL PROTECTED]> on 11/22/2002 09:30 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Relocating TSM DB (storage) I am wanting to move our TSM DB which is currently on ESS, and has 37 1GB dbvolumes, to another set of ESS disk. If I define the new dbvolumes on the new disks, do I then just extend the db, and then do a del dbvol on the old ones? Does the delete make the data migrate over? Do I have to do a reduce db for any reason before I do the delete dbvol? Can I do the delete with the server up and running? Thanks This E-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended only for the use of the Individual(s) named above. If you are not the intended recipient of this E-mail, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination or copying of this E-mail is strictly prohibited. If you have received this E-mail in error, please immediately notify us at (865) 374-4900 or notify us by E-mail at [EMAIL PROTECTED] This E-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended only for the use of the Individual(s) named above. If you are not the intended recipient of this E-mail, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination or copying of this E-mail is strictly prohibited. If you have received this E-mail in error, please immediately notify us at (865) 374-4900 or notify us by E-mail at [EMAIL PROTECTED]
Re: Relocating TSM DB (storage)
They said for effeciency. Maybe it was just for our situation. We were creating a 300GB database and were at odds to how many volumes we should create. The TSM people said don't use more than 10. Once you get over 10 its really too much I/O and TSM will not be very efficient in writting to your DB's. Thanks, Robert Rippy. From: Niklas Lundstrom <[EMAIL PROTECTED]> on 11/22/2002 09:46 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Re: Relocating TSM DB (storage) That's interesting. Did they explain why you shouldn't use more than 10 db vols? Regards Niklas Lundström -Original Message- From: Robert L. Rippy [mailto:[EMAIL PROTECTED]] Sent: den 22 november 2002 15:35 To: [EMAIL PROTECTED] Subject: Re: Relocating TSM DB (storage) Yes, you are correct. Create the new DB's and extend the DB and then delete the old DB's. The data will migrate over to the new extended space. Any reason you had 37 1GB volumes for your DB's. IBM told me not to really go over 10 volumes on your DB and to be sure they aren't on the same drive if you can help it. I would suggest that if you could, create 5 8GB new volumes for a total of 40GB and move the DB over to the new 8GB partitions. Thanks, Robert Rippy From: "Thach, Kevin" <[EMAIL PROTECTED]> on 11/22/2002 09:30 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Relocating TSM DB (storage) I am wanting to move our TSM DB which is currently on ESS, and has 37 1GB dbvolumes, to another set of ESS disk. If I define the new dbvolumes on the new disks, do I then just extend the db, and then do a del dbvol on the old ones? Does the delete make the data migrate over? Do I have to do a reduce db for any reason before I do the delete dbvol? Can I do the delete with the server up and running? Thanks This E-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended only for the use of the Individual(s) named above. If you are not the intended recipient of this E-mail, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination or copying of this E-mail is strictly prohibited. If you have received this E-mail in error, please immediately notify us at (865) 374-4900 or notify us by E-mail at [EMAIL PROTECTED]
Re: Relocating TSM DB (storage)
If you don't extend and create more 'available' space, then how is there space available to move the DB's to when you start deleting volumes? Before TSM can use DB space, you must extend and make the space available for use. Thanks, Robert Rippy From: Andy Carlson <[EMAIL PROTECTED]> on 11/22/2002 09:42 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Re: Relocating TSM DB (storage) Do not extend the DB before doing the delete dbvol. The delete command uses the empty, enextended space to move the data from the volumes to be deleted. Andy Carlson|\ _,,,---,,_ Senior Technical Specialist ZZZzz /,`.-'`'-. ;-;;,_ BJC Health Care|,4- ) )-,_. ,\ ( `'-' St. Louis, Missouri '---''(_/--' `-'\_) Cat Pics: http://andyc.dyndns.org/animal.html On Fri, 22 Nov 2002, Robert L. Rippy wrote: > Yes, you are correct. Create the new DB's and extend the DB and then delete > the old DB's. The data will migrate over to the new extended space. Any > reason you had 37 1GB volumes for your DB's. IBM told me not to really go > over 10 volumes on your DB and to be sure they aren't on the same drive if > you can help it. > > I would suggest that if you could, create 5 8GB new volumes for a total of > 40GB and move the DB over to the new 8GB partitions. > > Thanks, > Robert Rippy > > > > From: "Thach, Kevin" <[EMAIL PROTECTED]> on 11/22/2002 09:30 AM > > Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> > > To: [EMAIL PROTECTED] > cc: > Subject: Relocating TSM DB (storage) > > I am wanting to move our TSM DB which is currently on ESS, and has 37 1GB > dbvolumes, to another set of ESS disk. If I define the new dbvolumes on > the > new disks, do I then just extend the db, and then do a del dbvol on the old > ones? Does the delete make the data migrate over? > > Do I have to do a reduce db for any reason before I do the delete dbvol? > Can I do the delete with the server up and running? > > Thanks > > This E-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended only > for the use of the Individual(s) named above. If you are not the intended > recipient of this E-mail, or the employee or agent responsible for > delivering it to the intended recipient, you are hereby notified that any > dissemination or copying of this E-mail is strictly prohibited. If you > have > received this E-mail in error, please immediately notify us at (865) > 374-4900 or notify us by E-mail at [EMAIL PROTECTED] >
Re: Relocating TSM DB (storage)
Funny you should mention that. We have been working with IBM ATS support about poor performance issues with our TSM config, and they say that our problem is because we have all 37 volumes in one AIX logical volume/filesystem. They have had us create 32 new AIX logical volumes/filesystems (don't need 37 because our db is not very full after running CLEANUP BACKUPGROUPS), each with a 1GB TSM DBvol inside, all of which are on separate ESS loops. They said the smaller DB volumes are better! Argghh!! -Original Message- From: Robert L. Rippy [mailto:[EMAIL PROTECTED]] Sent: Friday, November 22, 2002 9:35 AM To: [EMAIL PROTECTED] Subject: Re: Relocating TSM DB (storage) Yes, you are correct. Create the new DB's and extend the DB and then delete the old DB's. The data will migrate over to the new extended space. Any reason you had 37 1GB volumes for your DB's. IBM told me not to really go over 10 volumes on your DB and to be sure they aren't on the same drive if you can help it. I would suggest that if you could, create 5 8GB new volumes for a total of 40GB and move the DB over to the new 8GB partitions. Thanks, Robert Rippy From: "Thach, Kevin" <[EMAIL PROTECTED]> on 11/22/2002 09:30 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Relocating TSM DB (storage) I am wanting to move our TSM DB which is currently on ESS, and has 37 1GB dbvolumes, to another set of ESS disk. If I define the new dbvolumes on the new disks, do I then just extend the db, and then do a del dbvol on the old ones? Does the delete make the data migrate over? Do I have to do a reduce db for any reason before I do the delete dbvol? Can I do the delete with the server up and running? Thanks This E-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended only for the use of the Individual(s) named above. If you are not the intended recipient of this E-mail, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination or copying of this E-mail is strictly prohibited. If you have received this E-mail in error, please immediately notify us at (865) 374-4900 or notify us by E-mail at [EMAIL PROTECTED] This E-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended only for the use of the Individual(s) named above. If you are not the intended recipient of this E-mail, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination or copying of this E-mail is strictly prohibited. If you have received this E-mail in error, please immediately notify us at (865) 374-4900 or notify us by E-mail at [EMAIL PROTECTED]
Re: Relocating TSM DB (storage)
That's interesting. Did they explain why you shouldn't use more than 10 db vols? Regards Niklas Lundström -Original Message- From: Robert L. Rippy [mailto:[EMAIL PROTECTED]] Sent: den 22 november 2002 15:35 To: [EMAIL PROTECTED] Subject: Re: Relocating TSM DB (storage) Yes, you are correct. Create the new DB's and extend the DB and then delete the old DB's. The data will migrate over to the new extended space. Any reason you had 37 1GB volumes for your DB's. IBM told me not to really go over 10 volumes on your DB and to be sure they aren't on the same drive if you can help it. I would suggest that if you could, create 5 8GB new volumes for a total of 40GB and move the DB over to the new 8GB partitions. Thanks, Robert Rippy From: "Thach, Kevin" <[EMAIL PROTECTED]> on 11/22/2002 09:30 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Relocating TSM DB (storage) I am wanting to move our TSM DB which is currently on ESS, and has 37 1GB dbvolumes, to another set of ESS disk. If I define the new dbvolumes on the new disks, do I then just extend the db, and then do a del dbvol on the old ones? Does the delete make the data migrate over? Do I have to do a reduce db for any reason before I do the delete dbvol? Can I do the delete with the server up and running? Thanks This E-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended only for the use of the Individual(s) named above. If you are not the intended recipient of this E-mail, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination or copying of this E-mail is strictly prohibited. If you have received this E-mail in error, please immediately notify us at (865) 374-4900 or notify us by E-mail at [EMAIL PROTECTED]
Re: Relocating TSM DB (storage) (OFFDAY)
I will be out of the office from Nov. 25th to Dec.2nd. Any problems call the help desk at ext.8600
Re: Relocating TSM DB (storage)
Do not extend the DB before doing the delete dbvol. The delete command uses the empty, enextended space to move the data from the volumes to be deleted. Andy Carlson|\ _,,,---,,_ Senior Technical Specialist ZZZzz /,`.-'`'-. ;-;;,_ BJC Health Care|,4- ) )-,_. ,\ ( `'-' St. Louis, Missouri '---''(_/--' `-'\_) Cat Pics: http://andyc.dyndns.org/animal.html On Fri, 22 Nov 2002, Robert L. Rippy wrote: > Yes, you are correct. Create the new DB's and extend the DB and then delete > the old DB's. The data will migrate over to the new extended space. Any > reason you had 37 1GB volumes for your DB's. IBM told me not to really go > over 10 volumes on your DB and to be sure they aren't on the same drive if > you can help it. > > I would suggest that if you could, create 5 8GB new volumes for a total of > 40GB and move the DB over to the new 8GB partitions. > > Thanks, > Robert Rippy > > > > From: "Thach, Kevin" <[EMAIL PROTECTED]> on 11/22/2002 09:30 AM > > Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> > > To: [EMAIL PROTECTED] > cc: > Subject: Relocating TSM DB (storage) > > I am wanting to move our TSM DB which is currently on ESS, and has 37 1GB > dbvolumes, to another set of ESS disk. If I define the new dbvolumes on > the > new disks, do I then just extend the db, and then do a del dbvol on the old > ones? Does the delete make the data migrate over? > > Do I have to do a reduce db for any reason before I do the delete dbvol? > Can I do the delete with the server up and running? > > Thanks > > This E-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended only > for the use of the Individual(s) named above. If you are not the intended > recipient of this E-mail, or the employee or agent responsible for > delivering it to the intended recipient, you are hereby notified that any > dissemination or copying of this E-mail is strictly prohibited. If you > have > received this E-mail in error, please immediately notify us at (865) > 374-4900 or notify us by E-mail at [EMAIL PROTECTED] >
Re: Relocating TSM DB (storage)
Yes, you are correct. Create the new DB's and extend the DB and then delete the old DB's. The data will migrate over to the new extended space. Any reason you had 37 1GB volumes for your DB's. IBM told me not to really go over 10 volumes on your DB and to be sure they aren't on the same drive if you can help it. I would suggest that if you could, create 5 8GB new volumes for a total of 40GB and move the DB over to the new 8GB partitions. Thanks, Robert Rippy From: "Thach, Kevin" <[EMAIL PROTECTED]> on 11/22/2002 09:30 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Relocating TSM DB (storage) I am wanting to move our TSM DB which is currently on ESS, and has 37 1GB dbvolumes, to another set of ESS disk. If I define the new dbvolumes on the new disks, do I then just extend the db, and then do a del dbvol on the old ones? Does the delete make the data migrate over? Do I have to do a reduce db for any reason before I do the delete dbvol? Can I do the delete with the server up and running? Thanks This E-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended only for the use of the Individual(s) named above. If you are not the intended recipient of this E-mail, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination or copying of this E-mail is strictly prohibited. If you have received this E-mail in error, please immediately notify us at (865) 374-4900 or notify us by E-mail at [EMAIL PROTECTED]
