Architecting a Highly Available Infrastructure: An Overview SLN187. Mark Milow Mike DiPetrillo

Transcription

1 Architecting a Highly Available Infrastructure: An Overview SLN187 Mark Milow Mike DiPetrillo

2 Agenda Why? Solutions Q&A

3 Quick Stats 2004 Gartner study found an average of $42,000 per hour of downtime Average network experiences 175 hours of downtime a year (98% availability) That s $7.35 million in lost revenue each year An increase to 99% means only $3.68 million That s $3.67 million you can spend on DR

4 Quick Math: Amazon.com Revenue in 2001: $3.1B/year with 7774 employees Revenue Per Hour: ~$350,000 If outage effects 90% of revenue: ~$320,000 Assume average annual salary is $85,000 $656M/year or $12.5M/week for all 50 Hours/week: ~ $250,000 per hour If outage effects 80% of employees: ~$200,000 Total is $520,000 per hour of downtime

5 Why and for What? Different levels Planned disasters (hurricanes, etc.) Unplanned disasters (power outage, tornadoes, etc.) High availability Plan for local (inside the datacenter) failures Disaster recovery Plan for regional (the datacenter is gone) failures

6 Definitions MTR: Mean Time to Recover CTR: Cost To Recover Tiers: Levels of Recovery Options

7 Helpful Hints Tier data Break data into tiers of different MTR commits Networking Plan how to get your network to fail with the data People Don t plan on people flying to remote sites Automate Automate as much of the failover as possible

8 Local High Availability

9 Local High Availability Features Standard clustering agents Solutions for non-cluster aware apps Stateful and non-stateful failover Failover and fail-back Product vendors Legato, Microsoft, Veritas, Steeleye, Linux Deployment scenarios Physical to virtual Virtual to virtual Poor man s

10 Physical to Virtual Clustering Primary Server MS Exchange Windows 2000 Shared disks, arrays or SAN storage ESX Server Failover Server MS Exchange Windows U, 2-way Rack File / Print Windows NT Data File / Print Windows NT 1U, 2-way Rack Intranet App Server on Windows 2000 Data Intranet App Server on Windows U, 2-way Rack Data 4U, 8-way Rackmount with ESX Server

11 Virtual to Virtual Clustering

12

13

14 Poor Man s Clustering ESX Server 1 ESX Server 2 VM1 VM3 VM2 ON Shared disks arrays, or SAN storage ON VM4 VM6 VM5 VM4 VM5 VM1 VM2 VM6 OFF VM1 VM2 VM3 OFF ON VM3 VM4 VM5 VM6 Dell 4-way Rackmount HP 4-way Rackmount

15 Local High Availability Considerations Cost MTR Number of virtual machines Disk space Benefits Out-of-the-box solution Stateful failover Inexpensive For any application

16 OS Based Solutions

17 OS Based Solutions Features Regular agents Very similar to physical environment Efficiencies from virtual machine architecture Product vendors Legato, Symantec, Veritas Deployment scenarios Physical to virtual Virtual to virtual Trunk of Car

18 Physical to Virtual Backup Server Tape Array

19 Virtual to Virtual Backup Server Tape Array

20 Trunk of Car

21 OS Based Solutions Considerations Cost Number of virtual machines Bandwidth Disk space Benefits Standard solution No learning curve Great reduction in agent cost

22 Host Based Solutions

23 Host Based Solutions Features Agent based, runs as a service File/byte level replication Synchronous and asynchronous Failover and fail-back Product Vendors Legato, NSI Double-Take, NeverFail, Mimix Deployment Scenarios Physical to virtual Virtual to virtual Multi-node

24

25

26

27

28

29 Virtual to Virtual Primary Site Failover Site

30 Virtual to Virtual Primary Site Failover Site

31 Virtual to Virtual Multi-Node Primary Site Failover Site

32 Virtual to Virtual Multi-Node Primary Site Failover Site

33 Virtual to Virtual Multi-Node Primary Site Failover Site

34 Host Based Solutions Considerations Cost Distance Number of virtual machines Bandwidth Benefits Out-of-the-box solution Maximum uptime Ease of use

35 SAN Based Solutions

36 SAN Based Solutions Features SAN layered applications LUN Snapshot Replication/Mirroring Block level replication Synchronous and asynchronous Products Vendors EMC, HP, IBM, Network Appliance Deployment Scenarios Physical to virtual Virtual to virtual Hybrid

37

38

39

40

41

42

43

44

45 SAN: Virtual to Virtual Host Agent For Replication and Failover Primary Site Failover Site

46 Hybrid Mode Backup Host Agent For Virtual Machine and Application Failover SAN Replication Primary Site Failover Site

47 SAN Based Solutions Considerations Cost Distance Bandwidth Downtime Complex configuration Benefits High performance Centralization Multiple working copies

48 Questions

49