Marathon Technologies Product Overview Agenda

Marathon TechnologiesProduct Overview

2Marathon Confidential

Agenda

• everRun Product Family

• everRun Availability Architecture

• everRun FT Product Overview

• everRun HA Product Overview

• everRun SplitSite


everRun Product Family

• everRun HA– High availability for any Windows application

– Complete data and transactional integrity

• everRun FT– Fault Tolerance for any Windows application

– Zero downtime due to faults and failures

– Zero data loss – ensure data and transactional integrity

• everRun SplitSite– Supports both everRun HA and everRun FT

– Continuous operations through a site disaster

– Geographically separate Servers


everRun Configuration

• Software Solution– No proprietary hardware

• Two standard x86-based servers

• Storage types – DAS, NAS, SAN

• Two standard gigabit Ethernet links

• Standard Windows operating system

• Marathon software

• Any Windows application (Unmodified)


Device VirtualizationBuilding 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


Application & User Perspective

• Applications are installed in the Virtual OS environment

• Appears as a standalone reference server

• Clients connect to one server - always

everRun HAProduct Overview


Marathon everRun HAThe Next Generation Availability Technology

• A comprehensive high availability solution for– Applications with a short Recovery Time Objective (RTO)– Non-cluster aware applications– Applications needing higher and more robust availability

• Minimizes downtime due to faults– Computes through most device failures– Downtime only as a result of a complete server failure

• Scalability and 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


everRun HAHow it Works

• Virtual Server environment runs on one server at a time– Utilizes Ready server and devices for redundancy

• Storage is synchronously mirrored – RAID 1– Zero data loss

• Planned migration synchronizes Memory & I/O– Then migrates Virtual Server– Application remains online and available – no interruption

LAN

RedundantCoServer LinksCoServer 1

ActiveCoServer 2

Ready

VirtualServer


Device VirtualizationDisk Mirroring – Logical View

Virtual ServerApplication Environment

Virtual Disk

• Single write by the application

• Simultaneous writes to each physical disk


Easy to Operate & MaintainComputeThru® Disk Failures

Storage Storage Storage StorageDisk FailureOccurs

• A device failure simply causes a redirection of the I/O• Completely transparent to users• Zero application downtime• Repairs scheduled when convenient


LANLAN

Network FailureOccurs

Easy to Operate & MaintainComputeThru Network Failures


Active CoServer operating normally

Primary server fails

Ready CoServer OS and app

restart

Automated RecoveryComplete Server Failure Recovery

Server FailureOccurs

• Immediate migration of Virtual OS and app.

• Rapid consistent restart in virtual environment

• Migration only in event of server failure• Ready resources actively in use• No scripting or testing required• Ready server continually tested by system

to ensure successful migration


Application running in

Active CoServer

Application running in Ready

CoServer

Online MigrationReduce Scheduled Downtime

OnlineMigrati

on

App App

Application Operations Never StopClients Never Disconnect

• Seamless migration of Virtual OS and app.

• Zero application downtime• Maintenance without user impact• Migrate back or leave as is

everRun FTProduct Overview


Marathon everRun FT

• Continuous availability for zero downtime

• For critical applications with a Zero Recovery Time Objective (RTO)

• Complete hardware redundancy– Computes through all failures

– Ensures zero downtime through minor and major faults

– Ensures zero data loss

• Unique innovation in lockstepping– 12 US patents

• Mainframe-class availability (99.999%+ uptime)

• Supports any Windows application– No modifications or high-maintenance scripting

– No need cluster-aware versions that cost more


Marathon everRun FTA Logical View


Marathon everRun FT

How It Works

LAN

RedundantGigabit Ethernet

Links

CoServer 1 CoServer 2

Fault TolerantVirtual Server

• Lockstep processing– Both servers process transactions in parallel

• Both systems completely synchronized– Memory– I/O– Storage


Marathon everRun FT

Fault Management

Marathon everRun FTApplication Environment

Marathon everRun FTApplication Environment

Both Servers Operating

Redundantly

Operational Server

Failed Server

Failure

Occurs

• NOT a failover – simply a removal of the failed server• NO application downtime – Application is never affected• NO lost data• Once repaired, the failed server is simply brought back

online

20

Marathon Availability SolutionsSolutions to Meet All Availability Needs

FT

• Fault-tolerant software for continuous application operation

• For those applications that can’t afford ANY downtime

• Applications ride-through planned or unplanned events

HA

• High-availability software for fast, automatic application recovery

• For those applications that have a short Recovery Time Objective (RTO)

• Applications ride-through planned and many unplanned events and quickly recover from server failures

CoServer 1 CoServer 2

LAN

Active ReadyLAN


everRun SplitSite®

Survive A Disaster Rather than Recover From One

• Separation of CoServers to support disaster tolerant configurations– Different rooms in a building– Different buildings on a campus– Geographical separation

• Prevents Split-Brain

• CoServer Links use IP Backbone

• Routable over WAN / MAN


Addendum SlidesComparing clusters and replication


everRunvs. shared-disk Clusters

• Clustering Misconceptions– Microsoft Clusters are ‘free’

• They are included, but certainly not free

• Costs of applications, maintenance, administration

• Require custom coding for application support

– Cluster-aware applications make clustering simple• Maintenance of two instances

• Failover configuration and management

• Clusters require specialized skill set


everRun HAHigh Availability Superior To Clusters

• Significant improvements over clusters– Any application - No modifications– No special scripting– Simple administration– No failover resource planning– No shared storage or SAN requirements

• Provides better availability than clusters– ComputeThru technology - Fewer failovers– No false failovers

• Site-wide protection with SplitSite

Active ReadyLAN

SplitSiteGeographic separation of servers


Clusters

• Shared storage - doesn’t protect the data

• Require expensive and complex SAN to provide data redundancy

• Single point of failure

• Require two fully configured servers

• Two servers and applications to maintain

• Requires specialized expertise

• Minimal application support

• Require ‘cluster aware’ applications

• Majority of applications not ‘cluster aware’

• Distance limited to just a few miles due to shared-disk connections

everRun HA

• Maintains synchronous data copy• No single point of failure

• Appears as a single reference system• One system to install and manage• One application license

• Supports ANY application• No need for ‘cluster aware’ versions

• SplitSite allows miles of separation between servers

• Complete protection from site failures

Data Protection

Simple to deploy

and manage

Application

Support

Site-level

Protection

everRunHigh Availability Superior To Clusters


Clusters

• Requires extensive configuration and ongoing management to maintain failover

• Manual policy configuration for fault management

• Doesn’t handle faults, simply fails over

• Any device failure causes application shutdown and restart – DOWNTIME

• Any maintenance requires application to be shutdown and restarted on standby server

everRun HA

• All fault and policy management handled by everRun

• No configuration necessary – works ‘out of the box’

• Hardware layer masked from application environment

• ComputeThru technology redirects I/O away from failed devices without affecting application state

• Maintains extremely high levels of uptime

• Online migrations allow application to be migrated between servers without interruption

Failure

Management

Fault Handling

Online

Maintenance

everRunHigh Availability Superior To Clusters


Replication Solutions

• OK for disk-2-disk data backup where data loss is acceptable

• Not designed for application availability

• Rudimentary failover solutions– Vendors claim 2-minute failover – Best case yet unlikely

– Can take upwards of 90 minutes

– Manual recovery due to corrupt data can take hours

• Can’t guarantee data integrity– Utilize asynchronous or scheduled replication

• High latency

• Inherent loss of data

• Corrupt databases

– Often require manual rebuild of database from log files


Product ComparisoneverRun HA vs. Replication

Replication

• Asynchronous replication implies lost data

• Can’t guarantee data or transactional integrity

• Require two fully configured servers

• Two servers and applications to maintain

• Continuous maintenance burden to maintain and test failover process

• Some vendors provide application specific modules for helping with configuration

• Requires custom scripting to fit specific customer environments

• Any maintenance requires application to be shutdown and restarted on standby server

everRun HA

• Maintains synchronous data copy

• Guarantees data and transactional integrity

• Appears as a single reference system

• One system to install and manage

• One application license

• All policies maintained within everRun

• Supports ANY application out-of-the-box

• Doesn’t require any scripting

• Online migrations allow application to be migrated between servers without interruption

Data Protection

Simple to deploy and manage

Application Support

Online Maintenance


Product ComparisoneverRun HA vs. Replication

Replication

• Requires extensive scripting configuration and ongoing management to maintain failover

• Automatic failover not recommended due to likelihood of split-brain

• Doesn’t handle faults, simply fails over

• Any device failure causes application shutdown and restart – DOWNTIME

• Require manual rebuild of production server

• Often requires manual configuration of data recovery

• Always requires shutdown of application to fail back to production server

everRun HA

• All fault and policy management handled by everRun

• No scripting necessary

• Fully automated failure management – no operator intervention required

• Hardware layer masked from application environment

• ComputeThru® technology redirects I/O away from failed devices without affecting application state

• Fully automated recovery of data and application environment

• No interruption of application state during recovery

Failure Management

Fault Handling

Recovery


System Management

• Application Management via the Virtual Server

• CoServer management via the physical server

• Host system management

• Framework SNMP support


Marathon everRunApplication Environment

everRunEnvironment

everRunEnvironment

CoServer Environment

Desktop

CoServer Environment

Desktop

everRun Icon

everRun Icon


Marathon ManagerManagement GUI


Marathon ManagerDisplay of a Fault

• CoServer with disk

failure is highlighted

• Failed disk is marked

• Server remains online

• Fault is “managed around” while other

components remain available

Example: Disk Failure