beyond disaster recovery: restoring production workloads with platespin forge

Beyond Disaster RecoveryRestoring Production Workloads with PlateSpin Forge®

Jan KotowskiProduct [email protected]

The Industry Solution

© Novell, Inc. All rights reserved.3

How to Be Protected

DR by Duplication

DR by Back-up


DR by Duplication

• Focus is on protecting application– Local cluster– Duplicate hot site

• High performance, but at what price?– Near zero RTO, RPO

• High cost– Duplicate infrastructure– Cost x2


DR by Back-up

• Focus is on protecting data– Tape back-up– Imaging

• Poor performance– Slow RTO, RPO (days)

• Cost effective, but at what price?– How do we get the data back in to a useable state?– How long to rebuild the server?

Technology Overview


Workload

Application

Middleware

Operating System

Workload: The (New) IT Paradigm

A workload is an integrated stack of application, middleware, and operating system that accomplishes a computing task

•

A workload is portable and platform agnostic–it can run in physical, virtual or cloud computing environments

A workload or a collection of workloads makes up a business service, which is what the end user consumes


Overview:Another Perspective

Physical Server Virtual Host

1 workload per physical server

Multiple workloads per physical server


Overview:PlateSpin® Technology

Workload Profiling• Agent-less data collection• Resource sizing and analysis

Workload Portability• Move, copy and replicate workloads• Cross infrastructure boundaries

The Solution:Protect More with Less


Disaster Recovery and Availability Challenges

Disaster recovery and availability replicates whole-server workloads to a virtualized recovery site

Challenges – Before 20% protected/over-protected 80% under-protected Slow daily tape backup; poor RPO Slow recovery time; poor RTO Difficulty testing; can’t meet RTO

Solution – After 100% protected Match protection to workload need One-click recovery Fast recovery time Easy to test

P P VV


PlateSpin® Solution at a Glance

PlateSpin solves disaster recovery at a workload level (data, application, operating system)

Replicate whole server workloads into a warm standby consolidated virtual environment

Run failed workloads directly off of the secondary system in the event of downtime in minutes

Rebuild and recovery servers to new or existing hardware in hours

PlateSpin Forge®


PlateSpin Forge®

PlateSpin Forge is a disaster recovery hardware appliance able to protect up to 25 workloads

PhysicalServer

VirtualMachines

PlateSpin ForgeDisaster Recovery Appliance

Live incremental replication of

production workloads

Simplify recovery with one click

failover

Gain visibility into protection with reporting and

alerting

Hardware independent failback


How PlateSpin Forge® Works

Production Server

Users

Production Server

PlateSpin Forge

PlateSpin Forge

PlateSpin Forge

Step 1:Replicate up to 25 physical or virtual workload to PlateSpin Forge

Step 2:Test workload in new environment to ensure it runs as predicted

Step 3:Production server goes down, switch users to PlateSpin Forge in minutes

Failback: Restoring Production Workloads


Failback Overview

Failback is a build-in PlateSpin Forge® feature that leverages workload portability technology to restore physical or virtual production workloads

DR SiteProduction Site


Failback Flexibility

Physical Server - IBM

Physical Server - Dell

OR

Virtual Host: ESX, Hyper-V, Xen

OR

• Failback can be used to restore workloads to:– The same or different physical hardware– A virtual environment


Incremental Failback

Incremental failback will only transfer changes that occurred since the workload has been failed-over.

• Failback supports both full and incremental replications.

• Incremental failback can be used to restore the production workload that contains original data


Failback, Test and Cut Over

Step 1:Failback the workload

Step 2:Test the workload in production, while users are still connected to the failed-over workload

Step 3:Perform incremental failback to sync changes and switch users over to the production workload

Unpublished Work of Novell, Inc. All Rights Reserved.This work is an unpublished work and contains confidential, proprietary, and trade secret information of Novell, Inc. Access to this work is restricted to Novell employees who have a need to know to perform tasks within the scope of their assignments. No part of this work may be practiced, performed, copied, distributed, revised, modified, translated, abridged, condensed, expanded, collected, or adapted without the prior written consent of Novell, Inc. Any use or exploitation of this work without authorization could subject the perpetrator to criminal and civil liability.

General DisclaimerThis document is not to be construed as a promise by any participating company to develop, deliver, or market a product. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. Novell, Inc. makes no representations or warranties with respect to the contents of this document, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. The development, release, and timing of features or functionality described for Novell products remains at the sole discretion of Novell. Further, Novell, Inc. reserves the right to revise this document and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. All Novell marks referenced in this presentation are trademarks or registered trademarks of Novell, Inc. in the United States and other countries. All third-party trademarks are the property of their respective owners.