December 2, 2010 at 7:24 PM -0500 wrote:
>
>Our First Class email server runs on a dedicated bladeserver, but we also
>have a virtualized clone of it running under XEN on an identical "backup"
>bladeserver pool. Robocopy synchronizes the email network store daily
>and in the event of a server failure, we simply change the IP address of
>the virtual server to that of the failed server, start FCS and the virtual
>server takes over until we repair/replace/restore the primary server.
>
>The downside is that new FC updates have to be installed on both the hard
>and virtual servers, since the scheduled daily routine only syncs FC data.
Modify your robocopy script to also copy the fcserver folder (it will copy
executables while they're running) and anything else that's not mirrored
(FCAS apps, stats logs, etc). Then your upgrades will be in synch.
>
>
>We still have a few high utilization servers running on dedicated
>hardware, each with its own virtual backup, but one day soon, we will
>probably run everything from virtualized server pools.
>
>In the last few years I have learned that virtualized server pools are to
>dedicated servers what RAIDs are to hard drives.
>
>
>
>
>Ed Paynter
>Manager of Information Systems
>Greensboro Day School
>
>
Gregg Kaloust
gregg@kannoncom.com
Kannon Communications
FirstClass Platinum Partner
www.kannoncom.com
http://twitter.com/greggkannon
[ For info on ISED-L see https://www.gds.org/podium/default.aspx?t=128874 ]
Submissions to ISED-L are released under a creative commons, attribution, non-commercial, share-alike license.
RSS Feed, http://listserv.syr.edu/scripts/wa.exe?RSS&L=ISED-L
