Performing Sandboxed Testing with PlateSpin Forge®
Scott [email protected]
Lubomyr [email protected]
Technology Overview
© Novell, Inc. All rights reserved.3
What is a Server Workload?
Server
Data
Applications
Operating System
A workload is the operating system, applications and data that reside on a physical server or virtual host.
Disaster Recovery
© Novell, Inc. All rights reserved.5
The Need for Protection
of enterprises have declared a disaster or experienced a major business disruption*Power Failure 42% - Natural Disaster 33% - IT Hardware Failure 31%
Of enterprises have indicated that improvingDisaster recovery capabilities was critical**Cost of Downtime 56% - Improving Mission Critical Availability 52% -
Requirement to Stay Online 24/7 48% - Increased Risk 44%
76%
87%
*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
Traditional Approaches
© Novell, Inc. All rights reserved.7
How to Be Protected
DR by Duplication
DR by Back-up
© Novell, Inc. All rights reserved.8
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
© Novell, Inc. All rights reserved.9
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?
© Novell, Inc. All rights reserved.10
Cost/Performance Creates a Gap
DR byDuplication
DR byBack-up
Very High Cost
Duplicate Infrastructure
Near-zero Recovery is Crucial
Server/Application Protection
Low Cost
Tape Back-up or Imaging
Recovery in Days is Tolerable
Data Protection
Tier 1 Tier 2 Tier 4 Tier 3 Tier 5
The Solution
© Novell, Inc. All rights reserved.12
Consolidated RecoveryLeveraging Virtual Infrastructure for Protection of Physical servers
Solution– Inventory and monitor to
plan recovery environment– Live replication of workload
into an off-line virtual machine– One click test restore and failover
Benefits– Drastically reduce TCO and
RTO while achieving whole workload protection
– Improving RPO through incremental synchronization
– Simplify testing with bootable backups
Physical ProductionServers
Virtual Recovery Hosts
© Novell, Inc. All rights reserved.13
Cost Performance
Risk
ConsolidatedDisasterRecovery
Reduce recoverytime from days
to minutes
Test recovery plansto ensure you're prepared
Protects moreserver for less
PlateSpin® Solves 3 Challenges
© Novell, Inc. All rights reserved.14
Protection Candidates
Protection for middle tier servers
99.99% or better(less than 1 hour per year)
97%-99.99%(between 1 hour and 11 days per year)
97% or worse(11 days per year)
cost
Workload Protection with PlateSpin Forge®
© Novell, Inc. All rights reserved.16
Run Replication
PlateSpin Forge® Workload Protection:A 4-Step Process
Prepare Replication
Configure Protection
Add Workload
Step 1: Add Workload
© Novell, Inc. All rights reserved.18
Step 1: Add Workload
Adding a Workload:• User connects to
PlateSpin Forge®
• User executes “Add Workload” command
• Forge connects to the primary workload using WMI and remote registry queries and obtains inventory information
• The primary workload information is compiled by Forge and stored in its SQL database
PrimaryWorkloadForge User
Forge Server
HTTPS
Add Workload
WMI/Remote Registry
© Novell, Inc. All rights reserved.19
Step 1: Add Workload
• Click on ‘Add Workload’ button from Forge Dashboard or Workload Page
• Enter Local Admin or Domain Admin credentials and click ‘Submit’• WMI must be enabled and running on the source
© Novell, Inc. All rights reserved.20
• PlateSpin Forge® will validate the provided credentials against the Primary Workload
Step 1: Add Workload
© Novell, Inc. All rights reserved.21
Step 1: Add Workload
• The Add Workload screen will redirect you to the main Workloads Page and the ‘Adding Workload’ status will be displayed
• Clicking on the workload name will display a progress bar ofthe job
Step 2: Configure Protection
© Novell, Inc. All rights reserved.23
Step 2: Configure Protection
Configure Protection:• User executes “Configure Protection” command• Workload Protection Details page appear and filled by the user• Clicking on Save will assign the protection settings to the primary
workload object in the Forge database
© Novell, Inc. All rights reserved.24
Step 2: Configure ProtectionTier Settings• In this section, configure the workload protection schedule for incremental
replications and define the workload failure detection interval settings• Either select from existing tiers (Hourly, Nightly, or Weekly),
user-created Tiers or create a one-time tier by selecting Custom• Tiers can be changed at any time
© Novell, Inc. All rights reserved.25
Step 2: Configure ProtectionReplication Settings
• In this section, select the transfer method, the network to use for replication, and which volumes to copy
© Novell, Inc. All rights reserved.26
Step 2: Configure ProtectionReplication Settings – Transfer Methods
• PlateSpin Forge® provides three live transfer methods for replicating workloads:
– File based– Snapshot based (VSS)– Block based
© Novell, Inc. All rights reserved.27
Step 2: Configure ProtectionSource Credentials
• This section prompts for administrative credentials for the Primary Workload
© Novell, Inc. All rights reserved.28
Step 2: Configure ProtectionReplication Settings – Replication Network
• In this section, configure the network settings which will be used during replication
© Novell, Inc. All rights reserved.29
Step 2: Configure ProtectionReplication Settings – Protected Volumes
• In this section, select which volumes on the Primary Workload should be protected
• System Volume cannot be unchecked
• The Non-Volume Partition section displays allnon-volume partitions detected on the workload. For example, vendor partitions
© Novell, Inc. All rights reserved.30
Step 2: Configure ProtectionReplication Settings – Services to Stop During Replication• This section allows one to define which services to
stop on the Primary Workload during the replication
© Novell, Inc. All rights reserved.31
Step 2: Configure ProtectionFailover Settings• In the Failover Settings section users define the
configuration of the Recovery Workload during a Failover
© Novell, Inc. All rights reserved.32
Step 2: Configure ProtectionFailover Settings – Target Services
• In this section, specify the virtual network the Recovery Workload will use during the Prepare for Failover stage
© Novell, Inc. All rights reserved.33
Step 2: Configure ProtectionTest Failover Settings
• Test Failover Settings define which settings the recovery workload will use during a ‘Test Failover’ job
© Novell, Inc. All rights reserved.34
Step 2: Configure Protection
• Three commands are available at the bottom of the Workload Configuration page
• Once the workload protection settings have been saved, an overview screen will be displayed with three actionable workload commands
• To change the protection settings scroll up and click on Edit
Step 3: Prepare Replication
© Novell, Inc. All rights reserved.36
Step 3: Prepare Replication
Prepare Replication:
• User executes “Prepare Replication” command
• A PlateSpin® Controller is deployed to the Primary Workload
• PlateSpin Replication software is deployed to the Primary Workload
• The Recovery Workload shell is built and stored on the PlateSpin Forge® Appliance
PrimaryWorkloadForge User
Forge Server
HTTPS
Prepare Replication
© Novell, Inc. All rights reserved.37
Step 3: Prepare Replication
• To start the preparation, click on Prepare Replication and Execute in the Command Confirmation screen
• The WUI will switch tothe Workloads Pagedisplaying “PreparingReplication” under theReplication Status column
Prepare Replication
Step 4: Run Replication
© Novell, Inc. All rights reserved.39
Step 4: Run Replication
Run Replication:
• User executes “Run Replication” command
• The Recovery Workload boots and a local controller is created
• Data replication between the Primary Workload and the Recovery Workload is initiated. Both controllers report the replication metrics (transfer speed, total files, etc.) to the Forge Management VM Primary
WorkloadForge User
Forge Server
HTTPS
Run Replication
© Novell, Inc. All rights reserved.40
Step 4: Run Replication
• To start the replication, click on Run Replication and Execute in the Command Confirmation screen
Upon executing the command the WUIwill switch to the main Workloads pagedisplaying “Running First Replication”under Replication Status column
Sandboxed Testing – Test Failover
© Novell, Inc. All rights reserved.42
Test Failover
Test Failover Process:• User executes
“Test Failover” command• PlateSpin Forge® boots and
configures the Recovery workload and connects it to the internal test network
• User connects to the workload using VMware Virtual Infrastructure client and validates the workload functionality
• User marks the test result and shuts down the Recovery Workload
• PlateSpin Forge restores the recovery workload to its last “known good state”
PrimaryWorkloadForge User
Forge Server
HTTPS
Test Failover
© Novell, Inc. All rights reserved.43
Test Failover
Test Failover
• Clicking on theworkload name willdisplay the jobprogress indicator
• Email is sent when theworkloadis ready forinspection
© Novell, Inc. All rights reserved.44
Test Failover
© Novell, Inc. All rights reserved.45
Test Failover – Reporting
• Current Protection Status report provides a comprehensive view of workloads’ failover test
Demo
Where Forge Fits
© Novell, Inc. All rights reserved.48
Novell® Identity Manager
Novell® Access Manager
Novell® Roles Based Provisioning Module
Novell® Access Governance Suite
Novell Privileged User Manager
Novell® SecureLogin®
Novell® Cloud Security Service
How Novell® Delivers Intelligent Workload Management
Build Secure Manage MeasureSUSE® Linux Enterprise Server
SUSE Studio
SUSE Linux Enterprise JeOS
ZENworks® Configuration Management
SUSE Appliance Toolkit
Novell® Workshop
Novell® Business Service Manager
Novell® Business Service Level Manager™
Novell® Business Experience Manager™
Novell® myCMDB™
Novell® Sentinel™
Novell® Sentinel™ Log Manager
Novell Compliance Automation
PlateSpin® Migrate
PlateSpin® Orchestrate
ZENworks® Configuration Management
PlateSpin® Recon
PlateSpin® Protect
PlateSpin Forge®
PlateSpin® “Atlantic”
PlateSpin® “BlueStar”
ZENworks® “Workbench”
* Available by end of 2010
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.