Latest Announcemnent
New thread

Is it possible to Host site in 2 locations...??

Status
Not open for further replies.
T

toRRfriend

Active Member
1,559
2010
309
50
Guys,
100% uptime is not possible in most host, so is it possible to host site in 2 location(eg: in NL and Asia)

if one will down means, users will redirect/load from other, so they don't feel any downtime...

if possible means, load sharing between those 2 server is possible....???, like CDN,
that is visitors from Europe, USA are route to NL server and Asian and other users to Asia server...
 
Last edited:
11 comments
You can have it like this

Have a remote SQL server in some redundant US datacenter (like Softlayer) where your site's DB is located.

Then the php/html files can be uploaded to multiple servers. Include the multiple nameservers in your domain registrar's panel like

NS1.DOMAIN.COM & NS2.DOMAIN.COM => points to your 1st server
NS3.DOMAIN.COM & NS4.DOMAIN.COM => points to your 2nd server
NS5.DOMAIN.COM & NS6.DOMAIN.COM => points to your 3rd server

So if NS1 & NS2 are down, then NS3 & NS4 will be automatically used by the user trying to connect to your site.
Similarly if NS1,2,3,4 are down the NS5 & 6 will be active.

So now you have a redundant site. But the only problem is, if you allow the user to upload some files to the server (like attachments, profile avatars, etc.) then that may cause an issue.

I'm not sure if thats possible as I haven't tried it xD
 
BlaZe said:
You can have it like this

Have a remote SQL server in some redundant US datacenter (like Softlayer) where your site's DB is located.

Then the php/html files can be uploaded to multiple servers. Include the multiple nameservers in your domain registrar's panel like

NS1.DOMAIN.COM & NS2.DOMAIN.COM => points to your 1st server
NS3.DOMAIN.COM & NS4.DOMAIN.COM => points to your 2nd server
NS5.DOMAIN.COM & NS6.DOMAIN.COM => points to your 3rd server

So if NS1 & NS2 are down, then NS3 & NS4 will be automatically used by the user trying to connect to your site.
Similarly if NS1,2,3,4 are down the NS5 & 6 will be active.

So now you have a redundant site. But the only problem is, if you allow the user to upload some files to the server (like attachments, profile avatars, etc.) then that may cause an issue.

I'm not sure if thats possible as I haven't tried it xD
Click to expand...

You need to do your research before you begin suggesting stuff to people.

Blaze is correct about a remote SQL server in a DC that has guaranteed uptime. But he's wrong about the Nameservers.

If you have something like this:
NS1/2 -> Server1
NS3/4 -> Server2

Your users will NOT be automatically redirected to the NS that is up. When you have multiple nameservers, they are used RANDOMLY! If the server on NS1/2 is down, your users will NOT be redirected to NS3/4; they will still be taken to your Server1; zero redundancy.

This is exactly why remote DNS hosting services exist. And what you want, is typically done by a load balancer. A load balancer is an application layer on a redundant hardware (that has guaranteed uptime). It balances load by splitting requests amongst X no. of backend servers. If it detects that X server is unreachable, it will not redirect any requests to it, but instead use server Y and Z.

Remote DNS works in the same way. Their infrastructure is generally hosted on 100% uptime networks; and you can specify multiple zones within their infrastructure. If their system detects that a particular zone is unresponsive, it automatically redirects all requests to the secondary zone (or alerts you, if no secondary zone exists).
 
BlaZe said:
I'm not sure if thats possible as I haven't tried it xD
Click to expand...


Lifetalk said:
You need to do your research before you begin suggesting stuff to people.
Click to expand...

:|
============
Lifetalk said:
Blaze is correct about a remote SQL server in a DC that has guaranteed uptime. But he's wrong about the Nameservers.

If you have something like this:
NS1/2 -> Server1
NS3/4 -> Server2

Your users will NOT be automatically redirected to the NS that is up. When you have multiple nameservers, they are used RANDOMLY! If the server on NS1/2 is down, your users will NOT be redirected to NS3/4; they will still be taken to your Server1; zero redundancy.

This is exactly why remote DNS hosting services exist. And what you want, is typically done by a load balancer. A load balancer is an application layer on a redundant hardware (that has guaranteed uptime). It balances load by splitting requests amongst X no. of backend servers. If it detects that X server is unreachable, it will not redirect any requests to it, but instead use server Y and Z.

Remote DNS works in the same way. Their infrastructure is generally hosted on 100% uptime networks; and you can specify multiple zones within their infrastructure. If their system detects that a particular zone is unresponsive, it automatically redirects all requests to the secondary zone (or alerts you, if no secondary zone exists).
Click to expand...

:o didn't knew about that. I always thought that if NS1 goes down then NS2 is selected xD and thats why the two nameservers are necessary by default.

Redundant system :D I read about it few months ago but I haven't gone deep into it :p

We made a similar type of project using Microcontroller for the college :/ assemble level shit :/
 
Originally Posted by Lifetalk
Blaze is correct about a remote SQL server in a DC that has guaranteed uptime. But he's wrong about the Nameservers.

If you have something like this:
NS1/2 -> Server1
NS3/4 -> Server2

Your users will NOT be automatically redirected to the NS that is up. When you have multiple nameservers, they are used RANDOMLY! If the server on NS1/2 is down, your users will NOT be redirected to NS3/4; they will still be taken to your Server1; zero redundancy.

This is exactly why remote DNS hosting services exist. And what you want, is typically done by a load balancer. A load balancer is an application layer on a redundant hardware (that has guaranteed uptime). It balances load by splitting requests amongst X no. of backend servers. If it detects that X server is unreachable, it will not redirect any requests to it, but instead use server Y and Z.

Remote DNS works in the same way. Their infrastructure is generally hosted on 100% uptime networks; and you can specify multiple zones within their infrastructure. If their system detects that a particular zone is unresponsive, it automatically redirects all requests to the secondary zone (or alerts you, if no secondary zone exists).
Click to expand...

so database is the matter,
we need to place all other things in two servers.

So how to setup remote sql server, i don't need to add nameservers for that...?? or any simple steps, because i not tried that things...

how the script know, Db is in remote..?? any change in cms, wordpress......??
 
You can also go with load balancing/fail over DNS at dnsmadeeasy.com - I've used it, had 4 different locations and everything worked just fine. I would recommend it to you. You can host the DB on a good cloud.
 
torrfriend said:
so database is the matter,
we need to place all other things in two servers.

So how to setup remote sql server, i don't need to add nameservers for that...?? or any simple steps, because i not tried that things...

how the script know, Db is in remote..?? any change in cms, wordpress......??
Click to expand...

Now, I guess the light of knowledge has been bestowed upon you. It is now your will to continue
http://goo.gl/xaDPU
 
torrfriend said:
so database is the matter,
we need to place all other things in two servers.

So how to setup remote sql server, i don't need to add nameservers for that...?? or any simple steps, because i not tried that things...

how the script know, Db is in remote..?? any change in cms, wordpress......??
Click to expand...

A remote database is easy. Host your database on a cloud, as suggested, then connect to the IP from the other application servers. Put in security measures, including specifying which users can be connected to remotely, and IP address restrictions.

That said, go ahead and Google. By the looks of it, you're new to all of this. It will take a while to get the hang of things and figure out how they work, that's only natural. Google around, you'll find a ton of information on exactly what you're looking for.
 
Status
Not open for further replies.
Back
Top