1. 1 Windows Disaster Recovery (DR) with Replication using Double-Take Availability

2. 2  Protecting data is important, but cost and complexity prevent small companies & departments from doing it  Backup is very important, but it alone cannot provide for a rapid failover or recovery from a disaster Replication provides superior RTOs & RPOs.  Host-based DR for Windows servers can be both easy and affordable, also applicable to virtual servers  Double-Take is recognized as the market leader in host based replication and recovery for 16+ years Solution Overview

3. 3 When do SMBs start to consider DR and Replication?  When application recovery in the event of a disaster must happen quickly, <1hr vs. several hours Does not replace backup, augments data protection  RTO & RPO – Time and Point objectives for recovery Synchronous vs. Asynchronous – Depends on Latency  When should shared storage be considered as part of a DR project? Disaster Recovery for SMBs

4. 4  Smaller companies (SMBs) or departments within larger companies have historically been road-blocked from these features & capabilities Comparing approaches to Replication for DR Host-Based Replication SAN Appliance Disk-to-disk Replication Recovery PointNear real-time - real time Near real-time - real time Recovery Time<1hr - ~10min<1hr – instantly<30min - instantly ScalabilityGoodVery Good ManagementPer serverCentralizedPer array Entry Cost$$$ - $$$$$$ - $$$$

5. 5 Basic Architecture – What You Will Need  At least two servers for failover, one server for management  Two or more SAN storage devices (Fibre Channel* or iSCSI)  Shared Network (* = plus FC fabric and FCIP extension if FC storage)  Replication capabilities on servers or storage

6. 6  Top 5 criteria in addition to being SAN storage Cost Effective Protected & Reliable Easy Upgrades and Management Reasonable Performance NOT burdened with additional features that applications, operating systems, and server virtualization provides  iSCSI + Host-Based Replication is a good technology match for these criteria Requirements For SMB Replication

7. 7  What are the concerns Bandwidth & Latency of WAN Hardware-dependent failover  Addressing Those Concerns Real-time replication that is optimized for WAN ‣ Replicates with compression & bandwidth limiting optimization Across Hardware and Virtualization ‣ Failover across subnets, support for dissimilar hardware and storage, between physical or virtual systems in either direction Value of Host-based with Double-Take Availability ‣ 3 Levels of Compression, byte level differences only, real-time or scheduled/throttled, full-server or data-only Leveraging Replication Features for DR

8. 8 How Host-Based Real-Time Replication Works

9. 9 Putting It Together – DR with 16TB of SAN

10. 10  Top Questions For small environment (5 VMs & <100 users), how much Bandwidth? What is a practical distance for small environment DR (Latency)?  Solution Key Takeaways Protecting data is important, but cost and complexity prevent small companies and departments from doing it for most data. Backup alone cannot provide for a rapid failover or recovery from a disaster; replication provides superior RTOs & RPOs. DR for Windows servers (incl VMs) can be done both easily & affordably with DroboElite and Double-Take Availability. Top Questions & Key Takeaways

11. 11 Questions? Feedback & comments also welcome @ tv@drobo.com, or on Twitter @ Drobo More DroboElite solutions @ http://www.drobo.tv tv@drobo.comhttp://www.drobo.tv

12. 12 Example – Full Server Protection & Failover  Hardware and Application independent Physical or Virtual  Target requires only a base Operating System

13. 13 Example – Data Protection and Failover  Only replicates application data Less data across the wire  Faster failover possible