i have following questions

1) what is the default mailbox size in exchange 2003, 2007, 2010
2) what is the mailbox database size in exchange 2003, 2007, 2010
3) what configuration needs to be done for mailbox mobility on exchange for active sync

to work from mobile phones

4) if one active  AD site which has exchange database 2010 goes down like in chicago

and there is back up AD site in ohio, how will you bring it outline, name some simple steps
Who is Participating?
Bruno PACIConnect With a Mentor IT ConsultantCommented:

1) There is NO default size for mailboxes. When you create a mailbox it's empty and then it fills when it receives new mails... By default there's no quota on Exchange 2003 so the mailbox can grow without limit. There is NO size limit, just recommended limits.
On Exchange 2003 the recommended limit was 2 GB but a lot of (almost everyone) enterprise uses mailboxes that can have as far as 10 GB on Exchange 2003.
On Exchnage 2007 the recommended size limit is 10 GB, as far as I remember, and it is 25 GB on Exchange 2010.
But again, you can have mailboxes far over these limits.
In fact, the real limit is about the Outlook client, because if you're in cached mode you'll have to maintain a copy of the mailbox on the client !
Since Exchange 2007, there's a quota default of 2GB on mailbox databases, but it is supposed to be modified for your needs.

2) On Exchange 2003 there was an initial database size limit of 16 GB, but Microsoft provided a way to raise this limit to 75 GB per database.
On Exchange 2007 standard edition the database size limit is 50 GB. There is no limit on the Enterprise Edition.
On Exchange 2010, the maximum database size limit is 2TB.

3) The only thing you have to do is publishing the ActiveSync URL to Internet through a reverse proxy. You'll also have to buy a public certificate because all dialogs are done with HTTP protocol.
By default ActiveSync services are already installed and ready on Exchange. You just have to secure the access to it from Internet.

4) Haha !! No way to answer this question here !
It depends of:
 - Exchange version (2003, 2007, 2010)
 - The level of architecture you've installed (standalone server, Cluster, DAG)
 - The level of physical network you've installed (classical separated networks, geo-spanned Load Balancers, ...)

Designing a fault-tolerant Exchange architecture is a complex task that requires to take care of a lot of physical and technical constraints about network, distance, latency, etc...
Each of these design will have its own failover procedure.
It can be fully automatic (datas are permanently replicated and the failover is immediate), semi-automatic (datas are permanently replicated but an administrator has to modify a few parameters to bring the service back online on the backup site), or totally manual (datas have to be restored on the backup site).

Have a good day.
pramod1Author Commented:
it is exchange 2010

Exchange version ( 2010)
 - The level of architecture you've installed (standalone server on both sites)
 - The level of physical network you've installed (Load Balancers, ...)
Bruno PACIIT ConsultantCommented:
Hi again,

So if you already have standalone Exchange 2010 servers on both site and want some level of high availability you can start creating a DAG with these 2 servers.

The requirement is:
Both Exchange servers must be in the same Exchange Organization.
The network bandwith between both sites must be enough to accept database replications.
Network latency between sites must be lower than 500ms.

In a DAG, mailbox servers replicate database of each other so that a database actually exists in several replicas. The database transactions are received by all servers so the data are replicated almost in real time.
When a database fails a replica of this database on another server becomes active.

If you can't create a Load Balancers between both sites because of network limitations the failover will require some administrative actions on database configuration for the client to be directed on the right server (something like changing the RpcClientAccessServer attribute of the database).
If you can create a Load Balancer spanned over both sites then the failover can be totally invisible to clients.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.