jethro Posted October 16, 2005 Share Posted October 16, 2005 Any chance of having a look at possible real time db backup to a second "hot" board, i.e one that sits there and doesn't get used unless the production site goes down through whatever errors? This would just add a touch of the warm fuzzies for commercial companies. Link to comment Share on other sites More sharing options...
athlonkmf Posted October 16, 2005 Share Posted October 16, 2005 look into mysql replication then. Link to comment Share on other sites More sharing options...
jethro Posted October 16, 2005 Share Posted October 16, 2005 look into mysql replication then. Not the answer most commercial organisations using the product for their web presence are going to actually accept. This is a suggestions and ideas forum, just throwing in something which might be worth considering. Remember not all companies have an IT department specialising in setting this sort of thing up. For example, this morning l am out in the western suburbs upgrading a site, cause they do not have the internal specialists. An answer of "you will need to upgrade to get that functionality" is clearly not going to do them any good. Link to comment Share on other sites More sharing options...
hartzr Posted October 16, 2005 Share Posted October 16, 2005 This isn't something that can be done with IPB itself in a very practical way. You need at least two machines sitting behind a load balancer, which can be done with stuff currently available. Link to comment Share on other sites More sharing options...
mindstormmaster Posted January 5, 2006 Share Posted January 5, 2006 I've looked into replication via mysql, and some of the php functions used don't make this the most feasible idea. A lot of this stems from the autoincrement values that are used in each table, and php needing to access the last inserted value, which if you have two instances accessing the same replicated database causes problems. Link to comment Share on other sites More sharing options...
athlonkmf Posted January 5, 2006 Share Posted January 5, 2006 it requires some tricks but it's doable. Say you have 2 servers. 1 main, 1 backup with replication. You need another server that acts as a heartbeat monitor. I'd say use your server2 for that. If the server1 goes down, the heartbeat monitor needs to switch the DNS-entry to server2 (so using server2 as teh dns-server might be a good idea) Then server2 runs a script to stop the replication (slave stop;) and put the site out live. If server1 comes back online, the heartbeat monitor will know, but because the DNS is still pointing to server2, no one will get to server1. That is the failsafe part. If you want to restore server1 as main server, you can do it manually or with scripts too. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.