Web Hosting Talk : Web Hosting Main Forums : Web Hosting : WebSite with redundancy

[Formas]

Hello Guys,

I dont know if all knows about outage in Colo4Dallas few days ago.

After outage, i start to plan to have real redundancy in some og my clients websites.

So I would like to change information here about that. Someone already implement website with real redundancy? Wha strategy was used?

My idea is to have 2 server:

Server 01 with static site (scripts, html, etc...) and MySQL

Server 02 as mirror of static site of server 01, calling MySQL of server 01. If server 01 fail, so I start MySQl on server 2 manually.

The question is: how implement this??? Maybe using 4 DNSs for my domains in my registrar like the following:

1st DNS: ns1.domain.com (server01)
2nd DNS: ns3.domain.com (server02)
3° DNS: ns2.domain.com (server01)
4° DNS: ns4.domain.com (server02)

I am correct?? With DNS configuration above this will worked fine???

Any comments or sugestion about that or reference to articles is welcome.

Thanks

[gate2vn]

Static site will be easy to sync, but sync'ing 2 database servers will be a different story. You have just paid attention to dns only.

Also, if server02 and 01 are in 2 different datacenters, you will see slowness when connecting from 02 to 01.

[Formas]

Idea is take MySQL only in 1 server.

So if Static page is load on server 1 or 2 MySQL ever load on server 1. But if server 1 fail, so I will manually configure MySQl to load on server 2.

The slowness that you are saing is when server 2 connection with server 1 to get MySQL datas, correct?

[Formas]

My great doubh is about static site sync, I will try explain my doubth:

The hypothesis is:

1. I have 2 servers both with the same static site running as said previous;

2. I configure nameservers for my domains in registrar as:

ns1.domain.com point to server 01
ns2.domain.com point to server 02
ns3.domain.com point to server 01
ns4.domain.com point to server 02

Well here the doubts:

1. when both servers running fine, and I type my domains in my browser, where my browser will load the site? Ever In server 01? Or sometimes server 01 and sometimes server 02??? (I think that the reply is server 1, but I am not sure)

2. If server 01 fail, my browser will load the site automatically in server 02?

[KMyers]

Originally Posted by Formas

My great doubh is about static site sync, I will try explain my doubth:

The hypothesis is:

1. I have 2 servers both with the same static site running as said previous;

2. I configure nameservers for my domains in registrar as:

ns1.domain.com point to server 01
ns2.domain.com point to server 02
ns3.domain.com point to server 01
ns4.domain.com point to server 02

Well here the doubts:

1. when both servers running fine, and I type my domains in my browser, where my browser will load the site? Ever In server 01? Or sometimes server 01 and sometimes server 02??? (I think that the reply is server 1, but I am not sure)

2. If server 01 fail, my browser will load the site automatically in server 02?

Hello,
Setting these nameservers are not going to make a difference, you will actually need to look for a "Failover DNS" or a "Failover Load Balancer"

[Formas]

Originally Posted by KDisk

Hello,
Setting these nameservers are not going to make a difference, you will actually need to look for a "Failover DNS" or a "Failover Load Balancer"

Nice information Kdisk,

I did a quick read about 2 options. Seems that "Failover Load Balancer" is a solutions to be used with 2 servers in the same data center, that is not the case. Maybe "Failover DNS" can to be the best option.

I will try learn more about that.

Thansk

[layer0]

Nameservers are not meant to function in the way you described above. That would be an invalid DNS configuration.

Instead, you should use a company like www.dnsmadeeasy.com to manage your DNS and your A records configured to failover between servers.

[barbus]

You can sync static files between both server. MySQL can be replicated in master-slave mode. If master fails, you will have to switch slave to master mode and domains in DNS to point to the slave.