1 / 11

High Availability Concepts

High Availability Concepts. Vladimir Bronstein. Introduction. High Availability – the buzzword and the meaning Vladimir Bronstein – experience with high availability in telecom equipment. Topics of Discussion. High Availability – what is it and why we need it?

snow
Download Presentation

High Availability Concepts

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. High Availability Concepts Vladimir Bronstein CoolTechClub

  2. Introduction • High Availability – the buzzword and the meaning • Vladimir Bronstein – experience with high availability in telecom equipment CoolTechClub

  3. Topics of Discussion • High Availability – what is it and why we need it? • High Availability – problems to solve • High Availability – how to make it? CoolTechClub

  4. What • Five nines 99.999% - 5 minutes in a year downtime • Service availability (always on, internet dial tone) • Absolute reliability and survivability • Data integrity and protection CoolTechClub

  5. Why • Internet centralized service model • Many people rely on internet delivered service (service dependency) • Around the clock operation – no “maintenance time”. • “Carrier-grade” systems – a buzzword • Business downtime costs a lot of money CoolTechClub

  6. Problems • Equipment and software not reliable enough • MTBF and MTTR – availability = (MTBF + MTTR)/MTTR • Complex systems – combination of MTBF of components • MTTR – for software – automatic recovery (reboot) – still bad CoolTechClub

  7. How • No single point of failure – hardware, software, network • Redundancy for hardware • Warm restarts for software (problematic) – so better rely on hardware redundancy as well CoolTechClub

  8. Redundancy Types • Load sharing, hot standby, cold standby • 1:1, 1:N, M:N • Chain redundancy versus block redundancy CoolTechClub

  9. Software challenges • Faults and Fault isolation • Failures – result of faults • Ways to recover – redundancy hot failover • Hardware failover – switching HW resources (network, fans, CPUs) • Software failover – applications, protocols, databases etc CoolTechClub

  10. Design principles • Hot swappability support – to replace faulty units (FRUs) • Resource (equipment and software modules) model and management • Logging, trace, reporting of failures/switchovers • Checkpointing (data mirroring or synchronization) initially and continuously • Provisioning – redundancy state, software upgrades, different versions. CoolTechClub

  11. Solutions • Proprietary (long known in telecom industry). • Standard (SAFORUM middleware interface specification) • Off the shelf software – Linux Carrier Grade Platform • GoAhead software CoolTechClub

More Related