Disaster Recovery and High Availability Concerns within Your Network & Systems Management Strategy

1,898 views

Published on

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.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,898
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Disaster Recovery and High Availability Concerns within Your Network & Systems Management Strategy

  1. 1.
  2. 2. A big “Howdy” from SolarWinds®<br /> based in Austin, Texas<br />Josh Stephens, VP of Technology & Head Geek<br />Dan Wendeln, Education and Certification Manager <br />Today’s Topic: <br /> Disaster Recovery and High Availability<br /> Options as part of your Network <br /> Management Strategy<br />Who is SolarWinds?<br />What we do…<br />Who are our customers?<br />The SolarWinds community…<br />Introduction<br />
  3. 3. Agenda<br /><ul><li>Introductions & Housekeeping
  4. 4. Understanding Disaster Recovery (DR) and High Availability (HA)
  5. 5. Design Considerations for High Availability
  6. 6. Disaster Recovery Planning
  7. 7. Network and System Management Design
  8. 8. Impacts of DR/HA on Network Operations
  9. 9. Summary and Q&A</li></li></ul><li>A Few Notes about Today’s Session<br /><ul><li>Today’s content will be fairly high-level
  10. 10. We only have an hour
  11. 11. No attendee left behind…
  12. 12. Ask questions!!!
  13. 13. Don’t be afraid to ask deeper questions
  14. 14. Don’t wait until the end – ask away
  15. 15. Today’s session is being recorded
  16. 16. Recorded session on SolarWinds.com
  17. 17. Slides available on slideshare.com</li></ul>J0sher2014<br />
  18. 18. High Availability and Disaster Recovery<br /><ul><li>High Availability
  19. 19. Minimize downtime
  20. 20. Local system redundancy
  21. 21. Secondary system cut-over upon primary system failure
  22. 22. Self-healing systems
  23. 23. Disaster Recovery
  24. 24. Business Continuity
  25. 25. Remote site redundancy
  26. 26. Cut-over for worst case scenario
  27. 27. Not high availability</li></ul>J0sher2014<br />
  28. 28. HA/DR and Network Management<br /><ul><li>Network and Systems management are business critical
  29. 29. Loss of network management means loosing
  30. 30. Visibility
  31. 31. Problem detection, alerting and reporting
  32. 32. SLA verification, Security
  33. 33. When the NMS is down, the entire network is in an unknown state!</li></ul>J0sher2014<br />
  34. 34. Design Considerations for High Availability<br /><ul><li>Goals drive requirements and resources
  35. 35. Realistic goals allow obtainable results
  36. 36. System and service priorities
  37. 37. Critical, high, med, low
  38. 38. Method vs. Cost
  39. 39. Full HW/SW redundancy
  40. 40. HA systems
  41. 41. Clustering, virtualization, automatic movement, failover</li></ul>J0sher2014<br />
  42. 42. High Availability<br /><ul><li>Drivers
  43. 43. Businesses rely on IT infrastructures
  44. 44. Allow for expected maintenance and system reliability
  45. 45. Minimize failure points
  46. 46. Lower costs
  47. 47. A failed network costs much more than a functioning network</li></ul>J0sher2014<br />
  48. 48. High Availability<br /><ul><li>Methods
  49. 49. Redundancy
  50. 50. Virtualization
  51. 51. System hardening
  52. 52. Measurement
  53. 53. Define and agree on goals
  54. 54. 99.999% only allows for 6 seconds/week!
  55. 55. Single system vs. aggregated goals
  56. 56. Verify and report</li></ul>J0sher2014<br />
  57. 57. Disaster Recovery<br /><ul><li>Drivers
  58. 58. Business continuity post disaster
  59. 59. Increasing reliance on network services
  60. 60. Increased reliance on VPNs
  61. 61. Reliance on specific network expertise</li></ul>J0sher2014<br />
  62. 62. Disaster Recovery and Planning<br /><ul><li>Planning Considerations
  63. 63. Scenarios – types of disasters and failure points
  64. 64. Critical functions and requirements
  65. 65. Validation
  66. 66. DR Implementation Steps
  67. 67. Plan
  68. 68. Design
  69. 69. Implement
  70. 70. Test
  71. 71. Document – make sure DR Plan is accessible!</li></ul>J0sher2014<br />
  72. 72. Disaster Recovery and Network Management<br /><ul><li>Considerations
  73. 73. Database, OS, network, application
  74. 74. Personnel
  75. 75. Goals
  76. 76. Minimize NMS downtime
  77. 77. Minimize loss of data
  78. 78. Create seamless failover and recovery access
  79. 79. Maintain full functionality throughout</li></ul>J0sher2014<br />
  80. 80. Disaster Recovery and Network Management<br /><ul><li>Network management and the DR plan
  81. 81. Example - DR priorities (goal)</li></ul>Business critical processes and applications (ability to continue business)<br />Network and system management (ability to understand problems)<br />System wide stability (allows business continuity)<br />System wide recovery (return to normal)<br />J0sher2014<br />
  82. 82. Orion DR/HA<br />The Orion Failover Engine<br />Automatically switches Orion and modules to failover server<br />Allows for HA - local failover or DR - remote site failover<br />Capable of detecting application, system, processes and service health and triggering cutover automatically<br />Available for all combinations of NPM, NPM components and additional pollers<br />Failover server completely assumes the full identity and functionality of failed server including IP address and name<br />Fast transition from failed primary server to failover server<br />Automatic notifications of primary failure<br />Failover and primary server are synchronized out-of-band<br />Powered by Neverfail<br />
  83. 83. Orion Failover <br />
  84. 84. OrionFailover Deployment <br />
  85. 85. OrionFailover Example <br />
  86. 86. OrionFailover Example <br />
  87. 87. OrionFailover Example <br />
  88. 88. Orion Failover Engine<br /><ul><li>Available immediately
  89. 89. SQL failover
  90. 90. May already be built into your environment – check with your DBA
  91. 91. Also available directly from 3rd parties
  92. 92. Neverfail
  93. 93. Double-Take
  94. 94. MS SQL Clustering, Log shipping</li></li></ul><li>Summary and Q&A<br />Thank you for attending!<br />To learn more or to download free 30-day trials<br />of SolarWinds products visit:<br />www.SolarWinds.com<br />Contact information<br />Josh Stephens, Head Geek<br />headgeek@solarwinds.com<br />twitter: sw_headgeek<br />Blog: http://solarwinds.com/geek<br />p.s. Remember to renew your maintenance!!!<br />

×