FUT92716 SUSE Linux Enterprise Server for SAP Applications Roadmap

Transcription

1 FUT92716 SUSE Linux Enterprise Server for SAP Applications Roadmap Wednesday, Nov 9, 10:00 AM - 11:00 AM Thursday, Nov 10, 4:30 PM - 5:30 PM Hannes Kühnemund SUSE Product Management

2 SUSE Linux Enterprise Server The Recommended and Supported operating system for SAP applications and HANA The First Linux Distribution for on x86-64 servers The Only Linux for on Power Systems 2

3 SUSE Linux Enterprise Server for SAP Applications The Leading Linux Platform for Boost Performance for mission-critical SAP applications Reduce downtime of critical operations Minimize time and effort to deploy SAP landscapes 3

4 SUSE Linux Enterprise Server for SAP Applications 12 SP1 Latest release for x86-64 servers 24x7 Priority Support for SAP Extended Service Pack Support 18 Month Grace Period Page Cache Management Installation Wizard Firewall Resource Agents SUSE Linux Enterprise Server SLE High Availability & SAP NetWeaver SAP specific update channel 24x7 Priority Support for SAP 4

5 Attention! 5

6 Service Pack 2

7 Service Pack 2 Remote Disk Encryption Management 1 SUSE Connect 2 Compatibility High Availability 4 3 Future Product Direction 5 7

8 Service Pack 2 Remote Disk Encryption Management 1 SUSE Connect 2 Compatibility High Availability 4 3 Future Product Direction 5 8

9 Remote Disk Encryption Management Why using disk encryption? How does the setup process look like? How does it affect daily work when enabled? How to avoid usability pitfalls? 9

10 Remote Disk Encryption Management Why using disk encryption? How does the setup process look like? How does it affect daily work when enabled? How to avoid usability pitfalls? 10

11 Remote Disk Encryption Management Why using disk encryption? How does the setup process look like? How does it affect daily work when enabled? How to avoid usability pitfalls? 11

12 Remote Disk Encryption Management Why using disk encryption? How does the setup process look like? How does it affect daily work when enabled? How to avoid usability pitfalls? 12

13 cryptctl - Keyserver concept 13

14 Remote Disk Encryption Management - Keyserver 14

15 Remote Disk Encryption Management - Keyserver 15

16 Remote Disk Encryption Management - Keyserver 16

17 Remote Disk Encryption Management - Keyserver 17

18 Remote Disk Encryption Management - Keyserver 18

19 Remote Disk Encryption Management - Keyserver 19

20 Remote Disk Encryption Management - Keyserver 20

21 Remote Disk Encryption Management - Keyserver 21

22 cryptctl - Keyserver concept 22

23 cryptctl Client setup 23

24 Remote Disk Encryption Management - Client 24

25 Remote Disk Encryption Management - Client 25

26 Remote Disk Encryption Management - Client 26

27 Remote Disk Encryption Management - Client 27

28 Remote Disk Encryption Management - Client 28

29 Remote Disk Encryption Management - Client 29

30 Remote Disk Encryption Management - Client 30

31 Remote Disk Encryption Management - Client 31

32 Remote Disk Encryption Management - Client 32

33 Remote Disk Encryption Management - Client 33

34 Remote Disk Encryption Management - Client 34

35 cryptctl - Keyserver concept 35

36 Remote Disk Encryption Management Why using disk encryption? How does the setup process look like? How does it affect daily work when enabled? How to avoid usability pitfalls? 36

37 Service Pack 2 Remote Disk Encryption Management 1 SUSE Connect 2 Compatibility High Availability 4 3 Future Product Direction 5 37

38 What does your SAP landscape look like? SAP Business Application Software In Memory database SUSE Linux Operating System 38

39 What does your SAP landscape look like? SAP Business Application Software In Memory database SUSE Linux Operating System 39

40 Introducing SUSE Connect SAP Business Application Software In Memory database SUSE Linux Operating System 40

41 Service Pack 2 Remote Disk Encryption Management 1 SUSE Connect 2 Compatibility 3 High Availability 4 Future Product Direction 5 41

42 Joining a Windows AD Domain winbind (old) sssd (old) 42

43 Service Pack 2 Remote Disk Encryption Management 1 SUSE Connect 2 Compatibility High Availability 4 3 Future Product Direction 5 43

44 Overview supported SR scenarios SAP NetWeaver Manual Failover Simple Stack Enqueue Replication Combined Stack ScaleUp Manual Failover Performance Optimized Cost Optimized Multitenant Database Containers Storage Replication Public Cloud Others ScaleOut Auto-Host Failover Manual Takeover Performance Optimized Storage Replication Public Cloud Others 44

45 Overview supported SR scenarios SAP NetWeaver Manual Failover Simple Stack Enqueue Replication Combined Stack ScaleUp Manual Failover Performance Optimized Cost Optimized Multitenant Database Containers Storage Replication Public Cloud Others ScaleOut Auto-Host Failover Manual Takeover Performance Optimized Storage Replication Public Cloud Others 45

46 HA / DR Scale-Out Comparison Auto-Host Failover Cost Downtime Comment Manual Performance Optimized Storage Replication Public Cloud How does each scenario affect cost and downtime? Other 46

47 Scale-Out: Auto Host Failover Cluster 2 Usage: n/a Data pre-load on Secondary: No Cluster 1 Fail decision: SAP Auto-Host Failover Fail process: reaction time: Fast speed: Automated by Slower since failed node must completely loaded into memory of standby (PR1) primary PR1 A scale-out database consists of multiple nodes and SAP HANA instances. Each worker ( ) node has it's own data partition. Standby ( ) nodes do not have a data partition. 47

48 Scale-Out: Manual Cluster 2 Usage: Dedicated Data pre-load on Secondary: Yes decision: Manual monitoring and post-mortem analysis vip Cluster 1 Manual Cluster 2 process: Manual reaction time: Variable (PR1) primary PR1 System Replication PR1 (PR1) secondary speed: Fast since data pre-loaded 48

49 Available with SLES for SAP Applications 12 SP2 Scale-Out: Performance Optimized Cluster 2 Usage: Dedicated Data pre-load on Secondary: Yes decision: Fully automated by SUSE cluster solution vip Cluster 1 pacemaker Cluster 2 active/active process: reaction time: Fully automated by SUSE cluster solution Fast due to pacemaker heartbeat (PR1) primary PR1 System Replication PR1 (PR1) secondary speed: Fast since data pre-loaded 49

50 Scale-Out: Storage Replication Cluster 2 Usage: Depends Data pre-load on Secondary: No decision: Depends on storage vendor vip? Cluster 1 Manual Cluster 2 process: Depends on storage vendor reaction time: Depends on storage vendor (PR1) primary PR1 Storage Replication PR1 (PR1) secondary speed: Slower since secondary copy must be completely loaded into memory (See SAP Note ) 50

51 HA / DR Scale-Out Comparison Cost Downtime Comment Auto-Host Failover Manual Performance Optimized Only one cluster Only one DB Human error Inconsistency Relative to people cost SLES for SAP 12 SP2 Storage Replication Public Cloud See above See above AWS Other?? 51

52 Service Pack 2 Remote Disk Encryption Management 1 SUSE Connect 2 Compatibility High Availability 4 3 Future Product Direction 5 52

53 Outlook 53

54 References Best Practices SUSE Linux Enterprise Server for SAP Applications Training elearning.suse.com/product-line/sles12/ training.suse.com/training/suse-linux-enterprise-server-2/ Join SUSE jobs.suse.com/job/nuremberg/engineering-manager-linux-for-sap-applications/3486/ jobs.suse.com/job/nuremberg/software-developer-linux-for-sap-applications/3486/

55 Suggested sessions SUSE Connect - Compatibility Is Key - Tuesday, Nov 8, 2:00 PM - 3:00 PM FUT Solve the paradox: SUSE Linux Enterprise Live Patching Roadmap - Tuesday, Nov 8, 11:30 AM - 12:30 PM - Friday, Nov 11, 9:00 AM - 10:00 AM TUT91496 Keep SAP Running When Patching the Linux Kernel - Wednesday, Nov 9, 4:45 PM - 5:45 PM TUT Towards Zero Downtime - How to Maintain System Replication Clusters - Wednesday, Nov 9, 4:45 PM - 5:45 PM - Thursday, Nov 10, 3:15 PM - 4:15 PM TUT Fast Failover Architecture with a SUSE High Availability Cluster on AWS - Thursday, Nov 10, 4:30 PM - 5:30 PM 55

56 Thank you Hannes Kühnemund SUSE Product 56

57 Backup 57

58 Overview supported SR scenarios SAP NetWeaver Manual Failover Simple Stack Enqueue Replication Combined Stack ScaleUp Manual Failover Performance Optimized Cost Optimized Multitenant Database Containers Storage Replication Public Cloud Others ScaleOut Auto-Host Failover Manual Takeover Performance Optimized Storage Replication Public Cloud Others 58

59 HA / DR SAP NetWeaver Comparison Cost Downtime Comment Manual Failover Simple Stack Enqueue Replication Combined Stack How does each scenario affect cost and downtime? 59

60 SAP NetWeaver: Manual Failover decision: process: reaction time: speed: Manual monitoring and situation analysis Manual Variable Middle since services need to restart on failover node SAP (PR1) Database App. Server Node 1 Manual Node 2 Failover PR1as PR1db PR1ci PR1 60

61 SAP NetWeaver: Simple Stack decision: Fully automated by SUSE cluster solution Node 1 Node 2 pacemaker process: Fully automated by SUSE cluster solution PR1as PR1db PR1ci active/active reaction time: Fast due to pacemaker heartbeat SAP (PR1) Database App. Server speed: Middle since services need to restart on failover node PR1 61

62 SAP NetWeaver: Enqueue Replication (excl. DB) decision: process: Fully automated by SUSE cluster solution Fully automated by SUSE cluster solution Node 1 Node 2 pacemaker vipas vipd2 active/active Enqueue Replication viper vipci reaction time: Fast due to pacemaker heartbeat SAP (PR1) ASC00 D02 SAP (PR1) ERS10 DVEBMGS01 PR1 PR1 speed: Fast since enqueue table pre-loaded 62

63 Controlled Availability SAP NetWeaver: Combined Stack (HANA SR) decision: process: Fully automated by SUSE cluster solution Fully automated by SUSE cluster solution Node 1 Node 2 pacemaker vipas vipd2 vipdb active/active Enqueue Replication viper vipci HANA System Replication reaction time: Fast due to pacemaker heartbeat SAP (PR1) ASC00 D02 primary PR1 PR1 SAP (PR1) ERS10 DVEBMGS01 secondary speed: Fast since enqueue table pre-loaded 63

64 HA / DR SAP NetWeaver Comparison Cost Downtime Comment Manual Failover Simple Stack Human error Inconsistency Relative to people cost Best practice Enqueue Replication Best Practice Excludes DB Combined Stack Technical preview 64

65 Overview supported SR scenarios SAP NetWeaver Manual Failover Simple Stack Enqueue Replication Combined Stack ScaleUp Manual Failover Performance Optimized Cost Optimized Multitenant Database Containers Storage Replication Public Cloud Others ScaleOut Auto-Host Failover Manual Takeover Performance Optimized Storage Replication Public Cloud Others 65

66 HA / DR Scale-Up Comparison Cost Downtime Comment Manual Performance Optimized Cost Optimized Multitenant Database Containers Storage Replication How does each scenario affect cost and downtime? Public Cloud Other 66

67 Scale-Up: Manual Node 2 Usage: Data pre-load on Secondary: Dedicated Yes Node 1 Manual Node 2 Failover decision: Manual monitoring and situation analysis vip process: reaction time: Manual Variable (PR1) primary PR1 HANA System Replication PR1 (PR1) secondary speed: Fast since data pre-loaded 67

68 Scale-Up: Performance Optimized Node 2 Usage: Data pre-load on Secondary: decision: Dedicated Yes Fully automated by SUSE cluster solution Node 1 pacemaker Node 2 active/active vip process: reaction time: Fully automated by SUSE cluster solution Fast due to pacemaker heartbeat (PR1) primary PR1 HANA System Replication PR1 (PR1) secondary speed: Fast since data pre-loaded 68

69 Scale-Up: Cost Optimized Node 2 Usage: Shared with other system (e.g. QA1). Additional storage required for QA1 Node 1 pacemaker Node 2 Data pre-load on Secondary: No vip active/active decision: process: reaction time: Fully automated by SUSE cluster solution Fully automated by SUSE cluster solution Fast due to pacemaker heartbeat (PR1) primary PR1 HANA System Replication (PR1) secondary PR1 QA1 (QA1) non-prod speed: Slow: stop QA1 (meaning QA1 downtime) + completely load PR1 into memory 69

70 Multitenant Database Containers (MDC) MDC Considerations: Can apply Performance Optimized or Cost Optimized scenarios A take-over acts on the parent HANA Database. Node 1 pacemaker Node 2 active/active Sys vip Sys A B A B HANA System Replication All tenant database containers and associated services and therefore affected by a take-over. (PR1) primary PR1 PR1 (PR1) secondary 70

71 Scale-Up: Storage Replication Node 2 Usage: Data pre-load on Secondary: decision: Dedicated No Depends on storage vendor Node 1 Node 2 vip? process: Depends on storage vendor reaction time: Depends on storage vendor (PR1) primary PR1 Storage Replication PR1 (PR1) secondary speed: Slower since secondary copy must be completely loaded into memory (See SAP Note for solutions) 71

72 HA / DR Scale-Up Comparison Cost Downtime Comment Manual Human error Inconsistency Relative to people cost Performance Optimized Best Practice Cost Optimized Best Practice Multitenant Database Containers See above See above Takeover affects multiple tenants (services) Storage Replication Public Cloud See above See above AWS Other?? 72

73