Brian Frank, Sr. Manager of Technical Delivery at HOSTING, and Melissa Schultz, Project Manager at HOSTING, will be discussing why your organization needs to invest in disaster recovery solutions and how to do it. He will cover: -DR and business continuity -Key considerations for business continuity -Preparing for disasters -DR testing -How to implement your DR plan and run book

1. 1
Protecting Against Disaster:
Plan for the inevitable before it happens.

2. • This webinar is being recorded and an on-demand
version will be available at the same URL at the
conclusion of the webinar
• Please submit questions via the button on the upper left
of the viewer
• If we don’t get to your question during the webinar,
we will follow up with you via email
• Download related resources via the “Attachments”
button above the viewing panel
• On Twitter? Join the conversation: @HOSTINGdotcom
2
Housekeeping

3. 3
Introduction
Brian Frank, Sr. Manager of
Technical Delivery at HOSTING
• 10 Years experience in designing, building and
maintaining high performance cloud solutions
• At HOSTING since 2011
• Implemented over 300 Disaster Recovery
Solutions
Melissa Schultz, Project Manager at
HOSTING

4. 4
Why invest in DR?
• 75% of companies believe
their DR plans are
inadequate
• 40% of businesses do
not reopen after a
disaster and another
25% fail within one year
according to the Federal
Emergency Management
Agency (FEMA)

5. Business Continuity
5

6. • Business continuity encompasses a loosely
defined set of plans that ensure an
organization’s business functions will continue
to operate and withstand critical incidents and
disasters
vs.
• Disaster recovery is part of business continuity
6
DR vs. Business Continuity: What’s
the Difference?

7. 7
Key Considerations for Business
Continuity
• What level of resilience are you building your
production environment to?
• Completed Risk Assessment
• List of high-value assets
• RPO (Recovery Point Objective)
• RTO (Recovery Time Objective)
• What are your application dependencies
• Do you have any recent organizational/IT changes

8. • According to
Timesavers
International studies,
the catastrophe most
businesses
experience is not fire,
flood or earthquake,
but rather something
much more insidious
– malware
8
Key Considerations for your Risk
Assessment

9. 9
Preparing for Disasters: Key
Questions to Ask
• What constitutes a disaster for your company?
• What business factors are going to cause the need to
re-evaluate DR?

10. • Build a run book:
• How do we declare a disaster?
• What order will we need to bring our applications/services
online?
• What steps do I need to take inside my servers once they
are online in recovery to make them function?
• Common mistakes that companies make in their
disaster recovery (DR) efforts:
• Planning for DR when designing the production solution
• Lack of testing
• Neglecting to consider how users will connect to the
recovery location
10
Essential Pieces of Business Continuity

11. Preparing for a Disaster
11

12. • How will your servers
connect to the
network at the
recovery location?
• How will your users
connect to the
applications at the
recovery location?
12
Network Connectivity Considerations

13. • Every DR solution must have a run
book
• This is a playbook that walks through what
happens in the event of a disaster with a step
by step scenario
• Possible compliance/audit or insurance
requirements for your business to have
runbook
13
Run Book!

14. 14
Frequency of Disaster Recovery Testing
• How often have you tested your solution?
• Depending on regulations/requirements, testing
may take place once a year or up to 4 times a
year.
• DR exercises may take a few attempts
depending on the complexity of your solutions

15. • Failover Test:
• Process of completely failing over a recovery
plan with the intention of testing. There is
nothing wrong at the production location.
• Disaster Recovery Site Test:
• Very similar to a failover test with the only
difference being that the production site
remains the “system of record”, meaning that
the production stays up and running for
production users.
15
Failover Test vs. Disaster Recovery
Site Test

16. Declaring a Disaster
16

17. 17
Steps for Declaring a Disaster – The
first 24 hours
1. Determine degree of disaster
2. Notify senior management
3. Notify your disaster recovery team
4. Notify users of the disruption of service
5. Notify HOSTING
6. Implement Disaster Recovery Plan
7. Contact external vendor/contacts
(software)

18. HOSTING DR AS A SERVICE (DRAAS)
18

19.  Full White Glove Service
 HOSTING implements entire solution end-to-end and
guides your team through a successful recovery
exercise
 DRaaS
 Live synchronization with HOSTING through reliable
data replication, powered by Zerto
 Completely managed
19
HOSTING DR

20. •Pre-Build
•10 DaysPhase 1
•Configuration
•30 DaysPhase 2
•Documentation
•3 DaysPhase 3
•Exercise
•14 DaysPhase 4
•Project CompletePhase 5
PHASED DELIVERY PROCESS
Average Delivery less than 3 months from signature to
proven DR solution
Phase 1 starts at Customer Implementation Kickoff call
Environment Assumptions
• < 40 VMs
• < 5 TB of Storage
• ≥ 75 Mbps available bandwidth at production site

21. 21
Q&A
For more information about DR solutions by HOSTING, please contact our
team at 888.894.4678.
Brian Frank, Sr. Manager of Technical
Delivery at HOSTING