I currently own several servers: let's say sites on 3 of those servers rely on a website that sits on server 4
If server 4 goes offline, then servers 1 2 and 3 suffer a lack of usability.
The website on server 4 is very small and fast, but receives several hundred thousand visits a day
I figured it would be a good idea to replicate that website on each of my servers, but I'm unsure about how to set up a good redundancy system..
Using several nameservers doesn't work as expected (visitors are randomly sent to one of the nameservers, in no particular order)
I want to setup a failover approach in which if after a particular timeout say 10secs the load shifts to some other website like Refer.com | The world. The timeout should be in Proxy Pass and if timeout occurs it shifts to Refer.com | The world
I have to create a structure in which there is a client, a server and an authentication authority.
The authentication authority verifies the identity of both the client and server before they can communicate, so that the client can access the content offered by the server. Everything must be made using HTTP with SSL (HTTPS).
For now I have installed xampp on my pc with ubuntu, I performed the initial configuration and was able to view a test page locally hosted by entering the URL of the virtual server "www.server.it" (added to the configuration of apache2).
Recently I cross compiled Apache2.4.6 to run in my ARM cpu, and I found that http can work well if only it's own port such as 80 is listened, but if add one more port to be listened in conf file, http fails. That means http is good, but after https is on, http stop working and https is good. At the same time, I built the same apache2.4.6 in X86 gcc4.6.1, http and https can both work well. In addition, I also tried apache1.3.33 in the same ARM system, http and https can work well too. It seems like that in apache2.4.6, http can't work well if there is one more port listened in ARM system. Actually http port is listening and is established when using netstat to monitor it.
root@freescale /usr/local/apache/bin$ netstat -a Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 :::www :::* LISTEN tcp 0 0 :::443 :::* LISTEN tcp 0 0 (null):www (null):3705 ESTABLISHED tcp 0 0 (null):443 (null):3720 ESTABLISHED
then i get the error below. Can anyone help me out? i really dont know what todo here.
Checking Update System........Your operating system's rpm update method (yum) was not able to locate the glibc package. This is an indication of an improper set up. You must correct this error before you can proceed.
I have a website on a linux-server working fine with PHP/Apache. The page loads a lot of css/js/image-stuff (total 84 requests, 220k), it takes about 4 secs to load via internet.
Now I'm testing the same page locally on a Win7-64-system (Apache 2.2, PHP 5.4). The system is not very slow (8 GB RAM, SSD, i7-CPU), but loading the same page as above takes about 50 secs.
The Q is: What might be the problem?
- I turned off firewall and anti-virus.
- I used mod_status: 150 threads, max. 11 seems to be used during the loading of the page.
- I tried php5apache2_2.dll with TS-PHP 5.4 and mod_fcgid.so with NTS-PHP 5.4, but the loading-time kept almost the same.
Looking at the "network-tab" in FF or Chrome, I found that a lot of subqueries get a timing like this:
Blocking: 11.96 s Sending: 0 Waiting: 1 ms Receiving: 6ms
So the loss of time seem to be in the "blocking"-section. I first thought of something like "limited number of TCP-Connections", but as said above, on the same system the page is remotly loaded fast enough almost without these "blocking"-parts.
They are located in different places on the file system. And i need to redirect from one project to another internally, so url for site.loc is preserved.
E.g. requesting site.loc/hey/there i need apache to serve files form proj2.0.
First, i know that on the .htaccess level we cannot use RewriteRule to file-system path (for security reasons).
Okay, an Alias is a workaround. Say I add an Alias to virtual host as following:
Code: Alias /newsite /some/path/to/proj2.0
Then if i'll add the rule to proj's .htaccess:
Code: RewriteRule ^hey/there /newsite
This will work.
But, the webroot does not work:
Code: RewriteRule ^$ /newsite
Is it i'm doing something wrong or there is some quirk about the webroot?
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.
Because of the attack on theplanet yesterday, my sites were down.
People are mentioning adding "redundant DNS servers" to protect against downtime in future attacks.. but I haven't found any info on how to set these up.
I also seen somebody post that the planet doesn't allow "zone transfers" so I'm a bit confused at how to proceed.
I just registered an account at [url] and I'm unsure on where to begin. Their FAQ is just a large photo.
My .com is registered at Godaddy. Do I edit records at godaddy to point to the server IP? Or do I have to edit records via WHM?
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 a renewal bill for my hosting account, but I can't see if I have any domains in it and therefore not sure if I should cancel it or not. I am with bright-byte.
Can I do a domain tools reverse search or something on the domain so it can tell me which of my domains are with that host?
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.
Some questions...
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:
Quote:
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?
I have a DB server, running mysql 64bit. I would like to add another server to the mix to build some kind of redundancy if the 1st one were to go down.
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.
I want to add a DNS Failover automated service at my server, in order that when it goes down, the DNS Failover enters in action and it will redirect all the traffic to a second backup/failover server (hosted at a different location).
So in order to do this i have been looking around and i have found dnsmadeeasy, and i found their offer interesting.
But i still have some question and doubts on how a dns failover service works. So maybe someone can expalin it to me.
My question and doubts:
1 - If i use for example the DNS failover from dnsmadeeasy, i would have to buy 2 servers where one is the principal server and the other is a backup/failover server, so when my main server goes down, the dnsmadeeasy will detect in a automatic way, and redirect all the traffic to my backp/failover server. After my principal server goes back online, dnsmadeeasy will automatic redirect all the traffic to the principal server.
Im i correct? Or i understound wrong how this works?
2 - I use my own Nameservers and i want to continue to use my own nameservers. So if i use dnsmadeeasy services, i will be able to continue to use my nameservers as ns1/ns2 and then i will add the dnsmadeeasy ns3/ns4...as the following example: ns1.mynameservers.com ns2.mynameservers.com ns3.dnsmadeeasy.com ns4.dnsmadeeasy.com ns5.dnsmadeeasy.com ns6.dnsmadeeasy.com
I am planning to rent 2 managed dedicate servers with windows server 2008 and ms.sql 2008. which I will use one for web application and 1 for database server.
why people usually divide them into web and database server? is it for security or performance reason?
Which one you prefer to choose?
- 1 server for web and 1 server for database. or
- 1 server(web and database) and 1 server for failover
In making my plans for my web hosting business I plan to start, I've thought about a failover but wanted to know the best way to set it up.
I would ideally like to start with something like getting a small shared hosting solution (not reseller, just shared) at a reliable hosting company. On this hosting plan, I will host a simple 1 page site that says my company is having technical difficulties, reminds people that data is safe, and provides any contact information accessable (like e-mail/phone/etc...).
I already have DNS setup offsite.
I would like that if my server(s) go down for any reason, whatsoever, that DNS automatically starts serving the temp site.
so if my server suddenly goes down, [url]or [url]suddenly goes to the offsite shared hosting plan.
This would not provide customer site redundancy. This would only ensure that if anything happens to my service, customers have a page available that explains what is happening and has information to contact us to get more details.
