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

[Johnathon Tinsley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Juergen Schinker wrote:
>> So some questions I have are:
>>
>> - Do I need to always buy servers in pairs and put load balancers in
>> front of them?
>> - create Xen-based servers which allow VMs to be migrated to another
>> server? (Servers in pairs again)
>> - just recreate the production server on a test machine or VM, test
>> then upgrade production machine and hope for the best?
> 
> Buy at least 2 Server pref same architecture
> 
> make them XEN-Hosts with LVM2
> 
> put infront LVS as loadbalacer (3. Server)
> 
> 
> 

4 servers. 2 Hosting your app, 2 firewalls. The firewalls handle
load-balancing, the backends host your website.

Firewalls have heartbeat, with a virtual IP address to which all your
traffic is pointed. If a firewall goes down, the ip snaps to the other
server, as does the traffic. Limit is the MAC address caching on the
routers, but if you set it up right, at most the site should be down
only for ~5-10 seconds.

At least, that's how we set them up where I work :-)

(Managed server hosting, including 4/6 failure resilient server clusters...)

Johnathon
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkn8uygACgkQ81bUwCB/xdjsbwCgvmQohHuI4vj+9D3za8Ez0XM7
WEAAn2qVWlw7fvX0nept2Rur3GrE3DZN
=e7Kd
-----END PGP SIGNATURE-----
-- 
Gllug mailing list  -  Gllug at gllug.org.uk
http://lists.gllug.org.uk/mailman/listinfo/gllug