1. 1 Marathon everRun™ Next Generation Availability Martin Kyprianides EMEA Systems Engineer Marathon Technologies

2. 2 Agenda Market About Marathon everRun Solutions –everRun FT –everRun HA –everRun SplitSite Product Demo / Q&A

3. 3 The Growing Need for Availability Application availability – No longer a luxury for any business Cost of downtime – Has risen dramatically in recent years Regulatory Compliance – New and changing laws governing availability Server consolidation – Will drive high availability in the enterprise

4. 4 The Availability Pyramid AL4: Continuous Availability AL3: High Availability Clustering/failover User Interruption. AL2: Recovery Data Back-up & Data Replication User interruption. AL1: Reliability Hot swappable components, ECC memory All service stops. AL0: Unprotected Servers No redundant system components, no protection for data, application, or OS. All service stops. Source: IDC “Real-time” 24x7 Operations, No User Interruption Limited Requirement Continuous Requirement Applications and Data Availability

5. 5 What we do? –Marathon delivers Next Generation Availability for Windows applications in a simple, comprehensive & automated solution –Superior application availability on standard Windows servers –Fault Tolerance and High Availability for ANY Windows application –No scripting or modifications required Comprehensive Solutions Automated Application Availability

6. 6 How do we do it? –A patented virtualization architecture that creates a single virtual server environment –ComputeThru ® failures vs. traditional failover approaches –Provide Intelligent Policy Management – automatic vs. scripted Comprehensive Solutions Automated Application Availability

7. 7 Marathon’s Technology Vision Next Generation Availability - A suite of software products designed to meet a broad range of availability requirements

8. 8 Marathon Momentum Core technology & IP development began in 1993 –A history of invention - 15 US Patents Launched software only solution in January 2004 –Further expanded product line in April 2006 Market traction –Over 1,400 Companies are now using Marathon –Shipped over 2,500 software licenses to-date Global –Offices in US, Europe, APAC –Worldwide Channel Partner Network

9. 9 Availability Market Large Enterprise Medium Enterprise Small Enterprise Verticals (Line of Business) Horizontals (Infrastructure) MARATHON’S “Sweet Spot” 60% of current revenue Key Verticals: Manufacturing Financial Services Media/Broadcasting Gaming Healthcare Strong ISV support Emerging “Availability for the Masses” Far easier, “Automated” and less expensive Rapidly Growing 30% of current revenue Key Applications: Exchange SQL Server Oracle Notes ERP/CRM

10. 10 Marathon Solutions Proven in Mission Critical Environments Financial Media Government Airports Manufacturing Pharmaceutical Technology Resorts/Casinos Telecom Energy $1 Billion Hedge Fund Logan

11. 11 everRun™ Solutions

12. 12 everRun FT

13. 13 Marathon everRun FT Flagship continuous availability offering Complete hardware redundancy –Compute-through all failures –Ensures zero downtime through minor and major faults –Ensures zero data loss Unique innovation in lockstepping –15 patents, others pending Mainframe-class availability (99.999%+ uptime) –Equal to ~5 minutes of unplanned downtime per annum Non-Intrusive –Supports any Windows application –No need for cluster-aware versions that cost more

14. 14 Marathon everRun FT How It Works LAN Redundant Gigabit Ethernet Links CoServer 1 CoServer 2 Fault Tolerant Virtual Server Lockstep processing, requires 100% identical hardware –Both servers process transactions in parallel Both systems completely synchronized –Memory –I/O –Storage

15. 15 everRun FT Architecture VS Processor VS OS CoServer Processor CoServer OS PCI-X VS Processor VS OS CoServer Processor CoServer OS PCI-X Storage Public Ethernet CoServer 1 Gig-e Main Memory CoServer 2 Lockstep everRun FT Environment Storage Public Ethernet Virtual Server Hosted on Both CoServers

16. 16 Marathon everRun FT ComputeThru ® Server & Component Failure Marathon everRun FT Application Environment Marathon everRun FT Application Environment Both Servers Operating Redundantly Operational Server Failed Server

17. 17 Device Virtualization Building Redundancy Application Environment everRun Virtual Server Virtual Disk Virtual NIC LAN Creates a virtual Windows server –Single IP address –Single hostname –Single MAC address Like physical devices are redirected –Disks –Network Interfaces –CD-ROM –Tape Drives Paired to create a single virtual device Failed devices do not affect application availability

18. 18 RAID1 Disk Mirroring Logical View Virtual Server Application Environment Mirrored Physical Disks Virtual Disk Single write by the application Simultaneous writes to each physical disk

19. 19 System Management Marathon Manager Interface n Monitor Health and Status n Check Failure Detail n Enable/Disable Devices n Make Operational Settings wMirror Copy Bias wAuto Recovery wCoS Link Optimization wDelta/Full Copy

20. 20 everRun FT Hardware/Software Requirements Intel-based P4/Xeon or AMD servers –2 Processors (Physical / Logical) –1 Processor with HyperThreading or Dual-Core 512MB RAM (1GB, recommended, max 4GB) 2 NICs (3 or 4 recommended) 1 NTFS disk drive (2 or more recommended) OS options for both CoServer and FT (one for each CoServer, one for the FT) –Windows 2000, Server or Advanced –Windows 2003, Standard or Enterprise Single license for deployed application(s)

21. 21 everRun HA

22. 22 Marathon everRun HA The Next Generation Availability Technology Minimizes downtime –Applications ComputeThru® most device failures –Downtime only as a result of a complete server failure Scalability & Flexibility – Highly scalable – 2x, 4x, 8x (physical) SMP – Up to 32GB RAM – No need for identical server pairs Utilize existing hardware Broad Platform Compatibility – Intel / AMD multi-core CPU designs – SAN / DASD storage configurations

23. 23 Ready VS Processors CoServer Processors Active CoServer OS PCI-X Active VS Processors Virtual Server OS CoServer Processors Active CoServer OS PCI-X Storage Public Ethernet Active CoServer 1 Main Memory Ready CoServer 2 Storage Public Ethernet Gig-e Virtual Server Hosted on Active CoServer everRun HA Architecture

24. 24 RAID1 Disk Mirroring Logical View Virtual Server Application Environment Mirrored Physical Disks Virtual Disk Single write by the application Simultaneous writes to each physical disk Identical to everRun FT

25. 25 Easy to Operate & Maintain ComputeThru ® Component Failures Storage Mirror Disk Failure Occurs I/O is redirected to redundant component (identical to everRun FT)

26. 26 Active CoServer operating normally Primary server fails Ready CoServer OS and app restart Automated Recovery Complete Server Failure Recovery Server Failure Occurs

27. 27 Application running in Active CoServer Application running in Ready CoServer Online Migration Reduce Scheduled Downtime Online Migration App Application Operations Never Stop Clients Never Disconnect Requires 100% identical hardware

28. 28 everRun HA Minimum Configuration Processors – Intel-based P4/Xeon or AMD –One single-core HT processor –Two single-core processors –One dual-core Physical Memory: 1GB (CoServer defaults to 256MB) Storage: 1 drive (NTFS for all boot partitions) Networks –(1) GB Ethernet for CoServer Link –(1) 10/100/1000 for client (redirected) network Storage Controllers –SCSI Host Bus Adapter (FC, Copper), IDE Controller, Serial ATA, RAID Windows Server 2003 SP1, Standard Edition

29. 29 everRun HA Maximum Configuration Processors: 4 dual-core HT (16-way) –Standard Edition supports up to 4-way –Enterprise Edition supports up to 8-way Physical Memory: Maximum allowed by Windows Server 2003 –Standard Edition supports up to 4GB –Enterprise Edition supports up to 32GB Networks (7 total) –(2) CoServer –(1) CoServer Management –(4) Redirected Windows Server 2003 SP1 Enterprise Edition

30. 30 everRun SplitSite

31. 31 everRun SplitSite ® Survive A Disaster Rather than Recover From One Permits geographical separation of CoServers to support disaster tolerant configurations –Different rooms in a building –Different buildings on a campus –Different buildings in different towns/cities Provides necessary integrity for failures where CoServers are physically separated

32. 32 everRun SplitSite - Networking Flexible CoServer Connectivity CoServer links can be: –Dedicated fiber –Private switched network –Public internet Bandwidth requirements (per link), for fault handling & performance –Minimum bandwidth = 51 Mbps –Recommended bandwidth > 155 Mbps Latency requirement: –Maximum latency = 5 msec –Recommended latency < 2 msec –CoServers on same IP subnet or vLAN Public Network Public Network WAN Public Network Dedicated fiber Switched Management Network WAN

33. 33 everRun SplitSite - Quorum Service Protects Against Network Failures Service runs on any network- accessible server Scenario: Simultaneous break in all CoServer communications (e.g., an errant backhoe) CoServer that can communicate with quorum server stays online CoServer that can’t communicate with quorum server takes itself offline Split-brain operation is avoided while maintaining application availability Redundant Quorum Servers –If one quorum server fails, CoServers elect a second quorum server –Maximum protection from site disasters CoServer Links Public Network Management Network Quorum Server

34. 34 Thank You. Questions?