Marathon everRun HA

Marathon Technologies has traditionally offered a cost effective alternative to hardware-based fault tolerant servers and clustering and its latest everRun HA software aims to increase its appeal.

Up until now Marathon's sole product was its everRun FT software which while delivering a superb range of features does have a few limitations such as a lack of support for SMP and a price tag that puts it beyond the reach of many SMBs.

The concept behind the HA software is virtually the same as for FT as it uses two physical servers, called CoServers, to present a single, virtual server to the network. RAID-1 disk mirroring is performed across the CoServers to ensure that both disk systems are synchronised. As all components are duplicated if any fail then the software redirects all operations to the functioning component. HA delivers a wide range of new features that are designed to improve its scalability.

First up is CPU support in the virtual server as HA scales up to four logical processors under Windows Server 2003 (WS2003) Standard and up to eight with Enterprise. AMD support is on the cards but at the time of writing Marathon was unable to give us a date. Memory limitations have been cut as although the HA virtual server still only supports 4GB with WS2003 Standard this have been boosted to 32GB for Enterprise.

Key requirements for FT are that both physical servers must be absolutely identical as it performs lock-stepping across them. HA doesn't require this although Marathon does recommend that the storage sub-system and drives should be a close match. It uses the same code as FT but the virtual server is actually only hosted on one physical system.

The primary server is designated as the Active component whilst the secondary server is the Ready server. For fault tolerance, FT can handle a complete physical system failure which will not affect operations as the virtual server is being hosted across both systems. The same situation with HA will cause some downtime as the virtual server has to be migrated across from the Active server to the Ready server. This means that transactions occurring at the time the Active server failed are unlikely to be preserved. Essentially, FT provides full server redundancy whereas HA offers component redundancy.

To test HA we used a pair of HP ProLiant ML370 G4 servers equipped with dual 3.2GHz Xeon processors and 1GB of memory. Each storage sub system comprised an HP Smart Array 641 RAID controller and a pair of 73GB hard disks. Your first job is to decide how the servers are to be connected together as for disk mirroring and I/O redirection to function the servers must be linked directly with up to two Gigabit Ethernet crossover cables. You'll also need adapters for presenting your services to the network over a virtual connection and you can use a fourth for isolating management access.

Our test servers had four Gigabit Ethernet ports which we configured for single CoServer and redirected links. We decided to keep management local to the servers so left this network connection out of the equation.

Software installation is a fairly straightforward if lengthy process as you need to install the Windows OS on each physical CoServer. Next, you install the relevant Windows service packs and once these are in place you load the HA software on each one. This must be done on CoServer1 first followed by CoServer2 and during these phases you define what roles each network adapter will play. From the HA management interface you create a virtual boot disk which then requires a third copy of Windows installed. Note that the virtual server must have an OS installed that is identical to that loaded on the CoServers.