Re: Opinion on disk layout for db, log & storagepools
Do you know what your workload is going to be? For database sizing, you need to know how many files total you will retain. For storage pool sizing, you need to know your average and peak daily backup rates in bytes. For recovery log sizing, you need to know how many files you will backup in a single backup session. On 09/27/2010 08:20 AM, Moyer, Joni M wrote: > Hi Everyone, > > I am in the process of acquiring new disk which means that I will be able to > layout the storage for the database, log and storage pools in a more > efficient manner. I was told by IBM that a filesystem should contain no more > than 2-3 volumes and there should be a 1 to 1 ratio of physical disk volumes > to TSM volumes. > > I was thinking about doing the following but I was wondering if there is a > known limit to the size of a volume that should be used for the database or > storage pools? And should I have more storagepool volumes created per > storagepool? > > Any suggestions/opinions are greatly appreciated > > 3 filesystems that are 50 GB each with 1 physical 50 GB LUN with 2 TSM > database volume per filesystem: > > Filesystem VolumeSize (GB) > /tsmdev/db1 dbvol1 25 > dbvol2 25 > /tsmdev/db2 dbvol3 25 > dbvol4 25 > /tsmdev/db3 dbvol5 25 > dbvol6 25 > > For my log volumes I'm just going to create 1 filesystem with 1- 15 GB lun > and then create 3- 4 GB log volumes from it: > > Filesystem Volume Size (GB) > /tsmdev/logfs logvol1 4 > logvol2 4 > logvol3 4 > > Storage pools: > > Filesystem Volume > Size (GB) > /tsmdev/stgpool1 vol150 > Represents AIX storagepool > Vol2 50 > Represents Sharepoint storagepool > /tsmdev/stgpool2 vol3250 > Represents vol1 of Linux storagepool > Vol4 > 250 Represents vol2 of Linux storagepool > /tsmdev/stgpool3 vol5250 > Represents vol1 of Oracle storagepool > Vol6 > 250 Represents vol2 of Oracle storagepool > /tsmdev/stgpool4 vol7125 > Represents Lotus Notes storagepool > Vol8 > 125 Represents Solaris storagepool > /tsmdev/stgpool5 vol9200 > Represents vol1 of Windows storagepool > Vol10 200 > Represents vol2 of Windows storagepool > Vol11 200 > Represents vol3 of Windows storagepool > > > > This e-mail and any attachments to it are confidential and are intended > solely for use of the individual or entity to whom they are addressed. If you > have received this e-mail in error, please notify the sender immediately and > then delete it. If you are not the intended recipient, you must not keep, > use, disclose, copy or distribute this e-mail without the author's prior > permission. The views expressed in this e-mail message do not necessarily > represent the views of Highmark Inc., its subsidiaries, or affiliates. -- -- Skylar Thompson (skyl...@u.washington.edu) -- Genome Sciences Department, System Administrator -- Foege Building S048, (206)-685-7354 -- University of Washington School of Medicine
Re: Opinion on disk layout for db, log & storagepools
You didn't say whether this was for a v5 or a v6 server. It makes a difference. On the v6 side, I think that IBM has recently been refining their recommendations. ..Paul At 11:20 AM 9/27/2010, Moyer, Joni M wrote: >Hi Everyone, > >I am in the process of acquiring new disk which means that I will be able to >layout the storage for the database, log and storage pools in a more efficient >manner. I was told by IBM that a filesystem should contain no more than 2-3 >volumes and there should be a 1 to 1 ratio of physical disk volumes to TSM >volumes. > >I was thinking about doing the following but I was wondering if there is a >known limit to the size of a volume that should be used for the database or >storage pools? And should I have more storagepool volumes created per >storagepool? > >Any suggestions/opinions are greatly appreciated > >3 filesystems that are 50 GB each with 1 physical 50 GB LUN with 2 TSM >database volume per filesystem: > >Filesystem VolumeSize (GB) >/tsmdev/db1 dbvol1 25 > dbvol2 25 >/tsmdev/db2 dbvol3 25 > dbvol4 25 >/tsmdev/db3 dbvol5 25 > dbvol6 25 > >For my log volumes I'm just going to create 1 filesystem with 1- 15 GB lun and >then create 3- 4 GB log volumes from it: > >Filesystem Volume Size (GB) >/tsmdev/logfs logvol1 4 > logvol2 4 > logvol3 4 > >Storage pools: > >Filesystem VolumeSize >(GB) >/tsmdev/stgpool1 vol150 > Represents AIX storagepool >Vol2 50 > Represents Sharepoint storagepool >/tsmdev/stgpool2 vol3250 >Represents vol1 of Linux storagepool >Vol4 250 > Represents vol2 of Linux storagepool >/tsmdev/stgpool3 vol5250 >Represents vol1 of Oracle storagepool >Vol6 250 > Represents vol2 of Oracle storagepool >/tsmdev/stgpool4 vol7125 >Represents Lotus Notes storagepool >Vol8 125 > Represents Solaris storagepool >/tsmdev/stgpool5 vol9200 >Represents vol1 of Windows storagepool >Vol10 200 >Represents vol2 of Windows storagepool >Vol11 200 >Represents vol3 of Windows storagepool > > > >This e-mail and any attachments to it are confidential and are intended solely >for use of the individual or entity to whom they are addressed. If you have >received this e-mail in error, please notify the sender immediately and then >delete it. If you are not the intended recipient, you must not keep, use, >disclose, copy or distribute this e-mail without the author's prior >permission. The views expressed in this e-mail message do not necessarily >represent the views of Highmark Inc., its subsidiaries, or affiliates. -- Paul ZarnowskiPh: 607-255-4757 Manager, Storage Services Fx: 607-255-8521 719 Rhodes Hall, Ithaca, NY 14853-3801Em: p...@cornell.edu
Re: Opinion on disk layout for db, log & storagepools
I would principally follow IBM's recommendations as put forth in the TSM Performance Tuning Guide. You seem to be running AIX, where putting volumes into a file system is the inferior approach to raw logical volumes (which I use, and have found satisfying). Richard Sims
Opinion on disk layout for db, log & storagepools
Hi Everyone, I am in the process of acquiring new disk which means that I will be able to layout the storage for the database, log and storage pools in a more efficient manner. I was told by IBM that a filesystem should contain no more than 2-3 volumes and there should be a 1 to 1 ratio of physical disk volumes to TSM volumes. I was thinking about doing the following but I was wondering if there is a known limit to the size of a volume that should be used for the database or storage pools? And should I have more storagepool volumes created per storagepool? Any suggestions/opinions are greatly appreciated 3 filesystems that are 50 GB each with 1 physical 50 GB LUN with 2 TSM database volume per filesystem: Filesystem VolumeSize (GB) /tsmdev/db1 dbvol1 25 dbvol2 25 /tsmdev/db2 dbvol3 25 dbvol4 25 /tsmdev/db3 dbvol5 25 dbvol6 25 For my log volumes I'm just going to create 1 filesystem with 1- 15 GB lun and then create 3- 4 GB log volumes from it: Filesystem Volume Size (GB) /tsmdev/logfs logvol1 4 logvol2 4 logvol3 4 Storage pools: Filesystem VolumeSize (GB) /tsmdev/stgpool1 vol150 Represents AIX storagepool Vol2 50 Represents Sharepoint storagepool /tsmdev/stgpool2 vol3250 Represents vol1 of Linux storagepool Vol4 250 Represents vol2 of Linux storagepool /tsmdev/stgpool3 vol5250 Represents vol1 of Oracle storagepool Vol6 250 Represents vol2 of Oracle storagepool /tsmdev/stgpool4 vol7125 Represents Lotus Notes storagepool Vol8 125 Represents Solaris storagepool /tsmdev/stgpool5 vol9200 Represents vol1 of Windows storagepool Vol10 200 Represents vol2 of Windows storagepool Vol11 200 Represents vol3 of Windows storagepool This e-mail and any attachments to it are confidential and are intended solely for use of the individual or entity to whom they are addressed. If you have received this e-mail in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not keep, use, disclose, copy or distribute this e-mail without the author's prior permission. The views expressed in this e-mail message do not necessarily represent the views of Highmark Inc., its subsidiaries, or affiliates.
