Best technical solution? That would be to not use VMWARE to host the
servers for starters.
The two versions are binary compatible versions. One has more features than
the other. If you would rather run several versions of standard on separate
servers, then you'll get similar performance than if you ran multiple
storage groups/db's on a single except that your network, cpu, storage and
memory wouldn't be hit as hard on the standard boxes.
700+ mailboxes is really not that many in this day and age. Sub-1000
machines are not as common as they used to be in favor of 1500 and greater
mailbox servers.
The biggest factor affecting your db size (and hence your mailbox sizes etc)
is the amount of restore time it requires. Larger db's take longer to get
on and off tape than do smaller one's in multiple storage groups (which can
be backed up and restored in parallel).
There are plenty of sizing guides. Microsoft has a pretty good one at
http://www.microsoft.com/exchange/library if you're interested. You can
search the net for John's name and see plenty of sizing related to Exchange
especially around disk sizing. He's very good at it and has posted
consistently good information about it.
VMWARE won't be able to scale as well with Exchange and your SAN may or may
not do what you think it will. Be sure to check and to remember that
Exchange is generally cache-unfriendly when it comes to SAN technology.
There are better SAN algorithms now, but you'll want to be sure you're
running SAN technology that takes that into account.
> Hi John,
>
[quoted text clipped - 53 lines]
>>>
>>> Michel
John Fullbright [MVP] - 07 Jul 2006 21:20 GMT
"and your SAN may or may
not do what you think it will. "
In my previous career, prior to IT, the mantra was "In god we trust, all
others we verify"
I guess this mantra carries over to IT: measurement of SAN IO response
times would be a good idea. I've lost count of the number of times
undersized SAN storage did not perform as expected. Again, I would
concentrate on resource bottlenecks.
John
> Best technical solution? That would be to not use VMWARE to host the
> servers for starters.
[quoted text clipped - 83 lines]
>>>>
>>>> Michel