I'm working for a client who has an e-commerce site currently hosted on a shared hosting solution.
He is now looking for 100% uptime (as near as), so I have suggested that we get 2 VPS and use DNS monitoring to switch servers as required (from DNSmadeEasy).
This is all fine, and the websites files/images do not change often, so I can use rsync every so often to sync these. Not a problem.
What does change frequently is the mySQL db for the site.
I've been looking at MySQL replication, but this seems to be no good. If one server goes down, then the other one takes over, they don't automatically sync themselves after they come back up. It seems MySQL cluster is best, but this needs 3 servers and they all need to be on the same LAN.
I've read you can set MySQL replication to MASTER-MASTER so that it acts like a cluster, and resyncs itself as required.
I don't know much about MySQL replication at all but am trying to present a few different options to a client of mine.
They run a large eCommerce site with a very active database. For several reasons, they are considering having their site mirrored across two completely different dedicated hosting providers.
The question here is, is it also possible to replicate the MySQL database in real-time across external servers and if/how secure it is.
Essentially, if one DC becomes inactive they'd like to fall-back on the other. An even more ideal solution would be to split traffic across the two... but not sure if that's even possible, perhaps with DNS?
Some of you may have read my previous posts about a dual server configuration I am currently working with. I run a high traffic forum which has up to 2-3k of people online at once. I was wondering if it could be effective to setup MySQL Replication of certain tables which are read very frequently and then modifying the script to grab data from the slave server rather than the master? For say viewing threads, forums etc. Information which isn't updated literally every second.
A few questions...
-Will this place a lot of load on the master having to write the data to the slave as well? As in would the load I save on SELECT queries be used on writing to the slave anyway?
I'm not too experienced with this, so I'm hoping someone more enlightened here can help.
Scenario: I'm trying to build a social network site geared towards old people. I'm using LAMP environment. I want to have 1 mysql master (writes) and 2 mysql slaves (reads). Two web servers will read from the 2 mysql slaves and write to the one mysql master.
Questions: My concern is this: when a user posts a comment via the webserver, the comment is written to the mysql master. I would like for him/her to see the comment he posted right away so they don't think something failed or went wrong. I'm afraid that replication to the mysql slaves will take some time to sync all of the mysql databases together. How can I work around this? Or am I mistaken and this doesn't actually happen?
How fast is replication? How can I mitigate this delay in replication to show the user instant results of their submission.
The same thing can apply to uploading photos to a user's profile.
I never did replication and do not know much about it so I figured I would ask here if anyone knows or has done it before like this.
I have a user who wants me to enable replication on my server for his user. I dont like the sounds of it on a shared environment but if there is no risk to other users and its not a big resource hog I will do it. Anyway, from what I gather I have to:
1. execute: GRANT REPLICATION SLAVE ON user_main.* TO 'repl'@'ip-here' IDENTIFIED BY '4T6WjUZa'; [url]
2. Stop mysql server and Add in my.cnf: [mysqld] log-bin=mysql-bin server-id=1 slave-compressed=1 binlog-do-db=user_main start server[url]
3. execute: SHOW MASTER STATUS; we need values of colomns File and Position from output of above command[url]
So my questions are:
Is there any security risk? Is there significant extra resource usage? Is this even done on shared environments?
I have fairly a large web site that has a forum and a torrent tracker.
Currently MySQL server is handling about 150 queries an avarage per second. Here is the server spec:
Core2Duo 2.66Ghz 4Gb RAM 320GB SATA 7200RPM (Server provider does not have 1.5K RPM nor 1.0k RPM) 100Mbit Connection (servers on the same switch and the switch does not have 1Gbit port) MySQL Version: 5.0.51a
I had Master-Master Replication setup with forum running on one and the tracker running on the other. Although this has been working for about few days, we started seeing lags in the replication process. After a week, there is a major lag and the changes made on one of the servers takes about 5 hours to appear on the another. So, this doesn't work.
What would be the other ways of splitting MySQL queries concerning the same database?
While I was researching, I read about MySQL Cluster with database storage engine being NDB.
But, let's say that there is a power failure on both the nodes at the same time, then I would lose the whole database as the database is stored on the memory correct? I would not like to take that chance either, but if this is faster then replication method then maybe I will concider.
I thought about editing the forum coding to make all queries that concerns the tracker to go in to, say server B (with forum's primary MySQL server being Server A), and make the tracker use server B as MySQL backend, but it seemed like a heavy work so that will be the last choice.
We are currently configuring two machines to act as primary / secondary name servers.
Both machines are server 2003 Standard Editions, obviously based in seperate locations.
I would like to replicate all primary zones as secondary zones on the second server.
However If a machine dies I dont want to have to re-add every zone manually - I would rather point the machine at the other one and have it pull back information for all zones that machine is authorative for.
Is there a way to do this on server 2003 DNS or not?
What would be the best way to replicate two exchange servers across a WAN? I would like to run exchange but in two different physical locations for redundancy and backup purposes, to ensure if one goes down, the other is right there. Is there any good commercial solutions?
I'm trying to find a low cost solution for realtime file share replication in a windows environment.
It doesn't look like there are any open source windows cluster filesystems around, so the only viable option I found would be running OpenFiler in a replication cluster on Hyper-V nodes. Has anyone worked with this, does it work reliably?
The required IO throughput on these shares would really be minimal and my biggest concern is 100% availability.
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
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.
We have 2 Cisco PIX 515's in a failover configuration (7.1 series IOS). We have available both a serial failover cable and adequate switch capacity to allow using either the serial or LAN-based approach. We have no current plans to locate the firewalls physically apart.
We have plenty of info on how to configure either, but no recommendation on which is the better choice.
I have a reseller account with a company that often has spontaneous DNS errors, and this, as you know looses us money. I also have a dedicated server running a panel exclusively via IIS. Is there a way I can set up my dedicated (Windows) box and my reseller account in a mirror way, so if one of them fails, the other will take over.
There are no file changes often, more database then anything. Is this possible? Main necessities are:
(Or, if a shared hosting company can accommodate this somehow and is relatively inexpensive.
Basically have 2 hosting accounts at different providers...each set-up for the same domain name...and then somehow wtih DNS make it so if host #1 goes down traffic goes to host #2 (which would basically be a splash screen explaining that host #1 is down and will be back soon).
DNS isn't my strong point, but I do know you can do this with MX records...so if the first server fails it tries the next until it gets a working one or reaches the end of the list. I'd just like to do it is A records.
It wouldn't be as simple as setting the nameservers like this would it?
Assume, a DNS failover service would change the DNS from server 1 to server 2 when the first one is offline. This will be changed quite fast, however isn't it true that some visitors still experience a downtime of a couple of hours (saying that the main server will be offline for 6 hours) as their ISP might not update DNS that frequently?
So basically, what is the added value of a failover service?
What happens if your primary nameserver goes down? Meaning that it goes completely off the net, not even denying dns requests but completely ignoring them.
I'd guess that resolvers would query the secondary NS after a specified timeout, but what is that timeout set to? Does it differ from ISP to ISP? How much of a slowdown are we looking at for end users?
We want to provide failover service at our server using dnsmadeeasy service.
So we have already buy the "failover server" (running linux/plesk), and now we are looking to find the most adequate / best way in order to keep the 2 servers sincronized, in order that if "main server" goes down, all the traffic can be redirect to the "backup server" using dnsmadeeasy.
on scripts/software to keep 2 linux servers sincronized in a failover setup?
Well my problem is, we have 2(ABC and XYZ company) internet connection and sometimes, the ABC connection is not active and we're disconnected for about 2-4 minutes interval to get the XYZ internet connection online.
My question is - Is there a software that will automatically set the XTZ internet connection to active? Something like if the ABC connection is down, the XYZ will supply internet connection right away.