IT Outsourcing: Business Continuity by Design by OneNeck IT Services

348 views
275 views

Published on

OneNeck provides a comprehensive, flexible suite of IT outsourcing solutions designed specifically for mid-market companies. Visit http://www.oneneck.com/ today.

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

No Downloads
Views
Total views
348
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • Focus on 100% referenceability … how hard we work on this … our management principle #1 is “it is OK to lose money but never a reference” … if we do not think that a prospect will be reference, we will most probably pass on the opportunity Private but very open … OEF and follow ups.
  • IT Outsourcing: Business Continuity by Design by OneNeck IT Services

    1. 1.
    2. 2. Dynamics AX: IT Outsourcing Experts <ul><li>Founded in 1997 </li></ul><ul><li>Supports over 50 customers at over 850 sites worldwide </li></ul><ul><li>99% Contract Renewal Rate exceeding the industry average of 85% </li></ul><ul><li>Primary data center/support center operations in Phoenix and Houston </li></ul><ul><li>100% US based operations and employees </li></ul><ul><li>Diverse staff of Dynamics AX certified professionals </li></ul><ul><li>Average of 99.9% systems availability </li></ul><ul><li>Supports multi-site deployments for two of the largest hosted Dynamics AX environments in North America </li></ul><ul><li>Ranked #1 ERP Outsourcing Vendor by the Black Book of Outsourcing </li></ul>OneNeck provides a comprehensive , flexible suite of IT outsourcing solutions designed specifically for mid-market companies Introducing OneNeck
    3. 3. IT Outsourcing: Business Continuity by Design Michael Ayers Senior Systems Engineer OneNeck IT Services
    4. 4. Business Continuity by Design <ul><li>Business Continuity </li></ul><ul><li>Continuity By Design </li></ul><ul><ul><li>System Design </li></ul></ul><ul><ul><li>Application Design </li></ul></ul><ul><ul><li>Network Infrastructure Design </li></ul></ul><ul><li>Summary </li></ul><ul><li>Questions and Answers </li></ul>Agenda
    5. 5. Business Continuity
    6. 6. Business Continuity <ul><li>Business continuity (continuance) and business continuity planning (BCP) are those steps an organization takes to ensure that essential business functions can continue during and after a service failure </li></ul><ul><li>The main goals of BCP </li></ul><ul><ul><li>Prevent interruption of mission-critical services </li></ul></ul><ul><ul><li>Return mission-critical services to operation quickly and efficiently </li></ul></ul><ul><ul><li>Minimize the loss of data in the event of a service failure </li></ul></ul><ul><li>Put in simpler terms: </li></ul><ul><ul><li>BCP attempts to minimize the financial impact caused by failure of a mission-critical service </li></ul></ul>What is Business Continuity?
    7. 7. Business Continuity <ul><li>Which applications would you classify as mission or business critical? </li></ul><ul><li>Email </li></ul><ul><li>ERP system </li></ul><ul><li>B2B (EDI) Transactions </li></ul><ul><li>B2B/B2C site </li></ul>Survey
    8. 8. Business Continuity <ul><li>Analysis </li></ul><ul><li>Design </li></ul><ul><li>Implementation </li></ul><ul><li>Test and acceptance </li></ul><ul><li>Maintenance </li></ul>The BCP Lifecycle
    9. 9. Business Continuity <ul><li>Business Impact Analysis </li></ul><ul><ul><li>Helps define critical and non-critical systems </li></ul></ul><ul><ul><li>Identifies critical system recovery times </li></ul></ul><ul><ul><li>Identifies critical system recovery requirements </li></ul></ul><ul><li>Risk Analysis </li></ul><ul><ul><li>Identifies how likely certain disasters are to happen to critical systems </li></ul></ul><ul><ul><li>Plan for the most extreme possibility </li></ul></ul><ul><li>Impact Scenarios </li></ul><ul><ul><li>A definition of those events that will likely cause a critical system failure </li></ul></ul><ul><li>Recovery Requirement Document </li></ul><ul><ul><li>A statement for each critical system </li></ul></ul><ul><ul><li>Defines “What” recovery means </li></ul></ul><ul><ul><li>Defines the maximum acceptable system outage </li></ul></ul>Analysis
    10. 10. Business Continuity <ul><li>Identify the most cost-effective recovery solution </li></ul><ul><ul><li>To restore the minimum usable system and data </li></ul></ul><ul><ul><li>Within the identified recovery time frame </li></ul></ul>Design
    11. 11. Business Continuity <ul><li>To execute the design </li></ul><ul><ul><li>May include initial functional testing of the design </li></ul></ul><ul><ul><li>Provides feedback to the design process </li></ul></ul>Implementation
    12. 12. Business Continuity <ul><li>To validate the design </li></ul><ul><li>To test the failure from primary to secondary system </li></ul><ul><ul><li>Test the declaration of continuity business processes </li></ul></ul><ul><ul><li>Test the system restore procedures </li></ul></ul><ul><li>To test the function of the secondary system </li></ul><ul><ul><li>Validate system availability </li></ul></ul><ul><ul><li>Validate data accuracy and completeness </li></ul></ul><ul><li>To test the return to primary from secondary system </li></ul><ul><ul><li>Test the return to operations procedure </li></ul></ul>Testing
    13. 13. Business Continuity <ul><li>Periodic validation of the design </li></ul><ul><ul><li>Documentation of changes to the system </li></ul></ul><ul><ul><li>Analysis of the changes to the design </li></ul></ul><ul><ul><li>Regular testing of the design </li></ul></ul><ul><ul><li>Employee awareness training </li></ul></ul>Maintenance
    14. 14. Continuity By Design
    15. 15. Continuity by Design <ul><li>Design Goals </li></ul><ul><li>Design Considerations </li></ul><ul><li>Many risks can be mitigated by thoughtful design </li></ul><ul><ul><li>System Design </li></ul></ul><ul><ul><li>Application Design </li></ul></ul><ul><ul><li>Network Design </li></ul></ul><ul><ul><li>DR Design </li></ul></ul>Continuity by Design
    16. 16. Continuity by Design <ul><li>System Recovery </li></ul><ul><ul><li>What is the minimum requirement that defines system availability? </li></ul></ul><ul><li>Recovery Point Objective (RPO) </li></ul><ul><ul><li>The point in time that recovered systems can be restored to </li></ul></ul><ul><ul><li>Is the backup from the night before last good enough? </li></ul></ul><ul><li>Recovery Time Objective (RTO) </li></ul><ul><ul><li>The amount of time it takes to return the system to operation </li></ul></ul><ul><ul><li>How long to procure a location and systems </li></ul></ul><ul><ul><li>How long to receive and restore tapes? </li></ul></ul>Design Goals
    17. 17. Continuity by Design <ul><li>System Recovery </li></ul><ul><ul><li>What is the minimum requirement that defines system availability? </li></ul></ul><ul><ul><li>A recovered system may not need to be as large as the primary system </li></ul></ul><ul><li>Recovery Point Objective (RPO) </li></ul><ul><ul><li>The point in time that a DR systems can be restored to </li></ul></ul><ul><ul><li>Is the backup from the night before last good enough? </li></ul></ul><ul><ul><li>Traditional RPO is 24-48 hours </li></ul></ul><ul><ul><li>The Lower the RPO, the higher the cost </li></ul></ul><ul><li>Recovery Time Objective (RTO) </li></ul><ul><ul><li>The amount of time it takes to return the system to operation </li></ul></ul><ul><ul><li>How long to procure a location and systems </li></ul></ul><ul><ul><li>How long to receive and restore tapes? </li></ul></ul><ul><ul><li>Traditional RTO can be 72 hours and up </li></ul></ul><ul><ul><li>The lower the RTO, the higher the cost </li></ul></ul>Design Considerations
    18. 18. Continuity by Design <ul><li>Use tier 1 hardware providers </li></ul><ul><ul><li>Consistent hardware in chassis </li></ul></ul><ul><ul><li>Support contracts available </li></ul></ul><ul><ul><li>Continually updated drivers </li></ul></ul><ul><ul><li>The TCO is less when considering management implications </li></ul></ul><ul><li>Design system fault tolerances </li></ul><ul><ul><li>Redundant Power supplies </li></ul></ul><ul><ul><ul><li>supplied through separate circuits </li></ul></ul></ul><ul><ul><ul><li>Uninterruptible power supplies </li></ul></ul></ul><ul><ul><li>Redundant Hard Disks </li></ul></ul><ul><ul><ul><li>RAID </li></ul></ul></ul><ul><ul><ul><li>SAN disk </li></ul></ul></ul><ul><ul><li>Alternative system restore utilities </li></ul></ul><ul><ul><ul><li>System Imaging </li></ul></ul></ul><ul><ul><ul><li>Virtualization technologies </li></ul></ul></ul>System Design
    19. 19. Continuity by Design <ul><li>Keep Operating Systems up to date </li></ul><ul><ul><li>Plan for operating system upgrades </li></ul></ul><ul><ul><li>Maintain current service-pack levels </li></ul></ul><ul><ul><li>Automate critical update processes </li></ul></ul><ul><li>Deploy anti-virus solutions </li></ul><ul><ul><li>Automate signature updates to all systems </li></ul></ul><ul><ul><li>Deploy separate vendors at mail server and Internet gateway </li></ul></ul><ul><li>Maintain application currency </li></ul><ul><ul><li>Automate updates to critical applications </li></ul></ul><ul><ul><li>Plan to install the most current version of applications </li></ul></ul>Application Design
    20. 20. Continuity by Design <ul><li>Design with backup and recovery in mind </li></ul><ul><ul><li>Deploy redundant infrastructure services (AD, DNS, Etc) </li></ul></ul><ul><ul><li>Deploy DFS for file management and backup </li></ul></ul><ul><ul><ul><li>Replicate DFS shares to datacenter (for backup) </li></ul></ul></ul><ul><li>Deploy applications where they are needed </li></ul><ul><ul><li>Centralize key applications like ERP, monitoring, Exchange </li></ul></ul><ul><ul><li>Locate file, print, and infrastructure services near user community </li></ul></ul><ul><ul><li>Appliances can present or virtualized services locally </li></ul></ul><ul><li>Clustering/Load balancing </li></ul>Application Design
    21. 21. Continuity by Design <ul><li>Use tier 1, business-class LAN/WAN hardware </li></ul><ul><ul><li>Designed to handle the data rates that business require </li></ul></ul><ul><ul><li>R&D produces superior products </li></ul></ul><ul><ul><li>Up-to-date on current technologies </li></ul></ul><ul><ul><li>Patched and tested for security </li></ul></ul><ul><li>Leverage current, right-sized networking hardware </li></ul><ul><ul><li>Newest technologies supported </li></ul></ul><ul><ul><li>Faster hardware </li></ul></ul><ul><ul><li>Latest security methodologies </li></ul></ul><ul><ul><li>Provides options for hardware redundancy </li></ul></ul><ul><li>Leverage WAN acceleration technologies </li></ul><ul><ul><li>Can replace local infrastructure services </li></ul></ul><ul><ul><li>Optimizes WAN bandwidth </li></ul></ul><ul><ul><li>Provides additional networking services opportunities </li></ul></ul>Network Design
    22. 22. Continuity by Design <ul><li>Leverage Current WAN Technology (MPLS) </li></ul><ul><ul><li>Offers fully meshed WAN topologies </li></ul></ul><ul><ul><li>Support for newer technologies like QoS </li></ul></ul><ul><ul><li>Built-in redundancy within the provider’s network </li></ul></ul><ul><li>Leverage the Internet with VPN failover </li></ul><ul><ul><li>Provides a redundant path to mission-critical applications </li></ul></ul><ul><ul><li>Can remove Internet traffic from the WAN </li></ul></ul>Network Design
    23. 23. Continuity by Design <ul><li>Design for multiple DR options </li></ul><ul><ul><li>Implement virtualization technologies </li></ul></ul><ul><ul><li>Implement replication technologies </li></ul></ul><ul><ul><li>Implement WAN Acceleration technologies </li></ul></ul><ul><ul><li>Implement an Internet VPN solution </li></ul></ul>DR Design
    24. 24. Business Continuity by Design <ul><li>BCP attempts to minimize the financial impact caused by failure of a mission-critical service </li></ul><ul><li>Proper design comes from a thorough business impact analysis </li></ul><ul><li>The lower the RPO and RTO, the higher the cost (traditionally) </li></ul><ul><li>Many risks can be mitigated by thoughtful design </li></ul><ul><li>Business continuity and DR planning is nothing more than insurance </li></ul>Summary
    25. 25. Business Continuity by Design <ul><li>Question/Comments </li></ul>Q&A

    ×