DanielSparrman
Active Newcomer
- Joined
- Sep 10, 2002
- Messages
- 7
- Reaction score
- 0
- Points
- 0
Hi all
We have a customer who's using Exchange 2010 in a split setup where Client Access Servers are different from mailboxservers.
The customer has several Client Access Servers (front-end) for load-balancing and high-availiability and several back-end mailbox servers (using DAG or Database Availability Groups). Since in Exchange 2010, the clients connect to the CAS servers, which then makes the connection with the mailbox server having the active mailbox, there is no direct client access to the mailbox server.
The customer is now interested in looking at FastBack as a add-on to the normal TDP for Exchange. The reason for this is the single-mailbox, single-mail/calendar entry/contact restore capability of FastBack for Exc. For long-term storage, they will still be relying on the TDP, but for short-term storage, they would like to see FastBack being the primary tool.
Enough about the situation
The issue we've run into is this:
The FastBack client for Exchange not only requires that the client access module(CDO, Collaborative Data Objects) is on the server you're installing the client on, but also that the FastBack client is installed on the server who's holding the actual mailbox databases.
In our scenario, there is nothing open on the back-end mailboxservers to allow incoming connections from say Outlook, only from the front-end CAS servers which use a completely diff connection. The customer is unwilling to actually open up the back-end servers for client connections as this is both a security hazard and also defeats the purpose of actually having the front-end servers.
My question is, is anyone else looking at FastBack for Exchange and have a similiar environment?
Best Regards
Daniel Sparrman
We have a customer who's using Exchange 2010 in a split setup where Client Access Servers are different from mailboxservers.
The customer has several Client Access Servers (front-end) for load-balancing and high-availiability and several back-end mailbox servers (using DAG or Database Availability Groups). Since in Exchange 2010, the clients connect to the CAS servers, which then makes the connection with the mailbox server having the active mailbox, there is no direct client access to the mailbox server.
The customer is now interested in looking at FastBack as a add-on to the normal TDP for Exchange. The reason for this is the single-mailbox, single-mail/calendar entry/contact restore capability of FastBack for Exc. For long-term storage, they will still be relying on the TDP, but for short-term storage, they would like to see FastBack being the primary tool.
Enough about the situation
The issue we've run into is this:
The FastBack client for Exchange not only requires that the client access module(CDO, Collaborative Data Objects) is on the server you're installing the client on, but also that the FastBack client is installed on the server who's holding the actual mailbox databases.
In our scenario, there is nothing open on the back-end mailboxservers to allow incoming connections from say Outlook, only from the front-end CAS servers which use a completely diff connection. The customer is unwilling to actually open up the back-end servers for client connections as this is both a security hazard and also defeats the purpose of actually having the front-end servers.
My question is, is anyone else looking at FastBack for Exchange and have a similiar environment?
Best Regards
Daniel Sparrman
