Jetstress is only of low usefulness (IMO) if you don't have a targeted I/O 
profile for your users. Be aware that SIR does significantly increase the 
per-user I/O requirements (although compared to E12 and before, they are still 
small).

You need to ensure that if you do decide to do backups, that you stagger your 
backups across the servers and backup only passive copies and watch the 
processor impact of the copy validation during backup.

On a related note, you should stagger your active copies across all servers. 
The mailbox calculator now shows you how to set that up, I recommend using it.

We didn't cover how many active mailboxes per server vs. how many passive 
mailboxes per server, but based on 42 mailbox databases, I'd probably bump the 
memory to 64 GB. That's just a SWAG. The mailbox calculator can help you with 
that too.

So again, I don't see any obvious issues. But operationally, you are going to 
need to take some care.

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com

From: Al Rose [mailto:[email protected]]
Sent: Friday, June 10, 2011 11:00 AM
To: MS-Exchange Admin Issues
Subject: Re: Design 2010 for 5000 mailboxes


On Fri, Jun 10, 2011 at 2:25 PM, Michael B. Smith 
<[email protected]<mailto:[email protected]>> wrote:
Are archive mailboxes going to be on the same mailstore as the primary 
mailboxes?
Yes

Will you be using single item recovery?
Single Item Recovery is enabled and the deleted retention window is configured 
to be 30 days
 Calculation can be taken from there: 
http://blogs.technet.com/b/exchange/archive/2009/09/25/3408389.aspx

Have you planned/projected your IOPS requirements on a per-user basis?
No, we are planning to use stress jet tools in a test environment


How will the SAN disks be presented to the MB servers? FC? iSCSI?

SCSI

If iSCSI, do your NICs/switches/routers all support jumbo frames?

Yes

How many copies of each database in the DAG? This configuration cries out for 4!

4 indeed


What, if any, is the backup requirement?
Not yet decided but Norton comes in the first place as a backup solution


I don't see any inherently bad design choices. As you can see, a number of 
questions immediately appeared in my mind.

Thank you

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com

From: Al Rose [mailto:[email protected]<mailto:[email protected]>]
Sent: Friday, June 10, 2011 8:12 AM
To: MS-Exchange Admin Issues
Subject: Design 2010 for 5000 mailboxes

Dear all,

Just looking for some feedback about real life implementation numbers.

The company i work for is looking at setting-up an Exchange 2010 environment 
for roughly 2000 users and additionnaly around 3000 Functionnal mailboxes, the 
total of mailboxes should soon evolve to 10 000.

Mailbox size limit will be 2GB per user, archive per mailbox 5GB, deleted item 
retention of 30 days.
First deployment for 5000 users will require at least 5000x2x5=50 TB of Data + 
Deleted Items
Each mailbox server wil be presented with 80 TB of available space.

Hardware has already been purchased and will consist of HP Blade Bl460c servers 
with 2 x Hex 2.93 CPUs, mailbox servers will have 48GB of RAM, Public Folders 
12 GB, CAS/HUB servers 24GB.

There will be 2 MBX servers in each site (so 4 in total spread accross 2 sites 
connected with a 10GB redundant link).
There will also be 2x2 CAS/HUB servers (4 servers will participate in a CAS 
array) and 2 Public Folders servers.

Storage design has been made and it is decided to use JBOD (P2000 SCSI SAN 
disks shipped with 2TB SATA disks 7.2K rpm), each server will be presented 
42x2TB SAN disks (no raid) and these disks will be mounted as folders to the 
Operating System.
So 42 folders for 42 databases. Each server will hold 10 active databases and 
30 passive databases.

There will a replication VLAN for DAG, a production VLAN (2 teamed Network 
cards on each server), a Backup VLAN (1 NIC on each server) and an 
administration VLAN.

We have not yet tested this setup but i was hoping in regards to this figures 
if you guys could eventually point out some evident bad design issues if any.

Thank you.

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
[email protected]<mailto:[email protected]>
with the body: unsubscribe exchangelist

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
[email protected]<mailto:[email protected]>
with the body: unsubscribe exchangelist


---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
[email protected]<mailto:[email protected]>
with the body: unsubscribe exchangelist

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to [email protected]
with the body: unsubscribe exchangelist

Reply via email to