Rie Irish @IrishSQL www.riepedia.net Director of Database Administration with Paymetric, Inc.  A single mom & lives with her teenage daughter just outside Atlanta, GA.  A SQL Server DBA for over 15 years in various industries: financial, pharmaceutical, eDiscovery, online commerce, government contracting and non-profits.  Helps run SQL Saturday Atlanta each year & is actively involved with the Atlanta MDF User Group.  Co-Leader PASS Women in Technology Virtual Group. Facilitates WIT Panels & speaks at SQL Saturdays on a variety of topics from encouraging young women to get involved in tech to helping women deal with interruptions in the boardroom. 

How to Create your Disaster Recovery Plan -Beginner Level Define what’s important.  Define RPO & RTO. Define stakeholders. Lay out plan for budgeting & building the infrastructure.  Building a Back Up Strategy. Building a Recovery Strategy. Failover Clusters, Availability Groups, Backups, Mirroring Mini disasters vs Full Blown disasters.

Knowing what’s important – before a disaster Defining what’s important. Defining RTO & RPO. What’s your budget? Who is responsible to declaring a disaster? Who is responsible the actual recovery work? Does everyone understand the role they’ll play?

RTO & RPO The recovery time objective (RTO) is the targeted duration of time and a service level within which a business process must be restored after a disaster (or disruption) in order to avoid unacceptable consequences associated with a break in business continuity. The recovery point objective (RPO) is the age of files that must be recovered from backup storage for normal operations to resume if a computer, system, or network goes down as a result of a hardware, program, or communications failure.

Recovery point objective how much data can you lose? This answer will vary across the business: minutes, hours to days. Execs & legal can help define this. Often, there are contractual obligations to external clients. Sometimes rebuilding is easier than restoring.

Who are my stakeholders? You stakeholders are defined as the people who can answer all the questions we’re asking today. In most cases, this starts with C-level Execs. They have to answer to the Board after a Disaster. They’ll also be the people that have to pay for it. Who is affected by data loss or system outage? Application Owners Business Users Clients (Internal & External)

Building a backup strategy

Building your restore strategy Any DBA is only as good as their last restore

Failover Clusters, Availability Groups, Backups, Mirroring

Mini disasters vs Full Blown disasters

How to Create Your Disaster Recovery Plan So your boss asked for a copy of your DR plan.  Once you've wiped that deer-in-the-headlights look off your face, you realize "We've got database backups," isn't exactly a plan.  You need to come up with a plan to recover your business when disaster strikes. This session will help you build this plan by defining what a disaster could be, documenting the business impact, and identifying your limitations.  We will show how to use this information to establish metrics (such as RTO and RPO), document current recovery configurations, and design an effective recovery strategy that meets the needs and budget of your business. Attending this session will give you the knowledge and tools to create an effective disaster recovery plan that will make your boss happy and ensure the continuity of your business. I will give you my DR template that you can use to get started with documenting your DR plan.