continuous data protection in business critical sap environment miikka vainionpää manager,...

21
Continuous Data Protection in business critical SAP environment Miikka Vainionpää Manager, Application & Integration Platforms [email protected] 1

Upload: jewel-carter

Post on 18-Dec-2015

214 views

Category:

Documents


0 download

TRANSCRIPT

Continuous Data Protection in business critical SAP environmentMiikka VainionpääManager, Application & Integration [email protected]

1

Table of Content

•Kemira overview

•OneKem overview

•Business requirements• Busines Impact Analysis

• RTO/RPO requirements

•Technical Solution

•Kemira ERP DR plan

2dd.mm.yyyy OneKem_Platform_Solution_View_.ppt

Kemira Overview

3dd.mm.yyyy OneKem_Platform_Solution_View_.ppt

Kemira is a 2.8B EUR global chemical company

Sites: ~140 Countries: 40 Personnel: 9400

North AmericaSales: 632 MEUR (23%)Personnel: 1420 (15%)

North AmericaSales: 632 MEUR (23%)Personnel: 1420 (15%)

South AmericaSales: 152 MEUR (5%)Personnel: 425 (5%)

South AmericaSales: 152 MEUR (5%)Personnel: 425 (5%) Europe, Middle East and Africa

Sales: 1,931 MEUR (68%)Personnel: 7077 (75%)

Europe, Middle East and AfricaSales: 1,931 MEUR (68%)Personnel: 7077 (75%)

Asia PacificSales: 117 MEUR (4%)Personnel: 483 (5%)

Asia PacificSales: 117 MEUR (4%)Personnel: 483 (5%)

*) 1 euro is ~ 1,35 USD

(2008 figures)(2008 figures)

Kemira company presentation 5

Sales by business segment and global market

2008 Total: EUR 2.8 Billion

Vision │ A leading water chemistry company

Target customers

Focus on customers operating in water-intensive industries

Water quality and quantity management

Water use, reuse, recycling, and recovery

Bringing value to customers’ processes

Improvement of energy, water, and raw material efficiency

Combining understanding of industrial processes and customer needs with a sustainable product portfolio and application expertise

Water footprint is becoming more important

A product’s water footprint consists of the total use of water in its value chain. For instance, the water footprint of beer also includes the water needed to grow barley. For industrial products, the water footprint is evaluated against the product's value – on average, 80 l / dollar. Source: www.waterfootprint.org

Decreasing the water footprint will be even more important with the increasing water shortage

Paper

10 l of water for a

sheet of A4 paper

Beer

75 l of water for a glass of beer

Leather

16,000 l

of water / kg

Industrial products

8 million l of water per

vehicle (value: $100,000)

OneKem Overview

8dd.mm.yyyy OneKem_Platform_Solution_View_.ppt

Firstname Lastname, Segmentname (optional) 04/18/23 9

OneKem Solution

ERP landscape

BW landscape

SCM landscape

HCM landscape

CRM landscape

PI landscape

Portal landscape

WebSAPConsole landscape

Vertex landscape

Solution Manager landscape

Archiving landscape

Scanning landscape

Disaster Recovery landscape

Us

er

Inte

gra

tio

nP

roc

es

s

Inte

gra

tio

n

SAP ERP

FI/CO

SAP HCM

MM

Manual Interfaces

Manual Interfaces

PM PP SD

WWI ServerExpert Rules(SAP EHS)

SAP SolutionManager

(Monitoring/CUA)

IXOS(archiving)

System 1 System 2 System 3 System 5 …System 4

SAP BI

Info

rma

tio

n

Inte

gra

tio

n

...

SAP Portal

Web BrowserBeX reportsSAP GUI (incl.standard reports)

QM EHS

SAP eXchange Inf rastructure (PI)

SAP SCM

WebSAPConsole

Bar code reader

KofaxScanning/OCR

Workflow SAP CRM

Vertex(tax calculation)

Business Requirements

10dd.mm.yyyy OneKem_Platform_Solution_View_.ppt

Business Impact AnalysisQuantitative Cost Estimate Cost after

2 hoursCost after12 hours

Cost after24 hours

Cost after48 hours

Cost after72 hours

Cost after1 week

One Time Cost

Production outage

Lost Sales

Lost customer

Staff

Expenses of hardware are not counted in to cost estimate.

Total (Estimated cost of system crash)

Qualitative Estimate including e.g. company brand image, legal/compliance issues, etc. Select that applies.

24 h 48 h 72 h 1 week More than a week

Critical (15 mEUR)

Remarkable significance

Great significance (2 mEUR)

Significant (1mEUR)

Somewhat significant (100 000 EUR)

No significance (1 000 EUR)

Criticality Classes – RTO/RPO Requirements

RTO (max) RPO (max)

Availability% (excluding planned downtime)

Unplanned downtime per year (h)

Planned downtime per year (h)

Business Critical+ 2h ~0h 99,95 % 4,35 60Business Critical 2h ~0h 99,95 % 4,35 60Important 24h 3h 99,50 % 43,44 72Standard 72h 24h 99 % 86,88 72Economy 120h 168h 96 % 347,52 72

Clustered solution between DCs

MS SQL Server - DB Recovery modell

EMC Continuous Data Protection

Mirror between disk systems/DCs

EMC RM/Snapshot Backup

Disk Backup(primary restore from disk)

Tape Backup(Off-line)

Business Critical+ Yes Full Yes Yes Yes Yes YesBusiness Critical Yes Full No Yes Yes Yes YesImportant Yes/No Full No No Yes Yes YesStandard No Full/Simple No No No Yes YesEconomy No Full/Simple No No No No Yes

RTO: Targeted amount of time to restart a business service after a disaster event

RPO: Amount of data lost from failure, measured as the amount of time from a disaster event

Technical Solution

13dd.mm.yyyy OneKem_Platform_Solution_View_.ppt

Technical solution

DC-4 DC-2

SANSAN Swicthes

RevoverPoint Appliance

StorageCDP

JournalSnapviewAnalyzer MirrorView/CRR

Host

Host

Host

Host

DC-1

Tape library

Backup server

StorageCRR

JournalSnapviewAnalyzer

ReplicationManager

Host

EMC RecoverPoint/SE:•4 x RecoverPoint Appliances

•Clustered (2 appliances/DC)•CDP (Continuous Data Protection, local)•CRR (Continuous Remote Replication, remote)•Journal (I/O-based change/transaction log, retention time 1 week)•Capacity license: 4 TB CDP + 4 TB CRR

•2 x disk enclosures DAE4P + 15x300GB FC4 15k allocated to Journal•Clariion splitter is used for I/O splitting

Backup:•Dell ML6020 Tape Library

•2 x LTO4 FC tape drives•2 x LTO3 FC tape drives

•Dedicated Backup LAN•EMC Networker

Application Platform:• SAP WAS 7.00 (ABAP/Java)

Database:• SQL Server 2005 Enterprise Edition (64-bit) SP01/SP02

Operating System:• MS Windows Server 2003 R2 Enterprise x64 Edition

SP01/SP02

Hardware:• 64 physical servers• Dell PE 2950 2 x Quad-Core Xeon 2.66/3.16 GHz• Dell PE 2850 2 x Dual-Core Xeon 2,8 GHz• Dell PE 6850 4 x Dual-Core Xeon 3,0 GHz• RAM 12-64 GB

Storage:• 2 x EMC CX4-480 disk systems

• 14 x disk enclosures DAE4P + 15x300GB FC4 15k

• 2 x disk enclosures DAE4P + 15x1TB SATA 7,2k

• 4 x EMC Racks (40U)• Software

• MirrorView/S for unlimited syncronous mirroring• SnapView for for unlimited snapshots and clones• Quality of Service Manager to guarantee the

certain performance for most critical applications• Analyzer for performance monitoring• Replication Manager enables MS SQL Server

consistent backups. It manages point-in-time replication technologies and centrally automate mounting, dismounting, scheduling, and expiration of replicas.

SAN:• 8 x Brocade DS5100 SAN switchs

• 32 ports activated/SAN switch

Continuous Data Protection

15dd.mm.yyyy OneKem_Platform_Solution_View_.ppt

Nightly Backup: Recovery once every 24 hours

RECOVERY GAP

Scheduled Snapshots: Recovery once every 3 hoursRECOVERY

GAPRECOVERY

GAPRECOVERY

GAP

RecoverPoint: Instant recovery to any point in time

Check-point

Patch Post-Patch

Cache Flush

QtrlyClose

HotBackup

Check-point

Pre-Patch

UNLIMITED RECOVERY POINTS, APPLICATION BOOKMARKS

Time

Synchronous mirroring between local arrays: Recover image, but susceptible to logical corruption

Any Point-in-Time Recovery

Traditional recovery methods

Nightly backups, snapshots, mirrored images plagued by time gaps, corruption

RecoverPoint

Recovery to any point in time– Mount image to any host in SAN– Full read/write access to image

without protection loss

Use recovered image for a variety of purposes– Operational recovery– Backup, testing, or decision support– Reporting

Grouping for a Consistent View

Allows application recovery to be tiered by service level

• Multiple volumes per group• Mixed recovery point objectives

within same infrastructure

Provides independent replication controls

• Recover by group, locally or remotely

• Start/stop by group

Enables grouping of optimization • Importance• Resource usage• Recovery point and recovery time

objectives

Group 3

Group 1

Group 2

E-mail CRR

CRRCDPSCM

CRROE

CRRCRM CDP

EMC Continuous Data Protection

RecoverPoint CDP –RM + Bookmarks

DC 1DC 4

SAP DATAMirror

CDP

RecoverPoint CRR

Critical+ DC 2

Networker Backup

Journal

JournalSAP DATAJournal

SAP DATA

SAP DB SAP CSMS Cluster

Transaction log backup Networker Backup

B2D

SAP DB SAP CS

Networker Backup Server

ERP DR Plan

19dd.mm.yyyy OneKem_Platform_Solution_View_.ppt

ERP DR PlanTable of Contents 1 Introduction...................................................................................................4

1.1 Solution Overview ........................................................................................................4 1.2 Terms & Abbreviations ................................................................................................ 4 1.3 Disaster Determination ................................................................................................ 5 1.4 System Continuity Assurance Methods, Recovery Strategy and Principles ..........5 1.5 System Description and Architecture.........................................................................7 1.6 Main Stakeholders........................................................................................................9 1.7 Disaster Communication Strategy............................................................................10 1.8 Liability Requirements ............................................................................................... 10 1.9 Assumptions...............................................................................................................10 1.10 Dependencies to Other Recovery Plans.................................................................11 1.11 References ................................................................................................................11

2 Course of Recovery ....................................................................................12

2.1 Disaster Recovery Handling...................................................................................... 12 2.2 Disaster Recovery Roles and Responsibilities........................................................ 13 2.3 RACI matrix of teams and phases.............................................................................15

3 Disaster Recovery Process ........................................................................16

3.1 From Incident to Disaster (Steps 1 – 5) ....................................................................16 3.2 Error Categorization and Root Cause Determination (Step 6) ............................... 18 3.3 Activating Alternate Procedures (Steps 7 - 8).......................................................... 18 3.4 Execute Recovery (Steps 9 – 12) ..............................................................................19 3.5 Returning to Normal Operation (Steps 11 – 16)....................................................... 21

4 OneKem ERP Recovery Scenarios ............................................................23

4.1 Media/Hardware Failure (technical failure)............................................................... 23 4.2 Lost Data (logical failure)........................................................................................... 24 4.3 Database Block Corruptions ..................................................................................... 27

5 Appendixes..................................................................................................29

Appendix 1 Error Categorization ....................................................................................29 Appendix 2 Alternate Procedures................................................................................... 32 Appendix 3 Preparations for recovery............................................................................33 Appendix 4 Recovery Phases ......................................................................................... 35 Appendix 5 Normal operations ....................................................................................... 46 Appendix 6 Operational Instructions for Recovery....................................................... 47 Appendix 7 OneKem ERP Technical details ..................................................................56

Thank you!

21dd.mm.yyyy OneKem_Platform_Solution_View_.ppt