GFI Software

Welcome to the GFI Software community forum! For support please open a ticket from https://support.gfi.com.

Home » OLD forums » Kerio Connect Multi-Server » Removing a Server and Disaster Recovery Best Practice
Removing a Server and Disaster Recovery Best Practice [message #122320] Wed, 24 June 2015 19:15 Go to next message
nate.keegan is currently offline  nate.keegan
Messages: 46
Registered: June 2015
It looks like the Galera bug from 8.5.0 still applies to IM for 8.5.1 pre-release.

Not a big deal but when I go to add a distributed domain I see the attached which introduces some interesting questions.

If one encountered something like this in production what is the best practice for removing a server from Multi-Server?

In a similar vein if a server were to fail, say kerio-backend2 in my screenshot, I'm assuming that all I would need to do would be to clear the Puppet SSL cert, reset DHCP lease for the IP in question, boot up a fresh VMDK, choose the same hostname as the failed server, and then restore backups to that server which would provide both local back-end configuration in this case as well as the actual data on the new server.

Right now it isn't a big deal to reset the test environment to bypass IM until that issue is fixed but doing that in production is obviously a bit more complicated so I figured now is a good time to ask.
  • Attachment: kms-dd.png
    (Size: 14.80KB, Downloaded 755 times)
Re: Removing a Server and Disaster Recovery Best Practice [message #122329 is a reply to message #122320] Wed, 24 June 2015 22:45 Go to previous message
nate.keegan is currently offline  nate.keegan
Messages: 46
Registered: June 2015
Wrong thread, edited

[Updated on: Wed, 24 June 2015 23:20]

Report message to a moderator

Previous Topic: Multi-Server Support for Multiple Directory Servers
Next Topic: Kerio Directory Server Backup
Goto Forum:
  


Current Time: Thu Sep 28 06:43:34 CEST 2023

Total time taken to generate the page: 0.12533 seconds