Do you host your main site elsewhere?

S

SimplyShared

New member
Do you host your main website on other companies servers? From what I can tell it's not a bad idea incase your own servers go down and you can't be contacted. We've still got alternate means (e.g: Twitter, which we heavily advertise in our emails) however it's nice being able to use the main website.

Do you? And if so, who are you with- (we're about to go with HostRelic due to their low storage, low price & 99.989 uptime report last year)
 
I hope the best way is to host your own website, many customers do a traceroute to see the incoming providers to your network.

---> From what I can tell it's not a bad idea incase your own servers go down and you can't be contacted.

Think about redundancy in case of your server crashed.
You can also install from outside of the newtork where your website is a monitoring system like nagios that will send you alert if your server/website crashed.
 
Yeah, it was mainly in case the website goes down- that was they/we can still get in contact should anything *hope it never happens* goes wrong.
 
Never host your company's website on the same server you host your clients, always keep them separate. Where you host it really doesn't matter as long as it's a reliable and stable provider. This could be your own company or another company. :)
 
I suppose you can host your own site on a remote VPS too. It's definitely not a bad idea to host support.yourdomain.com remotely, so that communicating with the customers while a major incident takes place will not be a a problem.
 
ldcdc said:
I suppose you can host your own site on a remote VPS too. It's definitely not a bad idea to host support.yourdomain.com remotely, so that communicating with the customers while a major incident takes place will not be a a problem.
Click to expand...

Really good idea that! Most of it is done via email as opposed to ClientExec's support system (I don't feel it's quite there yet- thus why I'm looking forwards to CE 4.1)

Thanks though!
 
ldcdc said:
I suppose you can host your own site on a remote VPS too. It's definitely not a bad idea to host support.yourdomain.com remotely, so that communicating with the customers while a major incident takes place will not be a a problem.
Click to expand...

That's also an excellent setup :thumbup:. So you could have something like:

yourcompany.com = Server1

support.yourcompany.com = Server2

yourcustomers = Server3

and so on. :)
 
If you are so concerned about website availability and don't want to face any downtime, then I think you should also consider load balanced dedicated servers. Means, if one server is out of service, then the whole system will still work. The load balancer will recognize the failed node, and mark the crashed system. The total performance of the load balancing cluster will be reduced, but services will still be provided.

Normally it is called as a server mirroring & it's a process of channeling data from the Master server to the Slave server so that an identical copy of data exists on the Slave server. In other words server mirroring can also be described as utilizing a backup server that duplicates all the data of the master server. After the implementation of mirroring, if for any reason, the master server fails, the slave server can immediately take its place without any downtime.
 
A load balanced situation like Paul suggested is great, but keep in mind that the site should be located in different physical datacenters and ideally, different networks.

Also, you should have a backup in place should your DNS severs go offline. This will allow you to re-route your site through an alternate machine.

For us, our site is within our network, but we have two duplicate sites located elsewhere (one in England). If the datacenter has issues, we can quickly modify the DNS on the domain name and point to the other location.

For ultimate protection, using a LIVE DNS system where you can change the DNS within a few seconds and use a Round-Robin sitution, this would provide the ultimate protection.

We use 5 servers to host our site currently - each one dedicated to a single task of our system. One for site, one for support, one for billing, another for blog etc. Keeping these separate from client sites is also strongly recommended.
 
handsonhosting said:
A load balanced situation like Paul suggested is great, but keep in mind that the site should be located in different physical datacenters and ideally, different networks.

Also, you should have a backup in place should your DNS severs go offline. This will allow you to re-route your site through an alternate machine.

For us, our site is within our network, but we have two duplicate sites located elsewhere (one in England). If the datacenter has issues, we can quickly modify the DNS on the domain name and point to the other location.

For ultimate protection, using a LIVE DNS system where you can change the DNS within a few seconds and use a Round-Robin sitution, this would provide the ultimate protection.

We use 5 servers to host our site currently - each one dedicated to a single task of our system. One for site, one for support, one for billing, another for blog etc. Keeping these separate from client sites is also strongly recommended.
Click to expand...

Nice setup Conor!.. And very nice tips as well. :) Talk about redundancy! :thumbup:
 
I host all my sites to hosting providers ( micfo and knowhost ). It is cheaper this way rather then learning / employing someone to look after my own server.
 
We've now migrated our main site to RelicHost due to a good friend's personal tracker showing almost 100% uptime (exactly what I wanted!)

Thanks for your help
 
I suppose that Conor is a bit suspicious of such perfect uptime, as I am too. I guess it depend a bit on the precision of the monitoring tool as well. If the checks are done every 30 minutes, some short downtime occurrences can easily be missed.
 
ldcdc said:
I suppose that Conor is a bit suspicious of such perfect uptime, as I am too. I guess it depend a bit on the precision of the monitoring tool as well. If the checks are done every 30 minutes, some short downtime occurrences can easily be missed.
Click to expand...

Valid point- I'm not trying to advertise for them, just stating that I went with them due to a good recommendation.
 
We host our main site internally, but do host our mail servers externally and have a backup copy of our customer database in our office that is updated nightly, so we always have an out of datacenter copy of contact. In any outage we establish the first communication with our customers. But great tips on how to keep things up when the worst happens!
 
Well what we do is that we have a couple of site mirrors on a few servers that we have and we use DNS MADE EASY for our DNS needs plus their monitoring service which automatically switches your DNS once it detects your website is down.

Their monitoring is made every 1-2 minutes. So sometimes when I restart my server, its just kind funny where you will see them switch to my backup server for about 2 minutes then back to my main site when my server reboots.

But then again, that's what I usually do for my main site. That keeps it from going down. Plus, the 2 servers which they are on are on totally different continents and different DC's. So going down both at once is kinda impossible.
 
We tend to place our main site off from the main server, there has been times of interruptions and we have been lucky enought to of been able to support clients with an active and open website.

We tend to keep our main site off from the server just in the event something occurs.
 
Personally I have a backup support site using the .net version of my .com.

The backup support site is hosted on a business grade account in a different country/continent from the main servers.
 
You must log in or register to reply here.

Latest posts

Forum supporters

Members recently online

Total: 20

Forum statistics

Threads
81,045
Messages
248,671
Members
20,690
Latest member
JohnMuller
Top