7 steps to
smarter backup
Speaker
Title
Date
Disaster-proof
your business.
Cut costly downtime.
4.6M instances of data loss,
every year.
18.5 hours to recover on average.
Downtime costs $5,600 each
minute.
US TechWench All Things Tech
Gartner Data Center Conference
3. Ponemon Institute
1.
2.
Can you fully restore critical systems
with current strategies and technology?
ONLY
28%
Very confident
72%
Less than confident
Forrester Research 2014
1 out of 5
recoveries
FAIL.
ESG; “The Modernization of Data Protection”, 2013
Step 1
Know your risks
Top causes of downtime are mundane events, not disasters
Operational failures
Natural disasters
Human-caused events
43%
31%
16%
15%
12%
10%
13%
9%
4%
1%
3%
1%
1%
Base: 94 global disaster recovery decision-makers and influencers (does not include “don’t know” responses; multiple responses accepted) Source:
Forrester/Disaster Recovery Journal November 2013 Global Disaster Recovery Preparedness Online Survey
1%
5%
Perform a risk assessment.
 Inventory your assets
 Assess your threats
 Analyze the impact of each incident
Step 2
Know your data
Not all data is the same.
Static
Business vital
Does not change over time
Is vital to the daily operations of
the business
Mission
critical
If lost or unavailable – even for
short periods of time – damage
will occur
Define your application criticality.
 Speak to your business stakeholders
 Group your applications and data
 Simplify, 3 to 5 groupings are enough
Examples of an inventory, risk assessment, and classification.
Location
SFO-1
Location
SFO-01
Server/VM
Orcl-001
OS and hypervisor
RHEL 5.x
Exch-001
Win 2012 r2
Exch-002
MOSS-001
SQL-001
SQL-002
SQL-003
SQL-004
AD-001
Win 2012 r2
Win 2012 r2
Win 2012 r2
Win 2012 r2
Win 2012 r2
Win 2012 r2
Win 2012 r2
Assets
Application
Oracle 11g
Exchange 2013
(DAG1)
Exchange 2013
(DAG2)
SharePoint 2010
SQL Server 2008
SQL Server 2008
SQL Server 2008
SQL Server 2008
AD Domain Controller
IP address
10.10.10.1
Disk allocated Disk used
5 TB
1 TB
Dependencies
10.10.10.2
20 TB
7 TB
Exch-002
10.10.10.3
10.10.10.4
10.10.10.5
10.10.10.6
10.10.10.7
10.10.10.8
10.10.10.9
20 TB
10 TB
5 TB
5 TB
5 TB
5 TB
3 TB
7 TB
8 TB
3 TB
2 TB
2 TB
2 TB
1 TB
Exch-001
SQL-01, SQL-02
Threat (internal and external)
Natural disaster - Earthquake
Orcl-001, Exch-001, SQL-001, SQLNetwork failure
002,SQL-003, SQL-004, SQL-005, FLS-001
Power failure
Probability
Low
Medium
High
Impact
High
Medium
High
Class
Description
Low impact
All data and systems that are needed to achieve the business’ strategic objectives, but does not need to be
immediately restored for the business to continue to operate.
Moderate impact
All data and systems that are important to the achieving business objectives. The business can operate but in a
diminished state.
High impact
All data and systems that are critical to the business operations. Business comes to halt without the associated
services.
Step 3
Know your goals
Set objectives for each data set.
 How much downtime can you tolerate?
 How much data can you afford to lose?
 How long do you need to retain data?
Map your recovery process.
RETENTIONS
Operating System
Recovered
Data Available
Operating System
Recovered
Disaster
Application Downtime
Hourly
Retention Time
RESTORE,
RECOVER,
RESTART
Data
Loss
Application Data
Main
BC Site
Daily
Weekly
DR Near
Line
Monthly
DR Offline
More
Fewer
Frequency of Retentions
TIMELINE
Data
RPO
Disaster
Occurs
O.S.
RTO
Application
RTO
Source: Cloud and Virtual Data Storage Networking (CRC)
Step 4
Know your tools
Review your capabilities.
 File and folder-based backups
 Image-based snapshots
 Deduplication and replication
 Single item recovery and virtual standby
Build a defense-in-depth.
Secondary Site
Tiered/Slow
Disk
Tiered Disk
 Replication
Backup Replication
Backup
Replica
Access
Backup
Copies
Standby
 Offsite/cloud
Selective Data-set
Virtual
 Local backup
Cloud
Asynchronous Replication
Near
Real-time
 Snapshots
Primary Site
Data Analytics
Off-site
Tape
Step 5
Build an off-site plan
Second sites: Cold, warm, or hot?
 Is off-site tape storage enough?
 Failover and load-balancing
 Duplicate the primary, or scale down?
 Cloud, DRaaS and virtual standby options
Data
readiness, is
not just
retention.
Physical Server
Identical
Hardware
Dissimilar
Hardware
Virtual Machine
SAN/NAS
Cloud
Backup
Server
Bare
Metal
Restore
Virtual
Standby
Step 6
Document your plan
Get buy-in and win confidence.
 Involve stakeholders across the business
 Clearly outline IT SLAs in case of failure
 Detail what to do before you need to
A plan is nothing.
Planning is everything.
Step 7
Challenge your plan
Test your defenses in layers.
Class
Description
Frequency
Walk-thru exercise
Review the layout on contents of your DR plan
As often as necessary to familiarize response teams and
individuals with a documented plan or changes to a plan
Tabletop exercise
Using a scenario, discuss the response and recovery
activities of a documented plan
At least 4 times per year, or any time a change is made to
the business or IT operating environment.
Physically exercise a component of a DR plan (e.g. testing
automated communications services or work-from-home
Component exercise capabilities together with IT or partner capabilities)
Using a scenario, carry out the response and recovery
Full-scale simulation activities of a DR plan the entire organization
Classification
Low impact
Moderate impact
High impact
Application
Filesystem
SharePoint, Active Directory
Exchange, Oracle
At least twice per year or when a change is made to the
business or IT operating environment
At least once or twice per year or when a change is made
to the business or IT operating environment
Server/VM
FLS-001
MOSS-001, AD-001, SQL-001, SQL-002
Exch-001, Orcl-001
RTO
24 hrs
12 hrs
1 hr
RPO
24 hrs
12 hrs
10 min
Your plan is alive.
 Test, test, and test again
 Automate testing to add coverage
 Build backup into the IT planning cycle
Stay protected.
Questions?
Session Feedback
1. Select your session
from the agenda.
2. Click the survey
button.
3. Rate your session & submit.