cancel
Showing results for 
Search instead for 
Did you mean: 

Multiple exchange servers accross two sites with EV

macomsupport
Level 3

Dear Forum,

we are planning to reconfigure the email infrastructure and I need to answer some questions in relation to the current configuration of our enterprise vault server, currently we have just one domain with one exchange and one enterprise vault server ver 8.2 using SQL std 2000 for the backend. plans are afoot to implement a second exchange server in another regional office at the same time as segregating the Domain into 2 or more child domains. the exchange server will be configured as the live system for the two locations and act as each others fail-over system in the event one of the sites suffered a failure.

Questions

  1. would we need to implement a second vault server in the new regional office or would the users continue to use the Vault on the current server.
  2. is it possible to implement a second enterprise server in the second regional office to act as live of the local users and a fail-over for the other office and vice versa.

how to go-about???

FIA

Steve

      
1 ACCEPTED SOLUTION

Accepted Solutions

JesusWept3
Level 6
Partner Accredited Certified
You could easily target the second exchange server from your original EV server, just depends on what the WAN link is like between the two offices that would determine your throughput Obviously the closer the EV server is to the exchange server, the better, so you could put a new server on the remote office with it's vault stores and indexes local, it would simply just communicate across the network to reach the EV directory databases In that scenario for performance sake you would lose OSIS as sharing large amounts of data between the two servers would not be recommended and if the wan link goes down, then you will cause all sorts of issues for people attempting to get their items or for EV to archive properly You could also use USL as a failover and when one server is down you simply repoint the ServerA alias to point to serverB and then run USL and serverB will take over both servers roles The issue with this is both have to have access to the exact same storage for indexes and vault stores, the data simply couldn't reside on local drives, otherwise the failover server couldn't read or find the data My recommendation would be to target the second server from the one EV server and give everyone vault cache and virtual vault so they can get their items even if the server goes down
https://www.linkedin.com/in/alex-allen-turl-07370146

View solution in original post

1 REPLY 1

JesusWept3
Level 6
Partner Accredited Certified
You could easily target the second exchange server from your original EV server, just depends on what the WAN link is like between the two offices that would determine your throughput Obviously the closer the EV server is to the exchange server, the better, so you could put a new server on the remote office with it's vault stores and indexes local, it would simply just communicate across the network to reach the EV directory databases In that scenario for performance sake you would lose OSIS as sharing large amounts of data between the two servers would not be recommended and if the wan link goes down, then you will cause all sorts of issues for people attempting to get their items or for EV to archive properly You could also use USL as a failover and when one server is down you simply repoint the ServerA alias to point to serverB and then run USL and serverB will take over both servers roles The issue with this is both have to have access to the exact same storage for indexes and vault stores, the data simply couldn't reside on local drives, otherwise the failover server couldn't read or find the data My recommendation would be to target the second server from the one EV server and give everyone vault cache and virtual vault so they can get their items even if the server goes down
https://www.linkedin.com/in/alex-allen-turl-07370146