Recommendations for Storage Pool sizes

18 Nov 2014

      ...
<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Century =
Gothic","sans-serif"'><o:p> </o:p></span></p><p class=3DMsoNormal><spa=
n style=3D'font-size:10.0pt;font-family:"Century Gothic","sans-serif"'>For =
example, right now I have a 3TB domain made up of 3 1TB luns.  That do=
--_000_61A8344D117D814CA4DA393472F38CF4019BEC6D4ACD1001M360cor_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I've been looking around for any best practices/recommendations on how larg=
e a storage domain can be but can't seem to find anything.

For example, right now I have a 3TB domain made up of 3 1TB luns.  That dom=
ain has about 200 thin disks created from it.

When I want to add more space, is there any reason I should not simply incr=
ease the existing pool?  Or is it better to create a new pool?

Thanks,
Ryan

--_000_61A8344D117D814CA4DA393472F38CF4019BEC6D4ACD1001M360cor_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:m=3D"http://sc=
hemas.microsoft.com/office/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-=
html40"><head><META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; chars=
et=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 (filtere=
d medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Century Gothic";
	panose-1:2 11 5 2 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Century Gothic","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-CA link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:10.0pt;font-family:"Century Gothic","sans-serif"'>I’ve been =
looking around for any best practices/recommendations on how large a storag=
e domain can be but can’t seem to find anything.<o:p></o:p></span></p=
main has about 200 thin disks created from it.<o:p></o:p></span></p><p clas=
s=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Century Gothic",=
"sans-serif"'><o:p> </o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:10.0pt;font-family:"Century Gothic","sans-serif"'>When I want=
 to add more space, is there any reason I should not simply increase the ex=
isting pool?  Or is it better to create a new pool?<o:p></o:p></span><=
/p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Centur=
y Gothic","sans-serif"'><o:p> </o:p></span></p><p class=3DMsoNormal><s=
pan style=3D'font-size:10.0pt;font-family:"Century Gothic","sans-serif"'>Th=
anks,<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10=
.0pt;font-family:"Century Gothic","sans-serif"'>Ryan<o:p></o:p></span></p><=
p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Century Go=
thic","sans-serif"'><o:p> </o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Century Gothic","sans-serif"'><o:p>&=
nbsp;</o:p></span></p></div></body></html>=

--_000_61A8344D117D814CA4DA393472F38CF4019BEC6D4ACD1001M360cor_--

Groten, Ryan

tags

participants (1)