1 / 13

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

Windows Disaster Recovery (DR) with Replication using Double-Take Availability. Solution Overview. Protecting data is important, but cost and complexity prevent small companies & departments from doing it

more
Download Presentation

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

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. Solution Overview • 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

  3. Disaster Recovery for SMBs 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?

  4. Comparing approaches to Replication for DR • Smaller companies (SMBs) or departments within larger companies have historically been road-blocked from these features & capabilities

  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. Requirements For SMB Replication • 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

  7. Leveraging Replication Features for DR • 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

  8. How Host-Based Real-Time Replication Works

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

  10. Top Questions & Key Takeaways • 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.

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

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

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

More Related