Data Management Services AssuredSnap

Page 2 Agenda Why protect your data?  Causes of data loss  Hardware data protection  DMS data protection  Data protection metrics Reducing Data Loss & Improving Recovery Times  Data Protection Strategies  Tape Backup vs. Snapshots  Reducing Data Loss  Improving Recovery Times  Improved Application Availability Reducing Backup Windows  Customer Needs  Reducing Backup Windows Data Management support  Customer Needs  Business Analytics  Application Test & Development Snapshot Benefits Summary Close and Q&A

Page 3 Why Protect Your Data? Protect against accidental corruption or loss of data  Human or program errors  System failures (hardware, software, network) Protect against malicious corruption or loss of data  Viruses, Sabotage Protect against local and wide area disasters  Disaster Recovery/Business Continuance Because you have to!  HIPAA, Sarbanes-Oxley, SEC 17 A, EU DPA, etc. No longer an option! Source: Horison Information Strategies

Page 4 Interesting Points to Consider On average, companies value 100 megabytes of data at more than $1 million (Source: Ontrack Data International) Estimates show that 1 out of 500 data centers will have a severe disaster each year 93% of companies that lost their data center for 10 days or more due to a disaster filed for bankruptcy within one year of the disaster. 50% of businesses that found themselves without data management for this same time period filed for bankruptcy immediately. (Source: National Archives & Records Administration in Washington.) The value and vulnerability of data, and the cost of not protecting

human error software program malfunction computer virus site disaster hardware or system malfunction 44% 32% 3% 7% 14% Causes of data loss source: Ontrack, a data availability service provider Data Protection Problems

44% 3% 14% RAID, clustering, and local/remote mirroring protect against hardware failure or malfunction Causes of data loss source: Ontrack, a data availability service provider Hardware protection is ½ the solution RAID: 0,1,3,5,6,10,50 32% 3% 7% 14% human error software program malfunction computer virus site disaster hardware or system malfunction

44% 3% 14% RAID, clustering, and local/remote mirroring protect against hardware failure or malfunction Causes of data loss source: Ontrack, a data availability service provider DMS Software completes the solution RAID: 0,1,3,5,6,10,50 32% 7% human error software program malfunction computer virus site disaster hardware or system malfunction 3% 14% Complete independent volume copy Additional data protection against RAID set or volume failure Non-disruptive use of live volume Logical, point-in-time copy of a data volume Maintains Business Continuity Reduces Backup Windows Improves Data Recovery Minimizes Data Loss Future offering Independent volume copy to a remote location AssuredSnap AssuredCopy RemoteSync

RAID, clustering, and local/remote mirroring protect against hardware failure or malfunction Complete independent volume copy Additional data protection against RAID set or volume failure Non-disruptive use of live volume Causes of data loss source: Ontrack, a data availability service provider Dot Hill’s Data Protection Solutions RAID: 0,1,3,5,6,10,50 AssuredSnap AssuredCopy human error software program malfunction computer virus site disaster hardware or system malfunction 44% 32% 3% 7% 14% RemoteSync Future offering Independent volume copy to a remote location Logical, point-in-time copy of a data volume Maintains Business Continuity Reduces Backup Windows Improves Data Recovery Minimizes Data Loss

Page 9 Key Considerations Recovery Point Objective (RPO)  How much data can you afford to lose? Recovery Time Objective (RTO)  How long can you afford to be without your data?  What are downtime costs?  What are downtime implications? Data Classification  How critical is your data to the operational and financial viability of the company?  All data is not created equal Budget  How much money can you afford to spend? Source: Enterprise Storage Group “The Evolution of Data Protection” RTO vs. RPO vs. Budget $ trade-offs as one size does not fit all…

Page 10 Data Protection Technology Positioning FeatureFunction Data Loss (RPO) Outage (RTO)CostProtection RAIDMethod for storing data across a number of hard disk drives to achieve data redundancy None $Disk drive failure SnapshotsPoint-in-time logical image of a physical volume HoursMinutes$$Logical data loss or corruption Volume CopyComplete physical and independent copy of a volume Hours-DaysMinutes$$$Logical data loss or corruption Remote Snapshot Replication Remote snapshots of a primary volume Hours - Days Minutes- Hours $$$Local or wide-area disasters Semi- synchronous Replication Replication of data to one or more geographically remote systems.  I/O to primary volume propagated to remote volume after sending host acknowledgement Seconds- Minutes Minutes- Hours $$$$Local or wide-area disasters Synchronous Replication Replication of data to one or more geographically remote systems.  I/O to primary volume propagated to remote volume before sending host acknowledgement NoneMinutes- Hours $$$$Local-area disasters BackupTraditional tape-based Days- Weeks Hours - Days $$Local or wide-area disasters (w/ vaulting) ArchiveTraditional tape-based -Days- Weeks $$-

Reducing Data Loss & Improving Recovery Time with AssuredSnap

Page 12 Data Protection Strategies Traditional Tape Backup  Nightly backup to tape  Full backup on weekends  Incremental or differential on weekdays  RPO = up to 24 hours Snapshots  Snapshot taken every 2 hours  RPO = up to 2 hours Risk Mitigation

Page 13 Reducing Data Loss (RPO) Traditional Tape Backup 1.File share taken offline at 12:00 am 2.Backed up to tape 3.File share brought back online at 12:30 am 4.Corruption occurs at 4:30 pm 5.Previous night’s tape located 6.File share restored from previous night’s backup tape 7.File share back online at 6:00 pm 16 hours of work is lost! Snapshots 1.Snapshot of File Share taken every 2 hours  12 am, 2 am, 4 am, 6 am, 8 am, 10 am, 12 pm, 2 pm, 4 pm, 6 pm, etc. 2.Corruption occurs at 4:30 pm 3.File share restored from 4:00 pm snapshot 4.File share back online at 4:45 pm 30 minutes of work is lost! Risk Mitigation: Lost Revenue and Customer Confidence

Page 14 Improving Recovery Time (RTO) Traditional Tape Backup 1.File share taken offline at 12:00 am 2.Backed up to tape 3.File share brought back online at 12:30 am 4.Corruption occurs at 4:30 pm 5.Previous night’s tape located 6.File share restored from previous night’s backup tape 7.File share back online at 6:00 pm  Data unavailable for 1 ½ hours! Snapshots 1.Snapshot of File Share taken every 2 hours  12 am, 2 am, 4 am, 6 am, 8 am, 10 am, 12 pm, 2 pm, 4 pm, 6 pm, etc. 2.Corruption occurs at 4:30 pm 3.File share restored from 4:00 pm snapshot 4.File share back online at 4:45 pm  Data unavailable for 15 minutes! Risk Mitigation: Lost Business and Customer Confidence

Reducing Backup Windows with AssuredSnap

Page 16 Reduced Backup Window Drivers Business  24-hour customer service  Such as help desks  24-hour business processing  Such as online sales orders  Customer satisfaction, loyalty and retention  Competitive advantage and financial viability Operational  7x24x365 operations  Continuous application availability  Shrinking backup windows

Page 17 Corporate LAN Automated Tape Library G: Primary Storage Snapshot Use - Reduce Backup Window Zero-downtime backup Exchange ServerFile ServerDatabase ServerBackup Server SAN 1. Take snapshot 2. Mount snapshot to backup server 3. Backup data to tape/disk

Data Management Support with AssuredSnap

Page 19 Customer Needs Business  Business Analytics - Access to and use of full copies or extracts of production data for other uses.  Data Mining  Decision Support  Data Distribution  e.g., web server content  Speed application time-to-deployment for improved productivity and competitive advantage. Operational  Access to and use of production data without impacting the data integrity of production applications.  Support Rapid Application development strategies  Use production data without effecting production data or impacting the production application.  Test with full production set vs. subset or “made-up” data; current vs. outdated data  Run parallel benchmarks  Reveal more problems sooner in test rather than in production

Page 20 Corporate LAN Automated Tape Library G: Primary Storage Snapshot Use – Business Analytics Data Mining; Decision Support Exchange ServerFile ServerDatabase ServerAppl. Server SAN 1. Take snapshot 2. Mount snapshot to application server 3. Access production data

Page 21 Volume 1 1:00 PM2:00 PM Active File System Snapshot 1 Snapshot 2 Ok for 1-time extracts AssuredSnap – Traditional Method Take snapshot 1 Mount to application host Take snapshot 2 Re-establish mount point Application Server

Page 22 Volume 1 6:00 AM Active File System Snapshot 1 Automated, periodic updates AssuredSnap – Reset Function »Take snapshot 1 »Mount to application host »Reset snapshot 1 »Etc. 12:00 Noon 6:00 PM Application Server 12:00 AM Snapshot Reset Logical delete of snapshot data followed by a snapshot create Re-use same volume attributes (WWN, SN, LUN, etc) for a new snapshot How it works:

Page 23 Application Development & Test Two Methods  Reset Snapshot  Refresh Snapshot Snapshot Refresh  Leverages the Original/Write Data Preservation function  Both original and modified data preserved  Modified data may be deleted to “refresh” the snapshot back to its original state Use production data without effecting production data or impacting the production application

Page 24 AssuredSnap R/Evolution AssuredSnap snapshot limits  16 snapshots per system included on 2000 Series, none on 5000 Series (change per OEM agreements)  Licensed upgrade for up to 64 snapshots on 2000 Series, 256 on 5000 Series Snapshot volume access  Mount for read-only or read-write  Both original-state and modified data preserved  Delete modified data on writable snapshot (i.e., refresh snapshot)  Limited to 32 snapshots per volume Roll-forward/Roll-back  All snapshots (i.e., both newer and older) are preserved even after performing a rollback operation  Rollback to the original or modified snapshot state  Roll back or roll forward to a different snapshot if the initial roll-back was not the one really needed Reset snapshot  Logical snapshot delete, create; maintains same volume attributes (e.g., WWN, SN, LUN, etc) for the new snapshot.  Supports application snapshot scripting (requires consistency of WWN, SN, LUN, etc.).  e.g., Backup Automated snap pool space management (i.e., auto-grow)  Policy set in MB/GB increments  Triggered off capacity threshold (default = 90%) Key Capabilities

AssuredSnap Benefits

Page 26 AssuredSnap Benefits 1.Minimizes Data Loss  Reduces the data protection interval period (i.e., Improved RPO)  Reduces data loss and re-work 2.Improves Data Recovery and Business Continuity  Rapid restore to any point-in-time snapshot  Improves application and data availability (i.e., Improved RTO) 3.Drastically Reduces Backup Windows  From hours to minutes  Improves application & data availability 4.Supports Business Analytics & Rapid Application Development  Use production data without effecting production data or impacting the production application  Improves quality and timeliness of business decisions  Improves application time-to-deployment 5.Satisfies Regulatory Compliance  Data is protected and recoverable Significant Business Impact; Operational and Financial

Page 27 AssuredSnap Benefits Risk Mitigation  Data Loss  Application & Data Availability  Employee Productivity  Lost Business  Lost Revenue  Lost Customer Confidence  Lost Market Good Will  Customer Satisfaction, Loyalty and Retention  Financial Viability Significant Business Impact; Risk Mitigation

AssuredSnap Questions