Transcript Marathon 07-03-07

Marathon everRun™
Next Generation Availability
Martin Kyprianides
EMEA Systems Engineer
Marathon Technologies
Agenda
• Market
• About Marathon
• everRun Solutions
– everRun FT
– everRun HA
– everRun SplitSite
• Product Demo / Q&A
2
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
3
The Availability Pyramid
AL4:
Continuous
Availability
“Real-time” 24x7
Operations,
No User Interruption
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.
4
Source: IDC
Comprehensive Solutions
Automated Application Availability
• 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
5
Comprehensive Solutions
Automated Application Availability
• 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
6
Marathon’s Technology Vision
Next Generation Availability - A suite of software products designed to
meet a broad range of availability requirements
7
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
8
Availability Market
Verticals
(Line of Business)
Large Enterprise
Medium Enterprise
Horizontals
(Infrastructure)
• MARATHON’S “Sweet Spot”
• 60% of current revenue
• Rapidly Growing
• 30% of current revenue
• Key Verticals:
• Manufacturing
• Financial Services
• Media/Broadcasting
• Gaming
• Healthcare
• Key Applications:
•Exchange
•SQL Server
•Oracle
•Notes
•ERP/CRM
• Strong ISV support
Small Enterprise
9
• Emerging
• “Availability for the Masses”
• Far easier, “Automated” and less expensive
Marathon Solutions
Proven in Mission Critical Environments
Financial
Media
Airports
Government
Manufacturing
Resorts/Casinos
Energy
$1 Billion
Hedge Fund
Logan
Pharmaceutical
10
Technology
Telecom
everRun™ Solutions
everRun FT
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
13
Marathon everRun FT
How It Works
• Lockstep processing, requires 100% identical hardware
– Both servers process transactions in parallel
• Both systems completely synchronized
– Memory
– I/O
– Storage
CoServer 1
Fault Tolerant
Virtual Server
Redundant
Gigabit Ethernet Links
LAN
14
CoServer 2
everRun FT Architecture
Virtual Server Hosted on Both CoServers
Lockstep everRun FT Environment
VS OS
Public
Ethernet
15
VS
Processor
VS
Processor
CoServer
Processor
CoServer
Processor
PCI-X
Gig-e
Main Memory
Main Memory
Storage
VS OS
PCI-X
CoServer OS
CoServer OS
CoServer 1
CoServer 2
Storage
Public
Ethernet
Marathon everRun FT
ComputeThru® Server & Component Failure
Marathon everRun FT
Application Environment
Both Servers
Operating Redundantly
16
Marathon everRun FT
Application Environment
Operational
Server
Failed
Server
Device Virtualization
Building Redundancy
• 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
17
everRun Virtual
Server
Application
Environment
Virtual
Disk
Virtual
NIC
LAN
RAID1 Disk Mirroring
Logical View
Virtual Server
Application Environment
• Single write by the application
• Simultaneous writes to each
physical disk
Virtual Disk
Mirrored
Physical Disks
18
System Management
Marathon Manager Interface




19
Monitor Health and Status
Check Failure Detail
Enable/Disable Devices
Make Operational Settings
 Mirror Copy Bias
 Auto Recovery
 CoS Link Optimization
 Delta/Full Copy
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)
20
everRun HA
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
22
everRun HA Architecture
Virtual Server Hosted on Active CoServer
Virtual Server OS
Public
Ethernet
23
Ready VS
Processors
CoServer
Processors
CoServer
Processors
PCI-X
Gig-e
Main Memory
Main Memory
Storage
Active VS
Processors
PCI-X
Active CoServer OS
Active CoServer OS
Active
CoServer 1
Ready
CoServer 2
Storage
Public
Ethernet
RAID1 Disk Mirroring
Logical View
Virtual Server
Application Environment
Identical to everRun FT
• Single write by the application
• Simultaneous writes to each
physical disk
Virtual Disk
Mirrored
Physical Disks
24
Easy to Operate & Maintain
ComputeThru® Component Failures
Storage
Mirror
Storage
Disk Failure Occurs Storage
I/O is redirected to redundant component
(identical to everRun FT)
25
Storage
Automated Recovery
Complete Server Failure Recovery
Server
Failure
Occurs
Active CoServer
operating normally
26
Primary server
fails
Ready CoServer OS
and app restart
Online Migration
Reduce Scheduled Downtime
• Requires 100% identical hardware
App
Online
Migration
Application running
in Active CoServer
Application running
in Ready CoServer
Application Operations Never Stop
Clients Never Disconnect
27
App
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
28
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
29
everRun SplitSite
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
31
everRun SplitSite - Networking
Flexible CoServer Connectivity
• CoServer links can be:
Dedicated
fiber
– Dedicated fiber
– Private switched network
Management Network
– Public internet
• Bandwidth requirements (per link), for fault
handling & performance
WAN
Public
Network
Switched
– Minimum bandwidth = 51 Mbps
– Recommended bandwidth > 155 Mbps
Management Network
WAN
Public
Network
• Latency requirement:
– Maximum latency = 5 msec
– Recommended latency < 2 msec
– CoServers on same IP subnet or vLAN
32
Public
Network
Management Network
WAN
everRun SplitSite - Quorum Service
Protects Against Network Failures
CoServer
Links
Management Network
Public Network
Quorum
Server
33
• Service runs on any networkaccessible 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
Thank You.
Questions?