Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 7 replies
  • Subscribers 1 subscriber
  • Views 20362 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Enterprise Console and Relay, High Availibilty

CRIPete

Hi

We currently have a management server, with relay server for external clients. However we are building a second data centre and need to work out the best way managing sophos if the first site gets taken offline.

It looks like the only solution is to virtualize the servers and replicate them to the second site. The questions are:-

  1. Is this really the best way of managing this 
  2. Are we going to run into problems in the second site when we bring up the servers. As the IP addresses on the new site will be different are we going to have issues with communication between the clients relay and management server. 

Thanks

:50116


This thread was automatically locked due to age.
Parents
  • 0

    Hello Pete,

    well, you have to take my word for it - about five years ago we (not really me, I was on paternal leave)  "lost" (don't ask me for details) the management server  Admins tried to restore it but in the end it didn't work out. I did have a backup of the really important stuff (viz. the certificate keys) and built a new server - as they were still trying to get the old one running with a different name and IP. We have no administrative rights over most endpoints (this is a university) so a reprotect (or even a reinit) is impossible. So we just made the old FQDN an alias for the new server and endpoints started to appear.

    As an aside, we kept the alias in place and even four years later two "new" endpoints with a policy pointing to the old server appeared - dunno where they had spent the years in between :smileyvery-happy:

    Christian

    :50334
Reply
  • 0

    Hello Pete,

    well, you have to take my word for it - about five years ago we (not really me, I was on paternal leave)  "lost" (don't ask me for details) the management server  Admins tried to restore it but in the end it didn't work out. I did have a backup of the really important stuff (viz. the certificate keys) and built a new server - as they were still trying to get the old one running with a different name and IP. We have no administrative rights over most endpoints (this is a university) so a reprotect (or even a reinit) is impossible. So we just made the old FQDN an alias for the new server and endpoints started to appear.

    As an aside, we kept the alias in place and even four years later two "new" endpoints with a policy pointing to the old server appeared - dunno where they had spent the years in between :smileyvery-happy:

    Christian

    :50334
Children
No Data
Unfiltered HTML