Re: How many 'disks' should a 1.7TB guest lpar have?

I think the magic number was more the number of storage spaces versus the
size of the storage spaces.
Originally I didn't think the 'arms' mattered on storage spaces since they
were always scattered over the plethora of physical drives we have.
However I've been corrected. The 'arms' are called something else and
having a number of them helps.
It's also been recommended to me that I pick some size that resembles a
physical size available.
And, there's been some debate on whether I should be happy with 35GB or
pick something higher for fear of 35GB load source drives being forbidden
in the near future (no concrete source on that).
Eight 280 GB drives or fifteen 140GB drives is looking promising.

Here's another question. Is there some performance advantage to carving
these all out at the beginning versus adding them as needed? Why? Because
I am moving data off of the host to this guest. If I carve them all out
at once it leaves the host with less than 3% free. That's cutting a bit
close for my tastes. I could easily move parts at a time.
I know with HDD's or SSD's if you are putting them in a raid set the
stripe can be spread across more drives if you add more at the beginning
than doing the minimum and expensing one drive a month to the raid set.

As it is, I'll be temporarily so tight I have have to go from host to tape
to guest when moving objects. As fast as our tape drives are I'm not sure
that would be any slower than host to save file transmitted to guest then
restored from save file. And might even be faster.


Rob Berendt