On Thu, 2004-07-22 at 11:14 +1000, Mary Gardiner wrote: > On Thu, Jul 22, 2004, Trevor Tregoweth wrote: > > Hi All > > > > after my last post, which i think wasn't quite to the point, i would > > like to find out how to have a web-backup server, and how to configure > > them, so that when one goes down the other takes affect. > > > > Thanks for you help and suggestions > > I know I said off-list that I didn't have much help to offer on this > one, but I suspect people who do might find answers to the following > useful: > > 1. What kind of website? (is it all static HTML files? scripts? database > driven?)
Yep, this one is probably the most important. If you're just talking static HTML files, it's a much simpler problem. Database synchronisation is seriously *hard* for any non-trivial work. If it's just static stuff, I'd be going for having 0-TTLs on the DNS records for your domain and having some kind of heartbeat control a switchover. You also get the option of doing round-robin DNS in the normal case for better scalability. If you do want database driven stuff, well, I don't have any simple answers. Commercial databases have made some progress on this problem. But to give you sensible commentary we really need to know a lot more about what the website does. Can you tell us some details about it? HTH, James. -- James Gregory <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part
-- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
