SAP OS/DB MigrationsEase complexity of SAP Landscapes with Vblock™ Systems

Michael R TovishBusiness Critical Applications Marketing Lead

michael.tovish@vce.com

2

Today’s Topics

• Introducing Innovation into Data Centers‒ Timing vs. capability: DC Readiness

• How to Simplify Diffusion of Technology‒ Creating a sustainable infrastructure to support competition

• Designing an Effective “Black Box”‒ Manufacturing the Golden Ratio of Technology

• Reducing Risk with OS/DB Best Practices‒ Creating the Ideal Rapid Deployment Service

3

The Board’s View of the World

In House Outsource

Decision on Solutions

Retu

rn

Long Term

Short Term

Incentives Training Change Management

ITPeople

Competing Business PrioritiesMarket Share Profitability/Productivity Customer and Partner Experience

Employee Satisfaction Shareholders Value Corporate Citizenship

4

The IT Blueprint for Success

Identify Market Shift

Thought Leadership Ideation

System Functional Specifications

Build Infrastructure

Competitive Differentiation

5

Assessing Data Center Readiness

6

Converged Infrastructure from VCE

To create Converged

Infrastructure

IT Business Mgmt

Driving Innovation at the intersection

Packaged to meet demands of real

business

Pivotal

Unified Computing

Nexus

Insieme

ViPRIsilon

XtremIO VNXVMAX

Horizon ViewvCloud Suite

vSphere

vCenter Ops

MDS

R&D pipeline from Industry leaders

7

VCE Solutions for SAP Landscapes

8

Continue To Be a “Rainmaker”In an Increasingly Cloudy World

RReduce TCI

IImproveSLAs

MMinimizeRisk

MODULAR

SCALABLE

Across the five SAP architectures: Cloud, Mobility, Applications,

Analytics, and Database & Technology

Scale departmental to enterprise ERP, CRM, PLM, SCM, BW and HANA workloads

Safely Enable the Landscape Services You Need

9

CiscoCisco Virtual Security Gateway (VSG) Cisco Intelligent Automation for Cloud Cisco Single-Node Hana Appliance GBIC/SFP Products Cloud Services Router (CSR) vWAAS UCS Director Manager (Cloupia)

EMC RSAEMC RSA EMC RSA Archer eGRC EMC RSA Data Loss Prevention EMC RSA Secure-ID EMC Isilon

VMware

VMware vShieldVMware vCloud Director VMware vCloud Suite VMware vCloud Automation Center (Dynamic Ops)VMware Site Recovery Manager VMware vCenter Configuration ManagerVMware vFabric: Gemfire, tc Server, HyperIC, vFabric Web Server

Regression testing

Design for continuous interoperability

Interoperability testing

System optimization Update/validation

Ongoing release matrix/code currency

Current and Optimized

Target on Total Cost of ImplementationIn The Factory To Your Data Center Floor In 45 Days

“With the Vblock System our SAP team had Supply Chain Management live in less than 90 days versus six months previously. With Data Domain we have reduced SAP backup from 26 hours to 3 hours.”

JAMES HOUSTONVice President

Shared IT Services

10

Target On Service Level AgreementsConverged Operations

“We virtualized 100% of the company while keeping the business running—and most never experienced a service interruption.”

Jeremy LawrenceDirector IT

11

Target On Minimizing RiskGuiding You Safely From Here To There

“We were able to convert everything— our integrated Sybase database, SAP applications, the entire operation— in one weekend. Quite honestly, it’s been a flawless implementation to-date.”

Michael RedekerVice President

and CIO

Professional Services

12

Intelligent OperationsHow We Deliver The Goods

13

OS/DB Migration Compelling Events

• Reclaiming control of shadow IT investments

• Procurement cycles associated with disparate H/W Vendors

• Business Continuity Plan

• Cost reduction by way of software licensing

14

Taking The RISK Out of RISC Migration

RiskMgmt

Process

Measure

Assess

Mitigate

Execute

Application AvailabilityApplication Availability

Application PerformanceApplication

Performance

Data IntegrityData Integrity BCP / DRBCP / DR

Risks to manage

Your critical SAP instances supporting business processes and associated applications run on RISC/UNIX based servers today

Business owners are looking for:• Technical feasibility of running existing

RISC/UNIX applications on UCS• Validation of financial benefits• Maintaining SLAs during and post

migration• Reducing the overall risks

15

SAP Platform OS/DB Migrations

• Thanks to the hardware abstraction layer standard SAP solutions are independent from operating system and database

• Moving to another OS or DB will not influence the business processes

• Simply a infrastructure project – not a business process one

BW

WebAS

TREXJ2EE

PortalWebAS

MIWebAS

NetWeaver Integration Solutions

SAP System landscapeSAP Business Solutions

MDMWebAS

SSMWebAS

ECC

WebAS

SCM

WebAS

SRM

WebAS

CRM

WebAS

XIWebAS

LiveCache

Business logic written in ABAP and Java (OS independent)

Hardware abstraction layer

Runtime (OS dependent)Database (OS dependent)

16

Migration Phases

HPUXAIX

HPUXAIX

AwarenessAwarenessAwarenessAwarenessBusiness Drivers

Technical Components

Interdependencies

Business Drivers

Technical ComponentsInterdependencies

VerificationVerificationVerificationVerification

Technical consistency

Functional consistency

Technical consistency

Functional consistency

StrategyStrategyStrategyStrategyComponents to migrate

Overall approach

Migration order

Components to migrateOverall approach

Migration order

ExecutionExecutionExecutionExecutionTools

Implement the plan

Test

Tools

Implement the plan

Test

17

DEV_OLD PRD_OLD

DEV_NEW

Migration

QA_OLD

Migration

PRD_NEW

Hom. Copy

QA_NEW

SAP Standard Migration Sequence

Migration sequence of a standard SAP three system landscape

Advantage: QA will be refreshed during migration!!

18

Migration PhasesMigration order – Step #1 Co-locate

18

Current State

Primarily 2 Production Systems� Supporting environments for each:

� Approximately 12 environments altogether

� Controlled servers, controlled storage costs

Client Server 2-3 Tier

SAP ABAP (only)

Single DBMS

Future State

Characteristics Approximately 8–9 Production Systems� Supporting environments for each:

� Approximately 54 environments altogether

� Exploding servers and storage costs

� Backup and recovery challenges

� Disaster recovery challenges

Enterprise SOA

Unicode SAP Dual Stack ABAPJAVA

Federated DBMSLandscape

Industry Apps

§ Reasons ForAids parallel operationsGenerally required to move

dataMore options/faster transfer

speeds

§ Reasons AgainstEnvironmental constraintsSecurity

Operational issues § Alternative

Direct pipes between environments

Import/Export

19

Migration PhasesMigration order – Step #2 Data Source

§ Review your current operating environment

OS, Storage footprint, RDBMS software, connectivity

§ Migration OptionsYour selected migration strategy will depend on the

current operating environment and virtualization strategy

§ Bare Metal Database Server(s)Data Replication, Disk to Disk Copy, Backup Restore

§ Virtualized Database Servers(s)Bare metal options plus P2V, VMotion, Storage

VMotion

Once your data source is migrated and tested – best move is to cut old SAP instances over to new data source

20

Migration PhasesMigration order – Step #3 NetWeaver Infrastructure

§ No Magic Order for NW migration – Best

Approach - Start from bottom up§ Before you start, make you have a service to

server mapping – this is important to know what will come over as you migrate

§ Target turning up different layers in the new Vblock architecture iteratively – allows for tier testing

§ If you are using Business Intelligence or Knowledge management modules – migrate after Core Netweaver components are in place

21

Migration PhasesMigration order – Step #4 Core business services

§ Migration order will vary from deployment to deployment

§ Start with core components§ Once core is complete move to

extension set if in use§

22

Migration PhasesExecution

BESTUSE

CASE

BESTUSE

CASE

PROSPROS

●Clean Software Install

●P2V ●Cloning●VMotion

●SAP Software Migration Tools

●Data ●Replication

Full advantage ofVblock systemtemplates for

replication

Captures all ofcurrent system

settings

In-line, no-downtime migration

Designed specifically move

applications & logic

Allows forgeographicseparation

Labor Intensive Replicates existingconfiguration issues

Introducesoverhead whileVMotion occurs

Moves only SAP A lot of manualintervention & test

Current operationplatform is notsupported byVblock sytems

Many 3rd-partyapp/connections

Currently virtualized Landscape will useboth VMS & bare

metal configs

Security and/orgeography do notallow co-located

CONSCONS

23

Migration PhasesCompute

CPU

§ Underestimate CPU Requirements – In physical world – you need to forecast future for future requirements. Start small and add virtual CPUs as needed

§ Large Payloads Cores = vCPUs – for heavy workloads size for worst case situations and make each core a virtual CPU

Memory§ Large Payloads Physical Memory = Virtual Memory – Just like CPUs – for larger systems do

not over subscribe memory̶ Size virtual memory to be the same size as physical memory̶ Set reservations so they don’t exceed physical memory foot prints

§ Do not Disable balloon driver – you may think this is wise, but it can impact performance§ Deduplicate - ESX Server memory page sharing generates appreciable memory savings

24

Migration PhasesNetwork

§ Larger Configurations require more networks – Separate network payloads based on network communication types

– Heavy upstream/downstream workloads – configure virtual switches to support both private/public networks

– Use standard recommendations for VMotion and VMware administration networks

§ More NICs equal better performance – allocate a minimum of 4 vNICs to each ESX server and ensure that they are spread across multiple physical NICs

§ Choose the right tags – Using Virtual Switch Tagging (VST) gives you the best bang for your buck in a consolidated Vblock switching architecture

§

25

Migration PhasesStorage

§ Take advantage of the converged architecture – SAP is I/O intense – take advantage of FCoE and maximize throughput channels

§ Use multiple vHBA paths - maximize redundancy between storage and compute using both A & B SANS

§ Mix and Match Storage Configurations – using both EMC and VMware data management products based on tiering and VM/BM configurations

§ Spread out your LUNs – Regardless of VM/BM – spread I/O intensive LUNs across multiple controllers & disks

§

26

Hopefully What You Learned

• Vblock value in a unique architecture delivering performance and scalability

• Fast deployment, simplified operations, low risk

• Mixed workload capable for flexibility and lower TCO

Thank you.

27

Learn more about CI & VCE Data Center Readiness Workshopwww.vce.com/sap

Corporate HeadquartersMaxfeldstrasse 590409 NurembergGermany

+49 911 740 53 0 (Worldwide)www.suse.com

Join us on:www.opensuse.org

28

Unpublished Work of SUSE. All Rights Reserved.This work is an unpublished work and contains confidential, proprietary and trade secret information of SUSE. Access to this work is restricted to SUSE 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 SUSE. 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. SUSE 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 SUSE products remains at the sole discretion of SUSE. Further, SUSE 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 SUSE 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.