I currently run spiderloop.com a SEO control panel designed for windows hosting accounts. The site and web service is hosted on our own server and works great, however I am concerned about redundancy and do not want to purchase a whole other server just to be fail safe. So I am going to purchase a shared hosting account to facilitate redundancy.
So here is the question.
How do I do it? How do I set up my current host to redirect to the new host when it goes down?
If the current host has problems how can I force the users browser to redirect to the redundant host? I simply don't understand.
I have been working on and designing a hosting company. Now setting up my names servers has came to a question. When I ran a previous business with a partner he only use Name Servers on 1 Machine in 1 location.
Now my question is my first server is going to be located in New Jersey, USA . So that is where My first set of DNS starts. With my previous partner I noticed most of the customers were based in Europe, Philippines, etc. Over seas. Now What I am asking is Will a VPS in a different location work for DNS Server. That way I can keep a lower budget till we get a few customers under out belt.
I've decided to move from managed hosting to colocated hosting and I'm in a bit over my head as far designing the server configuration goes. I'm looking for assistance with setting up a fully redundant configuration with no SPOF (single point of failure).
The colo provider ensures full redundancy to the cabinet, terminating with two network drops from diverse bandwidth providers and HSRP. I need to eliminate all SPOFs inside the cabinet.
1) I'm thinking of using the Cisco 2960 Series switch as the in-cabinet distribution switch. I believe it supports HSRP. From my understanding, the switch will automatically failover from one uplink to the other in case of a network problem on one of the uplinks, and this will all be transparent to any servers connected to the switch. Is this correct?
2) However, this introduces the switch as SPOF. So, I believe what I need to do is ask the colo for a second pair of network drops and deploy a pair of 2960's. Then I would connect each server to both switches via separate NICs. Is this correct?
3) Finally, assuming I am on the right track here, I would like this to all be transparent and automatic with no human intervention required to recover from a switch failure. The servers will be running RHEL 4. How would I configure the network interfaces on the servers so that they can transparently use either (or both) of the switches? Is there some way to assign the same IP address to more than one interface? How does the OS keep from getting confused about where to send the traffic?
Thanks in advance for any insight. I would also be happy to hear recommendations for excellent network consultants that I could hire to design and implement this configuration for me.
I have two servers. One hosts about 55 small sites and the other does nothing.
Can I make use of the spare one to take over automatically if the main server fails for whatever reason?
I had been thinking of using Rsync to backup accounts / mail every 6 hours or so and then manually changing the nameservers on the domains in the event of server1 failing. Would that even work? Then I got thinking about it all being automatic.
I have a few VPS's, the main one has cPanel/WHM and runs all my sites / email / DNS and MySQL DB's. Heres a little info:
VPS1 - CentOS 4.4, cPanel/WHM, runs all domains (OpenVZ) VPS2 - CentOS 4.4, Webmin, Slave DNS to VPS1 using Webmin cluster (OpenVZ) VPS3 - CentOS 4.4, Webmin, Slave DNS to VPS1 using Webmin cluster (Xen)
However, if VPS1 fails for say 24 hours, im screwed!
So, my question is can I get some kind of redunadancy built in somewhere. For example if someone is trying to access my domain "mydomain.com" and the main VPS is down, then the request for the site would go to VPS2, or VPS3...
The same for the mail server, if some is sending mail to one of the domains on the VPS, and the main VPS was down, the mail would be sent to my other VPS's.
I just don not like the fact there is a single point of failure!
I do have WHM managed Weekly and Monthly backups of all cPanel accounts etc.
We are a hosting company in Colombia, and we want start selling corporate email service.
The main idea is have two servers with redundance, I think this servers have to share the filesystem I don't know if using a scsi disk or just a network file system. We also want to have a good appliance for stop the SPAM, Im not so sure if we need to have redundance on it, its ideal but we are just starting the bussines and we dosn't have cliets yet.
Can anyone share their setup with us, and give us recomendations or tips?
Another option is, if someone know how to do that and have implemented this setup before and want to work $$ with us to implement that, please contact me to jbravo[at]colombiahosting.com.co
to setup a Windows server that can support the failure of the switch that comes before it in the network diagram. The idea would be that if the 15A circuit the switch was on failed, or the switch just died, the server would still be online.
I already have two switches in spanning tree just before the server. Is there a way to assign a single IP to the server on both its network cards and connect each card to a different (spanning tree'd) switch?
I'm upgrading my server again and now that we have 8 disks we need to upgrade our power supply (I was told).
But do I really need a redundant power supply Or can I just buy ONE 650 watt to upgrade?
These are my current server specs:
2 X AMD opteron 270 dual core 2 X 2 GB kingston PC3200 DDR ram 2 X 1 GB kingston PC3200 DDR ram (6 GB total) 8 X seagate cheetah 15k.5 SCSI 73.4 GB, U320, SCA in raid 10 1 X LSI megaraid 320-2x raid controller, dual channel 1 X Tyan thunder 8KSE (s2892) mobo 1 X 2 * 4 port chenbro scsi backplane (8 ports total) 2 X AMD CPU cooler 2 X 40X40X10 fans (Currently 1 X zippy P2G-6510P, 2U, single power supply, 510 Watt) 1 X Sony FDD 1.44" 1 X chenbro RM311, 3U case with 8 hot swap bays 1 X LG DVD/CD-rom burner
I'm in the process to setup a new service with an ISP with the following scenario and need your help.
I've got the rack (42U), servers and switches. Only routers has been left and here is that I need your help.
I have also 2 ports from the ISP where I can connect my routers. I need to get 2 router devices with auto sync feature in order to be able to setup a redundant plan in case that one of them goes down.
Those routers should have firewall features too in order to avoid setup iptables rules for each server. A basic DDoS protection is needed too.
I'm going to push around 100Mbit of traffic across the servers but that will happen after 3-4 months from the initial setup. In the first instance no more than 10-20Mbit will be used.
I heard a lot about Cisco but got no idea what model is the most suitable for my case. I will probably need a module for DDoS attacks and another one for advanced security IOS from what I read but it is not clear to me.
I'm looking to make high availability setup, and wondering how many of you have made it so? we are looking to multi-home the page with a round robin setup, using multiple VPSs/dedicated servers geographically different locations.
Right now i'm still looking at "stale" DNS setup, no automanagement of servers down. Is there a service/software which already offers automatic changes of zones for removing servers which are down, and adding them back when they get back online?
So the rule of thumb is if you have a 30A circuit to not exceed 80% or 24A.
If I buy a 30A circuit, I am assuming it is protected by a circuit breaker that is 30A, correct?
In *theory* we could run 29-30A all day and be fine.
So, I understand, the rule of 80% to be to the effect that "during startup, equipment uses more power ... or during runtime if it heats up, the fans go faster using more power" so it is safe to be at 24A in case you get spikes to 27-29A.
Is my reasoning correct?
Further, if you run primary/redundant circuits, is there really harm in running 13A on one circuit and 14A on the other.. and in the unlikely event of a failure, you are running 27A on one circuit (at 90% instead of 80%).
Any thoughts on this? Getting an extra 3A out of a 208V circuits is like putting in 3-4 more servers. If someone is doing this please let me know. I think it would work fine but i would like to know from the experts that do the colo stuff for a living what problems i could encounter, if any.
We have 2 linux servers with plesk. We want Redundant Dns and backup mail servers for our hosting domains. We already setup Primary nameserver ip address is first server, Sec Nameserver ip address is second Server. like
ns.ourdomain.com - first server ip address ns1.ourdomain.com - Second server IP Address
and how can setup backup mail server for both servers
I have a LAMP server running and would like to have the exact mirror running on another location. I would like to sync the web files and database in either real time (upon any update) or in delayed mode (x minutes after the update).
For MySQL, I believe replication can do the job unless anybody has better recommendation. What would you guys suggest for web files? Can I use different Linux flavor but maintain back the same LAMP version?
Is there any "online" 3rd party load balancing service that I could use to load balance the traffic to both servers?
I have registered a domain using godaddy. I have hosted my site on a server of my shared hosting provider(lets call them X).Currently I have pointed mydomain.com to the server and it is up and running.Sometimes, I have experienced downtimes.
In order to solve this problem, I have hosted a clone of my site on another server from another hosting company(lets call them Y).
1. I want mydomain.com to point to Y when X is down
2. again point it to X when it is up.
My main aim is to have my site live with less downtime. The probability having both servers down is very less.
I dont know if it is technically feasible, just a thought out of dirty mind. I tried to google but was not able to find an answer specific to my problem.
Can anybody tell me how to achieve this through godaddy domain.
Added note, My site is not a commercial site and I cant afford large dedicated servers with clustering and failovers.
do dual power supplies use more power than a single supply?
E.g. Say I have a server than uses two amps, powered by a single power supply. Now if I switch to a dual supply (and say each supply has the same efficiency rating as the single), does my server use more power? How much more?
My simple view of this is that it probably does, but maybe not much. The second power supply consumes some power itself, but since its not under load, it doesn't consume much. Therefore, my server with redundant supplies might use 2.1A or 2.2A.
I'm trying to find at least three web hosting companies to choose from to host a Joomla websites on a shared server. Would consider dedicated if the deal was right. I have a friend of mine who wants to create a church website, and is looking for the best deal. I use Netfirms which I have never had an issue with, but I didn't want to be bias, and would like give him other options to choose from.
Is there a good WebHosting Review site, I could check out, or maybe someone could recommend their top three. I reading threw the forums here and I noticed there are not that many complaints with Hostgator. Again, I just want to see if there was anything out there better.
Lets say you're a customer looking for web hosting, but do have technical experience - you know, you develop your own websites, you've had experience in this sort of thing before.
What if you came across a provider who seemed to offer a good service, they're high quality, they can host your website on their brilliant setup etc... but they do not provide any e-mail accounts with your hosting?
We're developing our own shared hosting setup, our own control panel too. Regardless of the control panel though, we wouldn't feel comfortable hosting peoples e-mail. We have plenty of experience in every other aspect of general shared hosting - but not looking after e-mail accounts nor the associated software.
To be honest I don't think that many shared hosting providers truely handle e-mail properly, and that job should really be left to the professionals.
We could of course guide customers or potential customers on why we won't offer e-mail accounts (i.e. not wanting to offer something we know we can't provide to a high enough standard) and instruct them on how to setup e-mail with another provider (such as Google, who will do this for free with limitations).
The alternative to the above is that we mask in a third party to look after e-mail, i.e. resell someone elses e-mail services as part of our hosting packages. The third party would require API access to setup/remove accounts..
What do you think? Are we just acting stupid trying to provide web hosting without e-mail hosting included? I noticed a while back Dreamhost encouraged their customers to use an alternative e-mail provider!
I have about 5 sites all hosted on my same hosting account. One of those domains is attached to the hosting account. I place my other domains in a folder of a sub-directory of my main domain. This has been working fine, up until today when i noticed a weird error. I give you a little example of how my sites are setup
my main domain: www.maindomain.com
My other sites hosted in a sub-directory of my main domain: www.maindomain.com/sites/site2/ www.maindomain.com/sites/site3/
How my other sites appear on the web: www.site2.com www.site3.com
This works fine for every page until i go to www.site2.com/index.php It redirects to www.maindomain.com/sites/site2/index.php for some reason
This question gets asked a lot in our Helpdesk and I figured I would post our knowledgebase article here to help anyone else wondering the Pros and Cons of Unlimited Domain Shared Hosting vs. Reseller Hosting. If anyone has anything else to add, I appreciate any feedback on how we can improve our KB article.
---------------------------------------------------------------------- Given the present state of shared hosting, many clients may ask "Why would I need a Reseller account if I can host unlimited Addon and Parked domains within a single shared hosting account?". There is certainly enough Disk Space and Bandwidth provided in many of today's hosting packages, so why bother to purchase a Reseller account?
Many don't realize the drawbacks of hosting large numbers of domains within a single hosting account until they've already packed tens of them onto a single package.
So how do you know whether a Reseller account or Shared Hosting account is right for you? The answer is in how you plan to provide access to others and how "mission-critical" the sites are. You should consider the following factors when deciding on hosting a large number of domains:
1. Who will be managing these sites?
2. How important is site security between sites?
3. Will these domains need dedicated SSLs?
4. How resource intensive will these sites be (RAM, CPU, MySQL)?
In a nutshell, Reseller plans are for those who wish to host websites for other sub-clients and a shared hosting package is for a single individual managing multiple personal domains. We'll go over the 4 points above in greater detail.
1. Who will be managing these site?
If you personally own multiple domains and wish to host them within the same hosting space, you can easily do so with an Addon or Parked domain. An addon domain will allow you to host a new domain within a subdirectory of your hosting space. A parked domain will allow you to have multiple domain names point to the same content. Since addon domains reside within the same user space as your main domain, you can manage all of your domains with a single login. You can see the problem if you want to provide another user with access. Since all accounts are managed with a single set of login credentials, if you give another user access to their addon domain you are also giving them access to your main domain. If you have vital information stored on your main domain and you are hosting another domain as an addon domain for someone else, you cannot provide them access to their hosting without compromising the integrity of your main domain.
When hosting sites as a Reseller, your clients in turn will want access to their account and will want exclusive rights to their disk space and server resources. With a Reseller account, each sub-account you create gets its own username, password, and isolated user space on the server. Individual clients of yours have access to their user space and their user space alone. In addition to the isolation with regards to access concerns, each account also gets their own cPanel access. All of the same great features that you use to manage your sites can also be given to your clients. Next time client Y wants to add an email account, you don't have to do it for them for fear of giving them access to your cPanel, you can simply give them their login details and they can manage their own email accounts.
2. How important is site security between sites?
This is along the same lines as point 1. This is not necessarily related to who you are hosting for, but what content you are hosting. Imagine that you are a webmaster and you are hosting your own personal site-in-a-box community forums (such as PHPBB or vBulliten) on your main domain and a company website for a paying client on an addon domain. It is not uncommon for popular scripts to have security flaws in older versions. Script authors will often update security flaws in later versions of their software. For this reason, it is very important to keep scripts up to date on your site. But let's assume you forget to update your scripts for a couple of months and an unscrupulous individual takes advantage of a well known security hole. Using this exploit, they gain access to your forums and any subdirectories. Since you are hosting another domain as an addon, they now have access to this domain's content as well. A site defacement on this company's site may not bode well for you when they are considering you for web master services in the future.
If these two domains had been separate into two individual users (i.e. two subaccounts created through a Reseller), their content would've been inherently isolated server side by Linux's user management. Sure, your forums still would've been affected by the security hole, but the break-in would've been isolated to your site alone.
Going back to our example, let's say that instead of a corporate website as an addon domain you are hosting an image gallery site for all of your cats. In this case, it may not be a big deal if a compromise in your main domain spreads to your addon domain. After all, they are both owned by you and you're only losing some time and effort to restore these sites from your local backups (which I'm sure you've actively maintained ). But then again, you are losing time and time is money. If these sites had been separated into individual users, again, you'd only have to restore one site's content.
The idea here is isolation. Reseller plans provide you with the peace of mind to know that if one of your users doesn't keep up with their site's content as actively as they should, their actions won't negatively impact the content hosted on other domains. If you and those you host in your addons are diligent webmasters, maybe this point won't have much bearing on your decision. Only you can say for sure.
3. Will these domains need SSLs?
As of this writing, SSL certificates must have a dedicated IP address to be installed. If you are hosting multiple domains on the same shared hosting package, you can still install an SSL (or purchase a dedicated IP address and install one) but you are limited to exactly one SSL on your account. If you are hosting multiple domains on the same package (and consequently the same IP), you must choose which domains gets to have the dedicated SSL.
Sub accounts of Resellers can each be placed onto separate IP addresses and, as a result, can each have their own dedicated SSL installed.
Of course, both shared accounts and Resellers' sub accounts can use the server's shared SSL free of charge. However, some clients prefer to see their domain in the URL bar when they visit https.
4. How resource intensive will these sites be (RAM, CPU, MySQL)?
We've already established that disk space and bandwidth will be no problem. But what about CPU, RAM, and MySQL resources?
It's important to be aware of the resource needs of your website. As administrators, we have to make sure all users "play nice" on the server. We can't have user X eating all of the CPU cycles computing pi to the trillionth decimal place while you are trying to serve web pages to your loyal visitors. We have to monitor the actions of all of our users and in the event someone is stepping beyond the bounds of acceptable resource consumption, we have to take action. In most cases, this entails disabling the abusive script, but in extreme cases we have to suspend the abusive user account to prevent other domains from encountering performance degradation on their sites.
If you are hosting 100 domains as addon domains, all serving nothing but static HTML pages, maybe you will stay off the radar.
But considering most sites are more complicated than static HTML, you may want to be aware of how many sites you host as addons and what content they serve. If you're hosting the latest and greatest Joomla modules, with up to date news feeds, integrated forums modules, polls, blog posts, etc your site can certainly require a degree of CPU to serve your pages. Now imagine you have 5 or 10 of these sites all hosted as addon domains. The resources these sites need to generate their content can quickly add up and before you know it you've got a friendly email from Acenet, Inc. in your inbox wondering why your user is consuming 2 of the 8 CPU cores on the server. That may be an exaggeration, but you get the idea. In the event your resource usage becomes so excessive that we have to suspend your user, now all of your sites are down instead of whichever one may be the direct cause of the spike in CPU, RAM, or MySQL consumption.
If each of these had been separate Reseller accounts, the offending account could've been suspended temporarily while we work through the cause, leaving the rest of your domains live and kicking.
The conclusion here is that you need to be aware of the needs of your sites in a general sense. Hosting unlimited domains within a shared hosting space is certainly a nice feature. For those webmasters who have multiple presences on the web, it's very convenient to be able to manage all of their personal domains from a single control panel. For those entrepreneurs who are hosting multiple domains for other individuals, the features and security associated with a Reseller plan and the inherent isolation of Linux users is a must have. ----------------------------------------------------------------------
I'have a problem with my aps setup on sanbox.When i create on customer ccp when i click finish i have this error. I must only test.
Error: Instance of application with id 124 and version '1-4' can not be provided: There is no resource of class 'Shared hosting Apache' with provisioning attributes 'Web Cluster' in subscription with id 1.:There is no resource of class 'Physical hosting (IIS)' with provisioning attributes 'Web Cluster' in subscription with id 1..If i add the shared hosting apache resourse i get this error : There are no "apache" services that satisfy given attributes: "Web Cluster".