SAP Saber Carving SAP into Separate Landscapes for Company Split. Van Vi and Rick Jones

[ SAP Saber Carving SAP into Separate Landscapes for Company Split Van Vi and Rick Jones [ Introductions Rick Jones Marathon Petroleum Corporation...
Author: Marlene Nichols
6 downloads 0 Views 2MB Size
[

SAP Saber Carving SAP into Separate Landscapes for Company Split

Van Vi and Rick Jones

[ Introductions Rick Jones Marathon Petroleum Corporation SAP Architect [email protected]

Van Vi SAP America, Inc. SAP Certified Professional Platinum Consultant [email protected]

Real Experience. Real Advantage.

[ Learning Points  How to quickly provision infrastructure to support an SAP rapid and agile deployment  Delivering SAP high availability at reasonable costs with low complexity  SAP Virtualization at Marathon Petroleum – the good and the not so good (lessons learned)

Real Experience. Real Advantage.

3

[ Agenda •

MPC Overview



SABER Project Overview



Why Windows/SQL Server?



Why Virtual?



Sizing Approach



MPC Virtual Environments



High Availability Options



Installation Method Used



VTO – Results



VMware Feature Testing



Recommendations (SAP/Windows)

Real Experience. Real Advantage.

[ Marathon Petroleum Corporation Overview  On January 13, 2011, Marathon Oil‟s board of directors announced they had approved plans for moving forward with the spin-off of the Downstream business.  Marathon Oil Corporation – Houston, TX (MRO - Upstream):  Operates as an international energy company with operations in the United States, Canada, Africa, the Middle East, and Europe.  Operations includes Exploration and production, Oil Sands Mining, and Integrated Gas.

 Marathon Petroleum Corporation Findlay, OH (MPC – Downstream):     

125 years in business 5th largest U.S. refiner Fortune 100 company Approximately 1,375 Speedway convenience stores More than 5,000 Marathon Brand retail outlets

Real Experience. Real Advantage.

[ SABER Project Introduction Marathon Petroleum Corporation (MPC) split from Marathon Oil Corporation in July 2011. To sustain it’s current business operations on SAP, MPC will need to build out a new SAP Solution: • • •

MPC is moving from AIX 5.3/6.1 to Windows 2008 R2 and Oracle 10.2.0.4 to SQL Server 2008 R2 6 * HP ProLiant BL685c G7, 4 Processors / 48 Cores / 48 Threads, AMD Opteron Processor 6176, 2.3 Ghz, 512GB RAM 12 * HP ProLiant BL485c G7, 4 Processors / 24 Cores / 24 Threads, AMD Opteron Processor 6176, 2.3Ghz, 256GB RAM

Real Experience. Real Advantage.

Project Information and Timeline: • Day 1: Q3‟ 2011 • NetWeaver BPC 7.5 (New Install) • NetWeaver BW 7.01 (New Install) • Solution Manager 7.01 (New Install) • Day 2: Q1‟2012 • ECC 6.0 (OS/DB Migration) • NetWeaver Portal (OS/DB Migration) • Pecaso (OS/DB Migration) • GRC AC 5.3 (New Install) • GRC PC 3.0 (OS/DB Migration) • PI 7.3 (New Install) • BI 4.x (New Install) • HP QC (New Install) • ARIS (New Install) • Day 3: Post Day 2 to ~ 2013 • Adding additional functionality • Adding additional SAP Product (e.g. SRM, MDM, BW Java….)

[ Why Windows? Summary Point For Decision Making: Windows

UNIX

LINUX

MPC Experience with OS

High

Low

Low

Existing Partnership with Supplier

Yes

No

No

VMware Support

Yes

No

Yes

Licensing Cost

Medium

High

Low

Infrastructure Cost

Low

Medium/High

Low

MPC Datacenter Consistency

Yes

No

No

Real Experience. Real Advantage.

[ Why SQL Server? Summary Point For Decision Making: SQL

Oracle

Licensing Cost for multicore processor

Low

High

Infrastructure Cost

Same

Same

MPC experience with DB

High

Medium

Windows native clustering

Yes

No

Virtualization Support

High

Medium (OSS note 1173954)

Established Tier 1 History

Real Experience. Real Advantage.

Moderate

Long

[ Windows / SQL Server Quick Facts More than 30,000 SAP installations are on SQL Server and more than 65,000 are on Windows Server. 

Over 400 SAP customers have a productive SQL server DB size of over 1TB. 

Several Microsoft SQL Server and SAP customers have SAP ERP productive DB sizes of over 1TB. 

Microsoft Microsoft SQL SQL Server Server and and SAP SAP customers customers are are running running SAP SAP ERP ERP with with over over 3,000 3,000 concurrent concurrent users. users.

http://blogs.msdn.com/b/saponsqlserver/archive/2011/10/01/sap-on-sql-general-update-for-customers-amp-partners-october2011.aspx

Real Experience. Real Advantage.

[ Why Virtual? MPC Drivers for Virtualization:  Shorter Deployment Cycle (High Priority):  Have existing older x86 servers for immediate start for SAP installations  Provide flexibility in relocating SAP to different data center (FDY DC ready but CYL-DC was not)  Faster provisioning of Virtual Machines  x86 Server Hardware independency – Decoupling software from Hardware  Faster procurement time for commodity hardware  Datacenter/Infrastructure consistency – Virtualization on VMware.  Simplification for HA and DR  SAP and Microsoft Supported

 Cost

http://www.vmware.com/files/pdf/partners/sap/vmware-sap-virtualization-tco-roi-article-en.pdf Real Experience. Real Advantage.

[ Sizing Approach Since this is not a new installation but rather categorize more of a migration project, decision was to calculate current capacity and match it on x86 HW.  IBM provided number of SAPS for each LPAR for existing.  MPC IT HW building blocks were “HP ProLiant BL685c G7 Server Blade, four AMD Opteron 6176 12-core/2.3Ghz processors per blade, 512GB RAM per blade” as the SAP Resource Pool.  Leverage similar publish SAP benchmarks on similar hardware to determine SAPs per core ~ 1000 SAPS/core (Validated with HP)

Real Experience. Real Advantage.

[ MPC SAP Virtualized Production Landscape Hostname: M5780 SAP CI BW (BWP) vCPU: 4, RAM: 16 GB

Hostname: MPS5730 SAP CI ECC (ECP) vCPU: 4, RAM: 16 GB

Hostname: MPS5751 SAP DI EPP (EPP) vCPU: 4, RAM: 16 GB

Hostname: MPS5711 SAP DI PI (PIP) vCPU: 4, RAM: 16 GB

Hostname: MPS5790 SAP Plat. BI 4.x vCPU: 2, RAM: 8 GB

Hostname: MPS5781 SAP DI BW BWP) vCPU: 4, RAM: 16 GB

Hostname: MPS5731 SAP DI ECP (ECP) vCPU: 4, RAM: 16 GB

Hostname: MPS5756 SAP WD EP (EPP) vCPU: 1, RAM: 4 GB

Hostname: MPS5716 SAP WD PI (PIP) vCPU: 1, RAM: 4 GB

Hostname: MPS5791 SAP Plat. BI 4.x vCPU: 2, RAM: 8 GB

Hostname: MPS5789 SAP DB BW (BWP) vCPU: 8, RAM: 64 GB

Hostname: MPS5732 SAP DI ECP (ECP) vCPU: 4, RAM: 16 GB

Hostname: MPS5759 SAP DB EP (EPP) vCPU: 4, RAM: 32 GB

Hostname: MPS5717 SAP SCS PI (PIP) vCPU: 1, RAM: 4 GB

Hostname: MPS5792 SAP Web BI 4.x vCPU: 2, RAM: 8 GB

Hostname: MPS5760 SAP BPC .NET vCPU: 4, RAM: 16 GB

Hostname: MPS5736 SAP WD ECC (ECP) vCPU: 1, RAM: 4 GB

Hostname: MPS5800 SAP CI GRC PC (GPP) vCPU: 4, RAM: 16 GB

Hostname: MPS5719 SAP DB PI (PIP) vCPU: 4, RAM: 32 GB

Hostname: MPS5799 SAP DB. BI 4.x vCPU: 4, RAM: 16 GB

Hostname: MPS5700 SAP CI SolMan (SMP) vCPU: 4, RAM: 16 GB

Hostname: MPS5739 SAP DB ECC (ECP) vCPU: 8, RAM: 64 GB

Hostname: MPS5809 SAP DB GRC PC (GPP) vCPU: 4, RAM: 16 GB

Hostname: MPS5810 SAP CI GRC AC (GAP) vCPU: 4, RAM: 16 GB

Hostname: MPS5840 SAP CI/DB PEC (PCP) vCPU: 4, RAM: 16 GB

Hostname: MPS5709 SAP CI SolMan (SMP) vCPU: 4, RAM: 16 GB

Hostname: MPS5750 SAP CI EP (EPP) vCPU: 4, RAM: 16 GB

Hostname: MPS5710 SAP CI PI (PIP) vCPU: 4, RAM: 16 GB

Hostname: MPS5819 SAP DB GRC DB (GAP) vCPU: 4, RAM: 16 GB

Hostname: MPS5820 ARIS .NET Bus Svr vCPU: 4, RAM: 16 GB

Hostname: MPS5821 ARIS .NET Bus Pub vCPU: 4, RAM: 16 GB

Hostname: MPS5828 ARIS DB vCPU: 4, RAM: 16 GB

Hostname: MPS5822 HP QC .NET vCPU: 4, RAM: 16 GB

Hostname: MPS5829 HP QC DB vCPU: 4, RAM: 16 GB

………………………. ………………………. ……………………….

SAP Resource Pool Capacity: (vCPU – 240 / RAM – 2560 GB) SAP Resource Pool Used: (vCPU – 126 / RAM – 600 GB)

Real Experience. Real Advantage.

5 x HP Proliant BL685c VMware vSphere 4.1 Update x CPU: 4 x 12 cores 2.3 GHz, AMD Opteron 6176 RAM: 512 GB 12 x HP Proliant BL485c VMware vSphere 4.1 Update x CPU: 2 x 12 cores 2.3 GHz, AMD Opteron 6176 RAM: 256 GB A total of 18 (12xBL485 + 6xBL685) physical servers in one Virtual Center Guest OS of all virtual machines is Windows 2008 R2 EE DB Servers run with SQL Server 2008 R2 EE

[ MPC SAP Virtualized Non-Production Landscape Installation Types: •

Non Production landscapes include SBX, DEV, TRN, and QA ( BW, BPC .Net, Portal, ECC, BI 4.x)



SBX, DEV, and TRN sized down and installed as central system.



QA are sized like production and installed as distributed system.

SAP BW VM#: 6 vCPU: 40 ,RAM:144 GB

SAP BPC .NET VM#: 4 vCPU: 8, RAM: 32 GB

SAP PI VM#: 7 vCPU: 22 ,RAM:104 GB

SAP SolMan VM#: 1 vCPU: 4, RAM: 16 GB

SAP Portal VM#: 7 vCPU: 25 ,RAM:116 GB

SAP ECC VM#: 8 vCPU: 33, RAM: 164 GB

HP Load Runner VM#: 2 vCPU: 6 ,RAM:24 GB

SAP Pecaso VM#: 1 vCPU: 4, RAM: 16 GB

SAP TDMS VM#: 1 vCPU: 4 ,RAM:16 GB

SAP BI 4.x VM#: 7 vCPU: 22, RAM: 88 GB

SAP GRC PC VM#: 3 vCPU: 12 ,RAM: 48 GB

SAP GRC AC VM#: 1 vCPU: 4, RAM: 16 GB

ARIS VM#: 3 vCPU: 12 ,RAM: 48 GB

HP QC VM#: 2 vCPU: 8, RAM: 32 GB

………………………………. ………………………………. ……………………………….

………………………………. ………………………………. ……………………………….

SAP Resource Pool Capacity: (vCPU – 288 / RAM – 3072 GB) SAP Resource Pool Used: (vCPU – 204 / RAM – 864 GB)

Real Experience. Real Advantage.

6 x HP Proliant BL685c VMware vSphere 4.1 Update x CPU: 4 x 12 cores 2.3 GHz, AMD Opteron 6176 RAM: 512 GB 12 x HP Proliant BL485c VMware vSphere 4.1 Update x CPU: 2 x 12 cores 2.3 GHz, AMD Opteron 6176 RAM: 256 GB A total of 18 (12xBL485 + 6xBL685) physical servers in one Virtual Center Guest OS of all virtual machines is Windows 2008 R2 EE DB Servers run with SQL Server 2008 R2 EE

[ MPC Aggregate Server Requirements for SAP Hosting

Real Experience. Real Advantage.

[ MPC Datacenter Design (Findlay / Lebanon)

Real Experience. Real Advantage.

[ MPC Datacenter Design (Findlay / Lebanon)

Real Experience. Real Advantage.

[ MPC Datacenter Design (Findlay / Lebanon)

Real Experience. Real Advantage.

[ High Availability Options with Physical/Windows SAP Single Point of Failures:  SAP DB  SAP CI with incorporated Enqueue/Message Server  SAP stand-alone Enqueue/Message Server

Examples of some HA MSCS/VCS Configuration Challenges of Physical High Availability Solutions •

Additional cost in terms of hardware

Additional cost in terms of Clustering software and support •

OR



Adds additional complexity to environment

Then multiple by number of systems in Production and another set in QA.

Real Experience. Real Advantage.

[ High Availability Options with VMware / Windows SAP Single Point of Failures:  SAP DB  SAP CI with incorporated Enqueue/Message Server  SAP stand-alone Enqueue/Message Server

Possible High Availability Solutions: SAP Component

HA Capability

Features

Comments

DB, CI, ASCS, SCS

VMware High Availability

• Protection against server failure • Restart of VM on another ESX host • VMware out of the box configuration

• No application level monitoring • Application not available during failover • No ERS replication during CI, ASCS, SCS failover • No Auto restart of SAP instance after failover.

DB, CI, ASCS, SCS

Microsoft Cluster (MSCS)

• Protection against server failure • Application monitored by cluster resource • Enables continuous availability of SAP locks due to ERS • No guest OS boot-up during failover

• No VMotion of clustered VMs • Clustered VMs cannot be part of HA/DRS. • Application not available during failover • Increase complexity

ASCS, SCS

VMware Fault Tolerance

• Protection against server failure • Continuous availability of application. • VMware out of the box configuration

• No application level monitoring • Current vSphere 4.1 / 5.0 only support 1 vCPU.

Real Experience. Real Advantage.

[ High Availability Options with VMware / Windows VMware HA

 VMware HA continuously monitors all ESX Server hosts in a cluster and detects failures  VMware HA agent placed on each host maintains a heartbeat with the other hosts in the cluster  Each server sends heartbeats to the others servers in the cluster at five-second intervals. If any servers lose heartbeat over three consecutive heartbeat intervals, VMware HA initiates the failover action of restarting all affected virtual machines on other hosts.

Real Experience. Real Advantage.

[ High Availability Options with VMware / Windows VMware HA – Extended (Symantec Application HA Plug-in) VMware integrated solution from Symantec

Real Experience. Real Advantage.



Agents for DB and SAP installed in VM provide service monitoring and restart capability



Integrated to vCenter via VMware HA API



Application visibility from vCenter console



Bridges gap between VMware HA and in-guest cluster solutions

[ High Availability Options with VMware / Windows Clustering Software  Only MSCS is supported by VMware. VCS support is by Symantec.  Protecting SAP SPOF with MSCS on two Virtual Machine on two ESX server - SAP does not support MSCS on two Virtual Machines on the same ESX server (OSS Note 1374671 and 1613999)  MSCS clustered virtual machines cannot be migrated via VMotion or be part of a DRS cluster.  Installation similar to physical host  Monitoring agents for SAP and DB

Real Experience. Real Advantage.

[ High Availability Options with VMware / Windows VMware Fault Tolerance  Enables a transparent failover with no disruptions of services in the event of hardware failures.  Works with existing VMware HA or VMware DRS clusters and can be simply turned on or turned off for virtual machines.  Limitation is the Fault Tolerance VM can only be assigned 1 vCPU.

Real Experience. Real Advantage.

[ SAP with VMware High Availability Scenarios - Compare SAP in VM Scenario

ESX Server Protection

SAP Application Protection

Minimize OS Patching

Cost / Complexity

VMware HA

Yes

No

No

Low

VMware HA + Symantec AppHA

Yes

Yes

No

Med

VMware FT

Yes

Yes*

No

Low

Clustering Software

Yes

Yes

Yes

High

Final choice • Depends on business requirements • Can business tolerate planned downtime for software maintenance? • Trade-off: cost/complexity vs availability * - Limitation of only 1 vCPU can be assigned to VM Real Experience. Real Advantage.

[ Installation Selections: Meet Current Business SLA Requirement:  Datacenter Outage: RTO – 72 hours / RPO – 24 hours  Local Server Outage: No HA implemented in as-is

Leverage Overall IT strategy on VMware for SAP:  Use Hypervisor capability for HA (e.g.VMware HA and Fault Tolerance)  Need to be able to leverage Site Recovery Manager and EMC replication for DR  Reduce complexity and limit the number of vendors in the solution (e.g. MS, SAP,VMware)

MSCS solution was discouraged because of their previous experience and reduced VMware capabilities Low High Symantec Application HA not considered because of another vendor support in the stack

Real Experience. Real Advantage.

[ Installation Types Automatic Failover

Automatic Failover + Fault Tolerance

 Distributed Installation  Central Instance in one VM  Dialog Instance in one VM  DB Instance in one VM  All VMs enabled for VMware HA

 Distributed Installation  Central Instance in one VM  Dialog Instance in one VM  DB Instance in one VM  Standalone ASCS or SCS in one VM  Web dispatcher in one VM  All VMs enabled for VMware HA  ASCS, SCS, WD VMs enabled for Fault Tolerance (Need to stress test)

Note: All VMs are VMware HA enabled – SBX, DEV, QA, TRN, and Prod. Real Experience. Real Advantage.

[ Installation Types Installation Standards Defined:

 Use virtual names for installation  “sapinst.exe SAPINST_USE_HOSTNAME = sapci00bwp”  Virtual naming standards for SAP Components (SAPXX##