Solved Multi Server Setup question.

Daniel_Dog

Verified User
Joined
Nov 16, 2019
Messages
452
Hello eveyone,

I have been using DirectAdmin for a couple of years now. I have always had just one server as I did not see a good reason to spend more money on extra servers.

But in recent times I have become more and more dependent on my DirectAdmin. (Not because of the thing that going around the world but due to the fact that I am an developer and prefure to use DirectAdmin to create a somewhat live / testing envioment.) And as you can guess I can not affort the server being down for any reason. That why I would like to have 2 servers and correct them togather so they act as one.

What mean by that is that I would like for server A and B to be the same and contain the same data. (DNS, Email, Webfiles, ect.) But from the docs I can not figure out if is possible or only for DNS. Since I know this was only possible for DNS in the past.

So if someone knows if is possible please let me know. And any advice is also welcome. ?
 
Multiserver setup - not enough.
Our client solved same issue by:
1. regular creating full da_backup without domains data and without mysql. (or when new domain added)
2. restore it at second server
3. rsync /home from 1 to 2 server
4. mysql replication of all databases
5. using cloudflare for fast proxy change from one IP to another (servers in different countries)
-----
my opinion - its better to move all to KVM VPS and just have fresh snapshot restored on reserved server.
 
2 Servers and IP's for those, then failover DNS ( so one in spare)
You even can have two complete live production servers, and only failover dns for the important custommers, ( so spare users/sites on server where those ip's are not in dns) ( and switch with the failover automaticly)
How you handle Data backup restore or synch then is a choice to made

Load balance hmm. ?

Good offline backups and snapshots , yup, but often you have to setup change all ips in dns after that.
 
Multiserver setup - not enough.
Our client solved same issue by:
1. regular creating full da_backup without domains data and without mysql. (or when new domain added)
2. restore it at second server
3. rsync /home from 1 to 2 server
4. mysql replication of all databases
5. using cloudflare for fast proxy change from one IP to another (servers in different countries)
-----
my opinion - its better to move all to KVM VPS and just have fresh snapshot restored on reserved server.
I already have a VPS for my DirectAdmin but (At least as far as I see it.) it can never hurt to have a fallback that does not include spinning up a new server and restoring a backup. That's why I am asking about multi server and its options + limitations.

2 Servers and IP's for those, then failover DNS ( so one in spare)
You even can have two complete live production servers, and only failover dns for the important custommers, ( so spare users/sites on server where those ip's are not in dns) ( and switch with the failover automaticly)
How you handle Data backup restore or synch then is a choice to made

Load balance hmm. ?

Good offline backups and snapshots , yup, but often you have to setup change all ips in dns after that.
As I said its more meant for redundancy so that if server a goes down I still have server b with the same data. (But with the exception of DNS because of IPs.) And was planning for server a and b to have there own independent DNS/NameServer so that all the domain IPs get to the right server. (Even tho its does not really Mather as they should be completely the same data wise.)
 
Multiserver setup - not enough.
Our client solved same issue by:
1. regular creating full da_backup without domains data and without mysql. (or when new domain added)
2. restore it at second server
3. rsync /home from 1 to 2 server
4. mysql replication of all databases
5. using cloudflare for fast proxy change from one IP to another (servers in different countries)
-----
my opinion - its better to move all to KVM VPS and just have fresh snapshot restored on reserved server.
And thanks for the suggestion.
 
Please read about failover DNS at some or most dns providers you can change the ip also manual if needed to go to other server.

SO domains / server can have "spare" real ip's

You config those with all ip's so is then prepared for fail over.

The (DATA) redudancy you handle then yourself with the second server the way you think is best.

You can so have multi server, and test in your local hosts file ( windows....) the domain on that other ip , if VPS you can have less cpu / mem / then for the "spare" wen needed update with more.

If you do same cpu / mem, with failover dns on extra server it possible to have automic solving problem switch to ...
(One critical drawback to using DNS failover in a situation where back-end synchronization is critical, is when the primary is only down for a very short period of time. The short period would be sufficient to trigger a failover, but insufficient so that existing client connections)

What is DNS Failover?​


DNS Failover keeps sites and web services online in the event of system or network issues. This is done by moving DNS traffic from one IP address to another IP address that you have running at another location.

Failover is most commonly used to move traffic off of an unhealthy web server, and redirect it to a preconfigured backup web server.​

 
Last edited:
What mean by that is that I would like for server A and B to be the same and contain the same data. (DNS, Email, Webfiles, ect.) But from the docs I can not figure out if is possible or only for DNS. Since I know this was only possible for DNS in the past.
DA doesn't support High Availability or clustering. The one CP that currently does is Interworx. Also the foss ISPconfig does as well.
 
Back
Top