Ultan Kinahan

1. Disaster Recovery PlanningAre you covered? Minasi internet Meeting 2010 Ultan Kinahan kinahan@live.com

3. Born & Raised in Ireland & moved states side in 1992 the week after I finished college & started working in a bar in Greenwich Village NYC… Landed first role in IT here in late ‘92

4. Currently;

5. Regional IT Director of Brown & Brown Insurance Co.

6. Previous roles included:

7. AOL – “Mapquest, Digital City & Moviefone”

8. Network Admin for a realty firm in NYC

10. A disaster is an unplanned event that interrupts normal business operations.

11. Types of events

12. “Acts of God”

13. Floods

14. Earthquakes

15. Volcano's

16. Snow Storms

17. etc.

18. Man Made

20. Business Continuity

21. Disaster Recovery

22. Recovery Time Objective (RTO)

23. The target time for making an application available

24. Recovery Point Objective (RPO)

25. The age of the data recovered

26. Data Center

28. RM (Risk Management) drives BCP (Business Continuity Planning)

29. BCP (Business Continuity Planning) drives DRP (Disaster Recovery Planning)

31. Is the creation and validation of a practiced logistical plan for how an organization will recover and restore partially or completely interrupted critical (urgent) functions within a predetermined time after a disaster or extended disruption. The logistical plan is called a business continuity plan.

32. In plain language

34. According to the report, 93% of organizations have had to execute their DR Plans and the average cost:

35. USA: $287,000

36. Canada: $496,500

37. The average budget for disaster recovery initiatives worldwideis $50 million USD – Not a lot really!

38. Average time it takes to "achieve skeleton operations after an outage" is 3hours.

40. In 2007, 55% of respondents reported DR committees involved the CIO, CTO or IT director

41. this dropped to 33 per cent in 2008

42. The number rose to 67 per cent in 2009

43. DR "becoming a competitive differentiator“ within organizations – especially in the financial sector

45. Recover systems based on a timeline as defined by an Internal Audit of operations

46. IT Infrastructure (12-24 hours)

47. Processing System (24-48 hours)

48. Email (4 days)

50. Internal Audits are one of the best options.

51. Typical findings;

52. Financials (accounts receivables, accounts payable, etc)

53. HR/Payroll (Payroll, Benefits processing, etc)

55. Servers

56. Desktops

57. Laptops

58. Networking Gear

59. Data Lines

60. Software

61. Home Grown Apps

62. Vendor Based Apps

63. Vendor Contact List

65. CD’s, DVD’s

66. USB Sticks or Drives

67. Tape

68. Disk

69. Local Replication

70. Other Options

71. Application Replication (Local site or Site to Site)

72. Site to Site Replication (Branch site or Colocation)

73. Cloud Storage or hosted applications

75. Purchase new storage, servers, software, licensing etc.

76. Can you use existing (non-production) systems at a second data center?

77. Data lines

78. Configuration of servers, software & storage

79. Setup external access ports for failover

80. MX Records, Terminal Server, Citrix, VPN etc.

82. The provider. In most cases with your standard T1 at 1.5MB your lucky to get 1.3MB then you have…

83. The asynchronous replication engine is often based on a protocol, protocol converter

84. Application running on top of IP or TCP

85. Transport protocol overhead

87. Low CPU Overhead

88. Defined Memory and Disk Usage

89. Write Order Intact Replication

90. Bandwidth Friendly Data Movement

91. User-definable Replication Sets

92. Compression, Scheduling, Scheduled Bandwidth Throttling capabilities

93. Point-in-Time Recovery

95. Detect Failure in Seconds or Minutes

96. Users can reconnect within minutes of failure

97. Failover can occur across a LAN, WAN and even NAT

98. Failover more than one Server Identity to the Same Target Server

100. Bring Source Application Online

101. Users Reconnect Within Minutes

102. Recover or Replace Source Server

103. Restore Data to the Source Server

105. Reduced recovery infrastructure requirements

106. Fewer hours spent creating and maintaining DR plans and processes

107. Significantly reduced cost of DR tests; eliminates IT staff overtime and application impact

108. Recovery in a matter of hours, not days or weeks – greatly reducing the financial exposure a company faces during a major outage

109. The following captures an estimate of the cost savings provided by SRM when used to recover from a major outage or disasterCompany that does $25M in revenue a year = ~$96k/weekday. Assume that SRM can achieve RTO of 12 hours instead of 72 hours compared to traditional DR plan. Value of Lost Revenue Value of Lost Time by Workers $96,153 2.5 X + 500 2.5 = X $300/day X X $ 615,385(per disaster) X Days of faster recovery Number of workers Lost revenue per workday Days of faster recovery Cost of worker wages

111. Raise alert when heartbeat lost

112. Initiate failover

113. User confirmation of outage

114. Granular failover initiation

115. Manage replication failover

116. Break replication

117. Make replica visible to recovery hosts

118. Execute recovery process

119. Use pre-programmed plan

121. According to Symantec’s annual Global IT Disaster Recovery survey One in four DR tests fail. This marks an improvement, however, when compared to previous years.

122. In 2007, 50% of DR tests failed

123. In 2008, 30% of DR tests failed

124. and 25% in 2009