ronmarcc
asked on
MS Exchange 2007 High Availability
Hi All,
I am looking to implement a Microsoft Exchange 2007 mail server scenario.
Mail for our client is critical and i would like to have another mail server running at another site which is connected via a managed WAN.
In the event of a server going down we would like to switch over to the other replicating server partner and it can then become the primary reciever of all mail. But i would also like this replicating server to act as a local cache / front end server so that the mail data on the WAN is as minimal as possible.
I was thinking.
CCR with 2007 Exchange
Front End / Back End Scenario with Exchange 2007
Perhaps a secondary MX record?
Has anyone had a lot of experience with this and have any other better ideas. I have tested this scenario previously and it has worked with smaller mailbox servers. This server could potentially have multiple storage groups and 80-100GB of mail.
I am looking to implement a Microsoft Exchange 2007 mail server scenario.
Mail for our client is critical and i would like to have another mail server running at another site which is connected via a managed WAN.
In the event of a server going down we would like to switch over to the other replicating server partner and it can then become the primary reciever of all mail. But i would also like this replicating server to act as a local cache / front end server so that the mail data on the WAN is as minimal as possible.
I was thinking.
CCR with 2007 Exchange
Front End / Back End Scenario with Exchange 2007
Perhaps a secondary MX record?
Has anyone had a lot of experience with this and have any other better ideas. I have tested this scenario previously and it has worked with smaller mailbox servers. This server could potentially have multiple storage groups and 80-100GB of mail.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
If internet fails, for sure you will not receive anything ;)
having two independent internet access is something you can implement, but it depends of your Budget.
having two independent internet access is something you can implement, but it depends of your Budget.
ASKER
Well I guess at the end of the day that is what i wanted the mail going to two different servers on two different internet connections at two different sites to avoid this from happening.
So CCR or SCR could work for either scenario, one is manual and one is automatic.
Secondary to that,
Is the topology still front end / back end.
I would like to have a local cache (so to speak) at some of the larger sites to reduce time to load mailboxes etc.. Is this something that can be implemented like 2003 frontend/backend scenarios?
So CCR or SCR could work for either scenario, one is manual and one is automatic.
Secondary to that,
Is the topology still front end / back end.
I would like to have a local cache (so to speak) at some of the larger sites to reduce time to load mailboxes etc.. Is this something that can be implemented like 2003 frontend/backend scenarios?
how are things going?
ASKER
Apologies, both you guys have answered my question and i am happy with the path i am moving on with.
ASKER
I will most definately be virtualising the datacenter.
But i was just curious on the best approach in the event the datacenter has a total internet failure, so that the other exchange servers will take over and simply re-synchronise when the internet is backup.
The datacenter is virtualised with blades, so its fairly redundant.
We just have no real availability in the event of an internet issues.