Thanks Albert, sorry for not being detail enough. one key point is it will be a brand new AD topology and new physical site(s) which, makes things a little less complex. So it will not depend on any existing infrastrucure.
Here is the scenario: End User - 2000 users scalable to 3000 (majority users are working from home) - 2GB mailbox - Use RPC/HTTPS connection with cache mode - 500 BlackBerry devices - Good user experience in terms of uptime and speed With redundancy and high availability in mind: [Backend / Front End Servers] - Disk subsystems architecture SAN (iSCSI??) - Real-time failover (I am thinking of XOsoft?) - Continuous backup [Network Infrastructure] - Redundant WAN Links - Acceptable speed / bandwidth to support fail-over and users connection experience No need to be very detail as I just wanted to make sure I didn't miss anything that is critical. Point form will be greatly appreciated. Thanks! Chee On Tue, May 20, 2008 at 10:50 AM, Albert Duro <[EMAIL PROTECTED]> wrote: > I'm not qualified to advise on that scale, but I can tell you this much, > that the design of the Exchange topology has to be intimately entwined with > the AD topology. Infact it's really one design. And the versions of OSs, > NOSs, and Exchange is quite critical. > I would suggest that if you want advice from the experts, you provide more > info on those two aspects, and focus your questions on more specific aspects > of the design. > > ----- Original Message ----- From: "Chee Lam" <[EMAIL PROTECTED]> > To: "Exchange Discussions" <[email protected]> > Sent: Tuesday, May 20, 2008 7:11 AM > Subject: Exchange Design Best Practices Questions > > >> Dear List: >> >> Given scenario of 1500 - 2000 users with mailbox size of 2GB each >> spread all over north america. There will be BES in place too. >> How would one design an Exchange environment that covers high >> availability, redundant with failover and good backup strategy? >> Need to pick some ideas from the real world experts :) >> things I am considering: SAN, redundant WAN links, second site with >> third party failover (XO soft?) at least 2-4 servers per site? >> >> Any comments appreciated. >> Thanks. >> Chee >> >> _________________________________________________________________ >> List posting FAQ: http://www.swinc.com/resource/exch_faq.htm >> Web Interface: http://intm-dl.sparklist.com/read/?forum=exchange >> To subscribe: http://e-newsletters.internet.com/discussionlists.html/ >> To unsubscribe send a blank email to >> [EMAIL PROTECTED] >> Exchange List admin: [EMAIL PROTECTED] >> To unsubscribe via postal mail, please contact us at: >> Jupitermedia Corp. >> Attn: Discussion List Management >> 475 Park Avenue South >> New York, NY 10016 >> >> Please include the email address which you have been contacted with. >> > > > _________________________________________________________________ > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > Web Interface: http://intm-dl.sparklist.com/read/?forum=exchange > To subscribe: http://e-newsletters.internet.com/discussionlists.html/ > To unsubscribe send a blank email to > [EMAIL PROTECTED] > Exchange List admin: [EMAIL PROTECTED] > To unsubscribe via postal mail, please contact us at: > Jupitermedia Corp. > Attn: Discussion List Management > 475 Park Avenue South > New York, NY 10016 > > Please include the email address which you have been contacted with. > > _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/read/?forum=exchange To subscribe: http://e-newsletters.internet.com/discussionlists.html/ To unsubscribe send a blank email to [EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with.
