Activity Stream
48,167 MEMBERS
6721 ONLINE
besthostingforums On YouTube Subscribe to our Newsletter besthostingforums On Twitter besthostingforums On Facebook besthostingforums On facebook groups

Page 1 of 2 12 LastLast
Results 1 to 10 of 12
  1.     
    #1
    Member

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

    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...
    torrfriend Reviewed by torrfriend on . Is it possible to Host site in 2 locations...?? 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... Rating: 5

  2.   Sponsored Links

  3.     
    #2
    Too busy :|
    Website's:
    L337Fx.com BeastieBay.net
    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

  4.     
    #3
    It begins...
    Quote Originally Posted by BlaZe View Post
    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
    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).

  5.     
    #4
    Member
    Website's:
    srdelta.com
    Good information Blaze

    here is more about this
    http://technet.microsoft.com/en-us/l...ice.12%29.aspx
    My Tech Blog
    www.SRDelta.Com

  6.     
    #5
    Too busy :|
    Website's:
    L337Fx.com BeastieBay.net
    Quote Originally Posted by BlaZe View Post
    I'm not sure if thats possible as I haven't tried it

    Quote Originally Posted by Lifetalk View Post
    You need to do your research before you begin suggesting stuff to people.

    ============
    Quote Originally Posted by Lifetalk View Post
    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).
    didn't knew about that. I always thought that if NS1 goes down then NS2 is selected and thats why the two nameservers are necessary by default.

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

    We made a similar type of project using Microcontroller for the college :/ assemble level shit :/

  7.     
    #6
    Banned
    Can you link me load balancer ?

  8.     
    #7
    Too busy :|
    Website's:
    L337Fx.com BeastieBay.net

  9.     
    #8
    Member
    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).
    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......??

  10.     
    #9
    Member
    Website's:
    hosthatch.com
    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.

  11.     
    #10
    Too busy :|
    Website's:
    L337Fx.com BeastieBay.net
    Quote Originally Posted by torrfriend View Post
    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......??
    Now, I guess the light of knowledge has been bestowed upon you. It is now your will to continue
    http://*******/xaDPU

Page 1 of 2 12 LastLast

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. [VPS] Handful of vps's in different locations
    By spyro in forum Archive
    Replies: 5
    Last Post: 23rd Apr 2012, 08:26 PM
  2. cPanel Log Locations
    By Bharat in forum Technical and Security Tutorials
    Replies: 1
    Last Post: 28th Dec 2011, 07:12 PM
  3. Replies: 21
    Last Post: 12th Dec 2011, 09:18 AM
  4. DotVPS is looking for new locations
    By dotvps in forum Webmaster Discussion
    Replies: 6
    Last Post: 20th Nov 2011, 11:00 PM
  5. site online and offline on some locations
    By zyberakuma in forum Webmaster Discussion
    Replies: 5
    Last Post: 1st Mar 2011, 04:14 AM

Tags for this Thread

BE SOCIAL