7 steps to smarter backup Speaker Title Date

Disaster-proof your business. Cut costly downtime.

4.6M instances of data loss, every year hours to recover on average. Downtime costs $5,600 each minute. 1. US TechWench All Things Tech 2. Gartner Data Center Conference 3. Ponemon Institute

Can you fully restore critical systems with current strategies and technology? 72% 28% Less than confidentVery confident Forrester Research 2014 ONLY

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 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 Power failure IT hardware failureNetwork failureIT software failureHurricaneFloodWinter stormFireEarthquakeHuman error Security malicious outsider Malicious insiderChemical spillTerrorismOther Operational failuresNatural disastersHuman-caused events 43% 31% 16% 15% 12% 10% 9% 4% 1%1% 13% 3% 1% 5%

Perform a risk assessment.  Inventory your assets  Assess your threats  Analyze the impact of each incident

Step 2 Know your data

Static Does not change over time Not all data is the same. Business vital 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

LocationServer/VMOS and hypervisorApplicationIP addressDisk allocatedDisk usedDependencies SFO-1 Orcl-001RHEL 5.xOracle 11g TB1 TB Exch-001Win 2012 r2 Exchange 2013 (DAG1) TB7 TBExch-002 Win 2012 r2 Exchange 2013 (DAG2) TB7 TBExch-001 MOSS-001Win 2012 r2SharePoint TB8 TBSQL-01, SQL-02 SQL-001Win 2012 r2SQL Server TB3 TB SQL-002Win 2012 r2SQL Server TB2 TB SQL-003Win 2012 r2SQL Server TB2 TB SQL-004Win 2012 r2SQL Server TB2 TB AD-001Win 2012 r2AD Domain Controller TB1 TB LocationAssetsThreat (internal and external)ProbabilityImpact SFO-01 Orcl-001, Exch-001, SQL-001, SQL- 002,SQL-003, SQL-004, SQL-005, FLS-001 Natural disaster - EarthquakeLowHigh Network failureMedium Power failureHigh ClassDescription 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. Examples of an inventory, risk assessment, and classification.

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?

Source: Cloud and Virtual Data Storage Networking (CRC) TIMELINE Data RPO Disaster Occurs O.S. RTO Application RTO Operating System Application Data Data Loss Disaster Operating System Recovered Recovered Data Available RESTORE, RECOVER, RESTART Application Downtime RETENTIONS MoreFewer Frequency of Retentions Hourly Daily Weekly Monthly Main BC Site DR Near Line DR Offline Retention Time Map your recovery process.

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

 Snapshots  Replication  Local backup  Offsite/cloud Primary Site Asynchronous Replication Tiered/Slow Disk Secondary Site Backup Replica Backup Copies Cloud Backup Replication Tiered Disk Selective Data-set Off-site Tape Standby Virtual Data Analytics Build a defense-in-depth. Access Near Real-time

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. Identical Hardware Cloud Bare Metal Restore Dissimilar Hardware Virtual Standby Backup Server Physical Server Virtual Machine SAN/NAS

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

ClassDescriptionFrequency Walk-thru exerciseReview 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. Component exercise Physically exercise a component of a DR plan (e.g. testing automated communications services or work-from-home capabilities together with IT or partner capabilities) At least twice per year or when a change is made to the business or IT operating environment Full-scale simulation Using a scenario, carry out the response and recovery activities of a DR plan the entire organization At least once or twice per year or when a change is made to the business or IT operating environment ClassificationApplicationServer/VMRTORPO Low impactFilesystemFLS hrs Moderate impactSharePoint, Active DirectoryMOSS-001, AD-001, SQL-001, SQL hrs High impactExchange, OracleExch-001, Orcl-0011 hr10 min Test your defenses in layers.

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.