[Gllug] best way to update a single production server?

Jose Luis Martinez jjllmmss at googlemail.com
Tue May 5 09:57:31 UTC 2009


On Tue, May 5, 2009 at 10:52 AM, Khusro Jaleel <kerneljack at gmail.com> wrote:
> Thanks, guys, for all your feedback.
>
> I assume, then, that if you have 2 web servers with failover (Xen,
> LVS, firewall, whatever), then if you need to do a little DB storage,
> let's say a simple User Guestbook, etc then it's best to put the DB on
> another server, isn't it, or a NAS, etc? This is assuming a web server
> that is 99% read-only, with only the occasional DB access.
>
> Can you guys recommend a good NAS for this purpose, if that is a good solution?
>
> I know DB mirroring between the 2 servers that are running in tandem
> can be setup, but I don't think it would work as reliably? I know
> sometimes you need to promote DB slaves to masters before they will
> work?
> --

Big shops normally adhere to the mantra of a system (or group of
systems) per function. You will not see a DNS, mail, web and DB server
function running from the same set of machines....
-- 
Gllug mailing list  -  Gllug at gllug.org.uk
http://lists.gllug.org.uk/mailman/listinfo/gllug




More information about the GLLUG mailing list