For more information on Network Management, visit: http://www.solarwinds.com/network-management-software.aspx Watch this webcast: http://www.solarwinds.com/resources/webcasts/disaster-recovery-and-high-availability-concerns-within-your-network-and-systems-management-strategy.html Understanding the differences between disaster recovery and high availability and the design constraints of each is an important part of any systems architecture or design. During this webcast we’ll discuss these topics in details along with the unique requirements of network and systems managements systems and operations with respect to each. Some of the things that we’ll cover include: • Design considerations for highly available systems • Understanding disaster recovery planning • Design considerations for network and systems management • The impacts of DR/HA on network operations IT Management tools have transitioned over the years from nice-to-have, point solutions to mission critical applications. From VoIP to email to POS transactions, every IT system requires 24 X 7 robust management. Join us as we discuss the SolarWinds Orion Failover Engine and how it can help you maintain 100% Orion IT management coverage through a variety of outage situations.

2. A big “Howdy” from SolarWinds® based in Austin, Texas Josh Stephens, VP of Technology & Head Geek Dan Wendeln, Education and Certification Manager Today’s Topic: Disaster Recovery and High Availability Options as part of your Network Management Strategy Who is SolarWinds? What we do… Who are our customers? The SolarWinds community… Introduction

4. Understanding Disaster Recovery (DR) and High Availability (HA)

5. Design Considerations for High Availability

6. Disaster Recovery Planning

7. Network and System Management Design

8. Impacts of DR/HA on Network Operations

10. We only have an hour

11. No attendee left behind…

12. Ask questions!!!

13. Don’t be afraid to ask deeper questions

14. Don’t wait until the end – ask away

15. Today’s session is being recorded

16. Recorded session on SolarWinds.com

17. Slides available on slideshare.comJ0sher2014

19. Minimize downtime

20. Local system redundancy

21. Secondary system cut-over upon primary system failure

22. Self-healing systems

23. Disaster Recovery

24. Business Continuity

25. Remote site redundancy

26. Cut-over for worst case scenario

27. Not high availabilityJ0sher2014

29. Loss of network management means loosing

30. Visibility

31. Problem detection, alerting and reporting

32. SLA verification, Security

33. When the NMS is down, the entire network is in an unknown state!J0sher2014

35. Realistic goals allow obtainable results

36. System and service priorities

37. Critical, high, med, low

38. Method vs. Cost

39. Full HW/SW redundancy

40. HA systems

41. Clustering, virtualization, automatic movement, failoverJ0sher2014

43. Businesses rely on IT infrastructures

44. Allow for expected maintenance and system reliability

45. Minimize failure points

46. Lower costs

47. A failed network costs much more than a functioning networkJ0sher2014

49. Redundancy

50. Virtualization

51. System hardening

52. Measurement

53. Define and agree on goals

54. 99.999% only allows for 6 seconds/week!

55. Single system vs. aggregated goals

56. Verify and reportJ0sher2014

58. Business continuity post disaster

59. Increasing reliance on network services

60. Increased reliance on VPNs

61. Reliance on specific network expertiseJ0sher2014

63. Scenarios – types of disasters and failure points

64. Critical functions and requirements

65. Validation

66. DR Implementation Steps

67. Plan

68. Design

69. Implement

70. Test

71. Document – make sure DR Plan is accessible!J0sher2014

73. Database, OS, network, application

74. Personnel

75. Goals

76. Minimize NMS downtime

77. Minimize loss of data

78. Create seamless failover and recovery access

79. Maintain full functionality throughoutJ0sher2014

81. Example - DR priorities (goal)Business critical processes and applications (ability to continue business) Network and system management (ability to understand problems) System wide stability (allows business continuity) System wide recovery (return to normal) J0sher2014

82. Orion DR/HA The Orion Failover Engine Automatically switches Orion and modules to failover server Allows for HA - local failover or DR - remote site failover Capable of detecting application, system, processes and service health and triggering cutover automatically Available for all combinations of NPM, NPM components and additional pollers Failover server completely assumes the full identity and functionality of failed server including IP address and name Fast transition from failed primary server to failover server Automatic notifications of primary failure Failover and primary server are synchronized out-of-band Powered by Neverfail

83. Orion Failover

84. OrionFailover Deployment

85. OrionFailover Example

86. OrionFailover Example

87. OrionFailover Example

89. SQL failover

90. May already be built into your environment – check with your DBA

91. Also available directly from 3rd parties

92. Neverfail

93. Double-Take