Plate Spin Protect Virtualize your Disaster Recovery 1

What You Will Learn 2 1 The Challenges of Protecting your Servers 2 How

Disaster Recovery 3 © Novell, Inc. All rights reserved.

The Need for Protection 76% of enterprises have declared a disaster or experienced a

The Challenge 5 © Novell, Inc. All rights reserved.

Measuring Recovery Time in Hours Business Downtime Data Loss 46% of enterprises expect to

As a CIO, You Need DR To: Deliver ROI on Physical, Virtual and Storage

The Plate. Spin Solution 8 © Novell, Inc. All rights reserved.

The Plate. Spin solution Production Site DR Site Wide Area Network 9 © Novell,

Plate. Spin Protect 10 © Novell, Inc. All rights reserved.

Consolidate Recovery Many to One Recovery Environment Whole Workload Protection File based replication Internal

Simplify Testing Rapidly Test Recovery Workloads Isolated Testing of Recovery Workloads Plate. Spin Protect

Rapid Failover and Flexible Failback Recovery Workload Runs on Virtual Resource Failback to Dissimilar

Integrate with Storage Near real time data RPO Virtualize low change application Best of

Customer Pains • Current RTO for tier 2 and tier 3 is not achievable

The Plate. Spin solution • Using block based replication (with VSS), replicate physical systems

What Plate. Spin is the Best Solution • Recovery time is fast. Customer RTO

Slides: 18

Download presentation

What You Will Learn 2 1 The Challenges of Protecting your Servers 2 How to Complete your DR architecture 3 Leverage new technologies to solve old problems 4 How Plate. Spin Protect complements existing DR infrastructure © Novell, Inc. All rights reserved.

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, Q 2 2008 - Forrester 4 © Novell, Inc. All rights reserved.

Measuring Recovery Time in Hours Business Downtime Data Loss 46% of enterprises expect to 65% of enterprises limit 65% of enterprises expect to 51% of enterprises limit recover a mission-critical application in 10 hours or less recover a business-critical application in 10 hours or less mission-critical data loss to 10 hours or less business-critical data loss to 10 hours or less April 3, 2008 – Building The Business Case for Disaster Recovery Spending – Forrester 6 © Novell, Inc. All rights reserved.

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 7 © Novell, Inc. All rights reserved.

Consolidate Recovery Many to One Recovery Environment Whole Workload Protection File based replication Internal Web Server Email Server 11 © Novell, Inc. All rights reserved. Block Based replication Lower Infrastructure Costs Plate. Spin Forge (Remote Site)

Rapid Failover and Flexible Failback Recovery Workload Runs on Virtual Resource Failback to Dissimilar Hardware Failback with Sync To Repaired Hardware Plate. Spin Protect (Remote Site) Internal Web Server Repaired Email Server New Web Server 13 © Novell, Inc. All rights reserved.

Integrate with Storage Near real time data RPO Virtualize low change application Best of Breed Plate. Spin Protect (Remote Site) OS/Application Replication Application Server Data Replication SAN mounted data 14 © Novell, Inc. All rights reserved.

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 16 © Novell, Inc. All rights reserved.

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 17 © Novell, Inc. All rights reserved.

The Plate. Spin 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 Plate. Spin Protect servers running at DR site (up to 20 physical servers per Plate. Spin Protect server) • Flexible image option for tier 3 systems (cheaper DR implementation) 18 © Novell, Inc. All rights reserved.

What Plate. Spin 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 19 © Novell, Inc. All rights reserved.