This session explores the two phases of restoring workloads and IT services from an outage or a full-blown disaster. Phase one is the disaster recovery itself, or automatic failover to run protected workloads in a recovery environment after a disruption. Phase two is often overlooked; it returns the protected workloads to the rebuilt or replaced production environment. During this session, you will learn how to configure PlateSpin Forge to handle both of these critical phases.

1. Beyond Disaster Recovery
Restoring Production Workloads with PlateSpin Forge ®
Jan Kotowski
Product Manager
jan.kotowski@novell.com

2. The Industry Solution

3. How to Be Protected
DR by Duplication
DR by Back-up
3 © Novell, Inc. All rights reserved.

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

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

6. Technology Overview

7. Workload: The (New) IT Paradigm
Application
Workload Middleware
Operating System
A workload is an A workload is A workload or a
integrated stack of portable and collection of
application, middleware, platform agnostic workloads makes
and operating system –it can run in up a business
that accomplishes a physical, virtual or service, which is
computing task cloud computing what the end user
environments consumes
7 © Novell, Inc. All rights reserved.

8. Overview:
Another Perspective
Physical Server Virtual Host
1 workload per Multiple workloads per physical server
physical server
8 © Novell, Inc. All rights reserved.

9. Overview:
PlateSpin Technology ®
Workload Profiling
• Agent-less data collection
• Resource sizing and analysis
Workload Portability
• Move, copy and replicate workloads
• Cross infrastructure boundaries
9 © Novell, Inc. All rights reserved.

10. The Solution:
Protect More with Less

11. Disaster Recovery and
Availability Challenges
Disaster recovery and availability replicates whole-
server workloads to a virtualized recovery site
P P V V
Challenges – Before Solution – After
20% protected/over-protected 100% protected
80% under-protected Match protection to
Slow daily tape backup; poor RPO workload need
Slow recovery time; poor RTO One-click recovery
Difficulty testing; can’t meet RTO Fast recovery time
Easy to test
11 © Novell, Inc. All rights reserved.

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

13. PlateSpin Forge ®

14. PlateSpin Forge ®
PlateSpin Forge is a disaster recovery hardware
appliance able to protect up to 25 workloads
Physical
Server
Virtual
Machines
PlateSpin Forge
Disaster Recovery Appliance
Live incremental Gain visibility into
Simplify recovery
replication of protection with Hardware
with one click
production reporting and independent failback
failover
workloads alerting
14 © Novell, Inc. All rights reserved.

15. How PlateSpin Forge Works ®
Step 1:
Replicate up to 25 physical
or virtual workload to
PlateSpin Forge
Production Server PlateSpin Forge
Step 2:
Test workload in new
environment to ensure it
runs as predicted
Production Server PlateSpin Forge
Step 3:
Production server goes
down, switch users to
PlateSpin Forge
PlateSpin Forge in minutes
Users
15 © Novell, Inc. All rights reserved.

16. Failback:
Restoring Production Workloads

17. Failback Overview
Failback is a build-in PlateSpin Forge feature that
®
leverages workload portability technology to restore
physical or virtual production workloads
Production Site DR Site
17 © Novell, Inc. All rights reserved.

18. Failback Flexibility
• Failback can be used to restore workloads to:
– The same or different physical hardware
– A virtual environment
OR
Physical Server - IBM
OR
Physical Server - Dell
Virtual Host: ESX, Hyper-V, Xen
18 © Novell, Inc. All rights reserved.

19. Incremental Failback
• Failback supports both full and incremental replications.
• Incremental failback can be used to restore the
production workload that contains original data
Incremental failback will only transfer changes that
occurred since the workload has been failed-over.
19 © Novell, Inc. All rights reserved.

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

21. Demo

23. 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 Disclaimer
This 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.