180 likes | 194 Views
PlateSpin Protect Virtualize your Disaster Recovery. What You W i ll Learn. 1. The Challenges of Protecting your Servers How to Complete your DR architecture Leverage new technologies to solve old problems How PlateSpin Protect complements existing DR infrastructure. 2. 3. 4.
E N D
What You Will Learn 1 The Challenges of Protecting your Servers How to Complete your DR architecture Leverage new technologies to solve old problems How PlateSpin Protect complements existing DR infrastructure 2 3 4
The Need for Protection 76% of enterprises have declared a disaster or experienced a major business disruption* Power Failure 42% - Natural Disaster 33% - IT Hardware Failure 31% 87% of enterprises have indicated that improving disaster recovery capabilities was critical** Cost of Downtime 56% - Improving Mission Critical Availability 52% - Requirement to Stay Online 24/7 48% - Increased Risk 44% *April 3, 2008 – Building The Business Case for Disaster Recovery Spending – Forrester **June 5, 2008 – The Forrester Wave: Disaster Recovery Services Providers, Q2 2008 - Forrester
Measuring Recovery Time in Hours Business Downtime 46% of enterprises expect to recover a mission-critical application in 10 hours or less 65% of enterprises expect to recover a business-critical application in 10 hours or less Data Loss 65% of enterprises limit mission-critical data loss to 10 hours or less 51% of enterprises limit business-critical data loss to 10 hours or less April 3, 2008 – Building The Business Case for Disaster Recovery Spending – Forrester
As a CIO, You Need DR To: Deliver ROI on Physical, Virtual and Storage infrastructure investments Maximize flexibility and agility Scale from dozens to hundreds of servers or more Deliver the correct protection for all your server tiers Be pragmatic
The PlateSpin solution Production Site DR Site Wide Area Network
Consolidate Recovery Many to One Recovery Environment Whole Workload Protection Lower Infrastructure Costs File based replication PlateSpin Forge (Remote Site) Internal Web Server Email Server Block Based replication
Simplify Testing Rapidly Test Recovery Workloads Isolated Testing of Recovery Workloads PlateSpin Protect (Remote Site) Internal Web Server Email Server
Rapid Failover and Flexible Failback Recovery Workload Runs on Virtual Resource Failback to Dissimilar Hardware Failback with Sync To Repaired Hardware PlateSpin Protect (Remote Site) Internal Web Server Repaired Email Server New Web Server
Integrate with Storage Near real time data RPO Virtualize low change application Best of Breed PlateSpin Protect (Remote Site) OS/Application Replication Application Server Data Replication SAN mounted data
Customer Profile • Large Enterprise to Very Large Enterprise • Multiple Datacenter Sites (Offsite DR facility) • Have virtualization infrastructure deployed, with remaining Physical server infrastructure • Have examined DR architecture and identified multiple protection tiers Example Tier 1: RTO – near 0, RPO – near 0 Tier 2: RTO – 2-5 days, RPO – 24 hours Tier 3: RTO – 30 days, RPO – best attempt
Customer Pains • Current RTO for tier 2 and tier 3 is not achievable for the physical systems using current solutions • Individual hosts can be recovered within the timeframes, but scaling is an issue. • The customer believes their current solution would require several administrator headcount to recover the systems, and test effectively
The PlateSpin solution • Using block based replication (with VSS), replicate physical systems to ESX servers running at the secondary site • Nightly backups staggered throughout replication window • Multiple PlateSpin Protect servers running at DR site (up to 20 physical servers per PlateSpin Protect server) • Flexible image option for tier 3 systems (cheaper DR implementation)
What PlateSpin is the Best Solution • Recovery time is fast. Customer RTO SLAs are now achievable • The personnel required for the recovery is far less than before. (Ex. Recovery of DBs protected with VSS do not require DBA support) • Multiple options (i.e. protecting as VMs or images) to complete DR architecture