• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Setting up a server as secondary/backup for hosting and mail

AlisonP

New Pleskian
We have two servers; both are running plesk on CentOS 5.
Server sA is new and we have just migrated all the hosting and mail to that one. Server sB is the old one.
We want to be able to use sB as backup for sA incase for whatever reason a problem arises with sA.
I already know that we can have a mail backup using qmail with smptroutes and morercpthosts on server B.

The main issues we are unsure of are:
1. How best to set up DNS so that B hosting is only in use when A is down?
2. The best way to keep data on B is as uptodate as possible and how often should we update it?
3. Is there a way we might be able to keep plesk control panel on B without having to pay for two licenses?

For item 2 I am looking into linux-ha and I think it would be reasonable to update once a day in the early hours of the morning.

Any input would be much appreciated, thanks.
 
Back
Top