Sie sind auf Seite 1von 144
Enablement D&T S4HANA Database migration to HANA Technical Workshop How to migrate Business Suite to HANA and S4/HANA Enablement D&T: DB Migration Workshop Part 1 - TODAY Introduction 30 mins HANA Technical Architecture overview it hour _HANA Data Center and Technical readiness - Database persistence and restart - HANA Sizing - Backup and recovery AeInOUES - High Availability and Disaster Recovery - Monitoring and Administration - Security and Auditing - Change Management and Transports “SAP Business Suite migration to HANA options 30 mins Enablement D&T: DB Migration Workshop Part 2 - NEXT SESSION Custom code optimization for HANA 30 mins Technical view on migration to HANA - Technical upgrade - Migration approach and execution - Use of DMO option - Unicode conversion 1 hour Overview on RDS for Migration to SAP Business Suite powered by SAP HANA Technical overview on S4 HANA architecture and migration approach 30 mins 30 mins Conclusion and Q&A ‘Migration on specific complex cases (interactive) 30 mins 30 mins DB Migration Workshop Hana Technical Architecture overview » Appliance and Tailored Datacenter Integration . Multi-system on one hardware (options) Virtualization New features (SPS09) hf SAP HANA SPS08 and SPS09 SAP HANA with SPS08 — One Platform, Enabling New Business (What's New) * Applications and Industry Platforms (Development Enablement with enhanced Modeling) * Cloud Enablement (New Configurations, HW, RedHat, Virtualization) * Big Data and Internet of Things (Geo-spatial, SDA enhancements, AFL) * Openness (VMware for PROD, 3 party tool certification, SAS integration) * Database Platform Services (Security enhancements, Enhanced HANA Live/Fiori support) SAP HANA with SPS09 - The Platform for All Application (What's New) * Cloud Enablement (SAP HANA Muttitenant Database Containers) * Application and Industry Platforms (Smart Data Streaming) * Big Data and Internet of Things (Dynamic Tiering for Data) * Openness (Intel eS CPU support, Hadoop) SAP HANA - Implications of being an Appliance Classic software delivery on-premise solutions + SAP ships only the software ‘Customer is responsible for ent product Ifecyele Appliance delivery kind of “SaaS on-site customer” + SAP defines the solution together wih is partners + SAP & partners control product Iecycle SAP HANA Platform SAP HANA Technology Partners SAP HANA Hardware Partners ( intel) @ ‘Bult Hae Sess @ FUJITSU lie Se S) sgi cisco HITACHI Linux on IBM Power CPUs NEC Inspire the Next possble start of pl phase ater SPS02 sooo ES HUAWEI SAP HANA scalability Scales from very small servers to very large clusters 12 PetaByte Data Warehouse with SAP HANA = Guinness world record oo F® ‘Single Server Scale Out Cluster Cloud Deployment 20PU 12808 98 CPU 77 2 on sores por csr ‘SAP HANA incancoscan bo (Speci layout Suto ON HANA. Ey richer 4 CBUNTB OF Goplyed to AWS ferupto 1278 pros) Ceuzte. Limi o developer iene Sing SAP HANA derloyments fo aygst corto conigabon: 112 Sones ‘SAP HANA Entrpise Cloud fata mars or arcoleraters panilerer nace Largest tested coniguaton: 250+ sores and esas recovery Support or tch vali and sate rocovory Certified Intel lvyBridge-EX HANA Hardware February 2015* (available now) s x, S % >| <*>! Batamart Xe 20 xf 9 9 ae 2 3} Suite x & %& = a wm waln a ne aly mm) CPUS a eeooolEEEL EEL EL) Sockets 2m 16 Inst image wit vitualzation| x Supportfor suse sues? | x SupportforRealat RHEL: | x mes Distributions for SAP Applications Relaxed HW Speci ns for Non-Production Bo Notes: Intel Xeon E7 Westmere Ex (E7-x8xx v1) or * Hardware still from PAM or ICC IwyBrdge EX (E7-x8xx V2) SAP Product Avalobity Matrix ee umee http:'sen sap com/docs/DOC. Maximum numery Sopp onthe box 52522 * Non-prod: Sizing flexible Instances can be combined GFFS (BM on), NES or XE8 wl ald Oa above SoH layouts can be used for BW Standard networking components SUSE Linux 11.x or Red Hat 6.5 Virtualized or Bare Metal SAP HANA Tailored Data Center Integration Differentiating Capabilities SAP HANA tailored SAP HANA appliance delivery dota canter integration Fast Implementation More Flexibility and Responsibility ‘Support fully provided by SAP Save IT budget and existing investment + Solution + Instalation and vet oan validation done Validation needs tobe |) suns by SAP and done by customer ow | + Preconfgued | * fhetardwareparner Tr = ‘ hardware setup cnindual suppon sues + Preise model Fy~ software SAP HANA Tailored Data Center Integration Customer Feedback & Challenges and alternative Concept SAP HANA tailored data center integration is an additional option to the existing appliance model + Limited flexibility in server! storage combinations (well defined packages) + Established IT operation processes have to be adapted slightly * Well defined HW and performance KPIs » Reduce hardware and operation cost at installed based customers * Mitigate risk and optimize time to value by taking more responsibilty * Gain additional flexibility in hardware vendor selection * Pease cola ong it pas: SAP HANA post al ce eran cn SAP HANA Tailored Data Center Integration Bo A continuous journey towards openness — Phase 2: Shared Enterprise Networking Phase 3 Enty-level SAP HANAES servers @ sap HAWA.70! Phase 4: SAP HANA s Linaicon IBM Power ¢ ers with wna a? Ske nana Prose Applance SEN sree oame SAP HANA Rewer gr) Roplanee =N2 @ Intel Xenon €. Iyensge 22) a 2 eg a She wana Ropiance SEN 1 wtbalo& Wosrere (7 vt) 2011- Oct. Feb. Nov. Mid. 2012 2013-2014 2014 2015 SAP HANA Tailored Data Center Integration The concept SAP HANA tailored data center integration is an ad the existing appliance delivery model SAP HANA tailored SAP HANA appliance delivery dats center Integration SAP HANA Tailored Data Center Integration Prerequisites for Enterprise Storage Requirements: Server - Only servers listed in the SAP HANA Product, Availability Matrix are supported. al he Configuration adjustments like: lm ~ No local disks, no flash cards required + Additional FibreChannel adapters for SAN boot are allowed ‘Storage — All storages successfully passed the SAP HANA Hardware Certification % * For more information, see Partner Information Center or contact HWC@sap.com ‘SAP HANA Installation — Needs a certified expert (internal or external) to be executed « The exam “SAP Certified Technology Specialist (Edition 2013) - SAP HANA Installation” (E HANAINS 141) needs to be passed successfully to perform SAP HANA installations at customer side. You get prepared for this exam with SAP training H) « For more information, see SAP Training ar equirements) Certification Sho SAP HANA Tailored Data Center Integration Bo Data Throughput and Latency KPIs for Production SAP HANA Systems Ce a Souree: SAP HANA Administration Guide = section 2.7: Heraware Checks for Tallored Data Center integration ‘or SAP Note 1652078 - SAP HANA database: Hardware check Bis == MBytels SAP HANA Storage Layout oo Disk sizing with class. HANA appliance vs. HANA TDI Classical SAP HANA Appliance ‘SAP HANA Tallored Datacenter Integration 0.8:8:1" Disk layout 4" Dis ayout 0.5xRAM log OS xRAM (51268 si2ce" S128" RAM @st268 RAM) ox RAM Deiat RAM 1xRAM SharedsTrace_ 1x RAM eet renter en Ranson for reduced abng © Aeptance cannot shuns becenaad on tert nce, «= Customers can change disk layout (extensions of satan et rca nn ore _ bentvbroe ciegel rote fteporebie te conpicte FAN Sloc ‘lobe updated fo latest changes) * Source: SAP HANA Storage Requirements Whitepaper (SAP nolo 1900828 or SAPFANA COM) “tinea enya sore S12G8-moretbereceeay “Mena abe ay eve S12 GB noe mt bec, ‘eminent hea aor asad ‘oy cee cold Sato areal ath SAP HANA Tailored Data Center Integration Hardware Configuration Check Tool (HWCCT) SAP HANA HW Config Check Tool (HWCCT) » Command-line tool, generally available since SAP HANA SPSO7 * Used by storage vendors, SAP Support, and customers + Measures the data throughput and latency times between the SAP HANA servers and the Enterprise Storage system © Does not require SAP HANA SW being installed beforehand © Uses the same libraries for file system access and the same IO patterns as SAP HANA does + Download it from SAP Service Marketplace © Navigation path: Software Downloads -> Support Packages and Patches -> A-Z Index > H -> SAP HANA Platform Edition > SAP HANA PLATFORM EDIT. 1.0 > Entry by Component > HANA config check -> SAP HANA HW CONFIG CHECK 1.0-> Linux on 86.64 64bit > HWCCT. 80.0-20011598 SAR) * Documented in the SAP HANA Administration Guide Contains the latest KPIs © For latest docu changes, see POF attachment of SAP Note 1943937 © SAP Note 1652071 Hardware check Important: There is no Self-Certification, but a Self-Assessment SAP HANA Tailored Data Center Integration Enterprise Network Data Center 1 Data Center 2 Ne rat tne Qin tnt system Repeaion nwo [More detals avaiable in ° e: SAP HANA documentation: soap sone: @ smernne stags ewer @)ssctep etree SAP HANA Master Guide, chapter? ment Pager wth further dts SAP HANA Tailored Data Center Integration Bao Enterprise Network Recommendations: Al recommendations mentioned refer tothe usage in productive environments Network Segmentation — All networks need to be properly segmented and may be connected fo te same corel backbone Switch, Note: Network securty and segmentation isa function of the network switch Vendor and must be configured according fo the specifications of the ot, witch vendor. For more details on network security see the SAP HANA Security Guide chapter 4 Bandwidth 2 10 GbE for Internode and Backup Network > 10 GbE (Ethernet) or 2 8 GBF (FibreChannel) for Enterprise Storage Network 2 Redundancy - it depends on the customer's high-availablity requirements if and how to apply redundancy for the different SAP HANA network segments. SAP strongly recommends to make the following networks redundant ‘Internal zone (Internode and System Replication networks) = Storage zone (Enterprise Storage and Backup Storage networks) Fully redundant switches and routers are recommended SAP HANA Tailored Data Center Integration Recent changes and Outlook General Availability - Server options: © More CPU flavors are introduced: * Intel Xeon E5 for non-production and production * Scope ‘Single Box, only Seale-Up Intel Xeon 2 socket E5 26x up to 1,5 TB (no 4 socket solutions) ‘Sizing process with NEW SAP HANA Quick Size’ Lists with HW solutions with SCN as “Supported Entry Level Systems" * Soon after SPSO9: |BM Power (with Linux for PowerPC) = Scope BWonH, no SoH No Seale-Out Hardware partitioning * Current status presented in SAP Note Hitachi LPAR HP nPartitions CS900 HANA Hawk" (SAP Note 20 Fujitsu pPAR (SAP Note 2077823) 8665 SAP HANA Scale-Out “Extension” Heterogeneous Landscapes Supported with the following constraints: * Certified SAP HANA scale out hardware from the same HW partner + Same memory on each node (e.g. 512 GB per node) + Distributed tables: Slowest part of a cluster will define the overall performance * Mixture of two Intel CPU generations per cluster will be supported (e.g. Intel Westmere EX & IvyBridge EX) Aim is to increase the size of the database, 7 not primarily the performance ‘Scale-Out cluster members ‘a : WER (CPU power Fulfilling IT compliance (IT po! Data Center compliances usually define specific topics to * Managing, Monitoring and Backup & Restore tools * Central user management with IDM tools * Anti Virus software usage mandates * OS security patches, firewalls * Ete. Additional 3° party tools required to complete these compliances are tolerated with following restrictions * Neither SAP nor hardware vendor offers support for tools which are not official part of the SAP HANA BOM. * The hardware vendor is tolerating the installation and operation of this compliance-related software. * Customers might be asked to stop these tools in case of a support issue and to enable reproduction of the problem * No closed source driver are allowed with these compliance tools without further support agreement of the vendor with SAP for these ies) for Data Centers Bo SAP. HW Partner HA Parner Tools Multi-SID on one SAP HANA hardware Bo ‘ucoD” “ucos” Virtualization (on premise) ‘pliance approach fr | Multiple Components on ene | Multiple Components on one Virtualization tocnelogy cpimal perrmance | Database ‘System, rut SID separates mutple OS tages 1 xAoplanee = xApptience Sx Apphanes ach contaning one HANA DS *1x HANADB 1c HANADB *mxHANADB nx Virtualized Apptances 1x8 schema sn DB schema + mxDB schema sax HANADD 1 Appleton sn xAppticatons “mxAppkestions +1 DB senoma (69. ERF, CRM OFBW) | Prog. usage forwhte sted — | Eg. DEVand GAsystem on “9 *ABplcaions *Boresnetlorvitualzed | scenaries alowed,eg. SAP | one hardware SeeSAP Soe SAP noe 178000 ERP togoter wih SAP Fraud | note 10010 Management. $9 SAP notes 1001202 and 182 Multi-SID on one SAP HANA hardware Bo Multi SID for SAP HANA allowed for all non-productively used appliances Installation process for these additional SIDs is available as Mult-SID Installer (since SPS5) For the current status, please check the following SAP notes 1661202 ~ Support for multiple applications on SAP HANA, 1681092 ~ BW on SAP HANA - landscape deployment planning, 1886670 ~ Multiple SAP HANA DBs on one appliance % 1826100 ~ Multiple applications SAP Business Suite powered by SAP HANA Whitepaper about Deployment options - SAP HANA System Landscape Guide 1849151 ~ MCOD on SAP HANA for ABAP and JAVA AS database schemas Joined SAP HANA and SAP NetWeaver ABAP Application Server and HANA Database on one hardware SAP HANA and SAP NetWeaver AS ABAP deployed on one server is a multi-component, resource and cost optimized deployment approach SAP HANA, SAP NW AS: SAP HANA, Server ABAP Server Server Separated ‘SAP HANA and SAP NetWeaver AS. deployment approach deployed on one server + Hardware resources isolated 4 Cost optimized approach = Separate hardware = Shared Memory and CPU SAP HANA Virtualized — The Big Picture Supported Deployment Options for SAP HANA Virtualized Single VM. ee feet oom 8 an ce 86S. ime | See, soe co eee ie ee ee tin —— am f cuporsonngsnawm severing 1 SAP HANA Virtualized Current Status Supported Hypervisors SAP HANA Platform Supported Hypervisors Other Hypervisors Scale-out Single VM Multi VM Single/Multi VM Single/Multi VM. " 6 v v v : Net supported General Support Controlled Availablity Controlled Avallabity Not supported nutatersing —wangesahawa mae Se pets tater sing Toivemmazed — wimmacmreare ‘ruatrecwnesons’ SAPrAtKwbaimechnes dbo lod Siyocoessas — “Sigeateersas Sonachae ees xP wiAistconer —aNRioslsarn—HANATstsowe SAP HANA Virtualized Current Supported Hypervisors Currently, the only SAP supported virtualization solutions for running SAP HANA virtualized are * VMware vSphere 5.1 and SAP HANA SPS 05 (or later releases) for non-production use cases. * VMware vSphere 5.5 and SAP HANA SPS 07 (or later releases) for production and non-production use cases. * VMware vSphere 6.0 support by SAP HANA planned for 2015, The following general conditions & constraints for running SAP HANA virtualized: * Limited to scale-up scenario only (scale-out / multi-nnode database installations are not supported). + Limited to 2 and 4 socket certified SAP HANA appliance hardware (large 8 socket appliances are not supported) + CPU & memory overprovisioning must not be used he » SAP HANA installation was either done by an SAP HANA certified engineer on SAP HANA certified hardware and — successfully verified with the SAP HANA hardware configuration check tool (SAP HANA Tallored Datacenter Integration option), or system had been delivered pre-configured as certified SAP HANA appliance, with hypervisor installed by SAP HANA hardware partner. See SAP Note 1788665 — SAP HANA Support for Virtualized Environments SAP HANA Virtualized SAP HANA on VMware vSphere in production SAP has released SAP HANA on VMware vSphere 5.5 for general availability, allowing to go live with SAP HANA on VMware Sphere 5.5, provided the following conditions have been met: * Single SAP HANA virtual machine on a dedicated 2 or 4-socket SAP HANA certified server * Multiple SAP HANA virtual machines on a single physical server No SAP HANA multi-node / scale-out deployment configurations No 8-socket hardware configurations * Both, SAP HANA appliance and SAP HANA Tailored Datacenter Integration (TD!) delivery methods are supported for SAP HANA on VMware vSphere. The maximum size of a virtual SAP HANA instance is limited by the maximum size of a virtual machine on VMware VSphere 5.5 release, which is 64 vCPUs and 1 TB of memory (limited by VMware, not SAP HANA). No CPU andlor Memory overcommitting ‘VMware Vmotion (hot move) or VMware-HA are supported ‘See SAP HANA Guideline for Being Virtualized with VMware vSphere SAP HANA Virtualized VMware vSphere Features Supported with SAP HANA The VMware vSphere 5.5 support for SAP HANA in production also covers the following VMware vSphere products / capabilities: * Use of VMware HA to protect Local BCA | | Renoene operating system or vSphere host hardware failures » SAP HANA System Replication or Storage based replication plus VMware SRM to provide disaster protection * The use of VMware vMotion in conjunction with DRS rules * The use of additional non-SAP HANA VMs on SAP HANA server * Use of snapshots and cloning capabilities AWA Sytem Reaeatn 08 Harpe Repeston and rene vsphore Host Sphere Host sphere Host x B e SAP HANA Virtualized Technology Roadmap Today * Support for SAP HANA on VMware in non-production scenarios * Support for single-VM SAP HANA on ‘VMware in production and non-production ' scenarios t * Controlled Availability for multi-VM scenarios t in production ' On Roadmap Ei i * Support for scale-out scenarios Bes 7 Support of larger VMs (4 TB) 1 ' * Support for 8 socket HW 1) t © Support of additional hypervisors } 4 core H1/2014 H212014 2015+ Yoon Varo vSphor on: SAP HANA Virtualized Comparison SAP HANA virtualized vs. native, based on VMware vSphere 5.5 What use cases are a good fit for SAP HANA During performance analysis the majority of tests stayed within 12% performance degradation compared to bare metal. However, there are around 100 low-level performance tests in the test suite exercising various HANA kernel components that exhibit a performance degradation of more than 12%. This indicates that there are particular scenarios which might not be suited for HANA on VMware. SAP HANA Virtualized Multi-tenant options ‘ne Schema utile Schemas Mulliple SAP HANA instances on Mie tant databases One (nttsitedaconros) aBlance(e., VMware) ‘Schema x | Schema ¥ os os os ee a Prior to SPSOS With SPS09 Multitenant database feature SAP HANA Multitenant Database Containers Overview SAP HANA multi-tenant database containers (MDC) Support for multiple tenant containers within a single system database Initial focus on the following scenarios: * SAP HANA Cloud Platform * SAP HANA Enterprise Cloud + Replace most MCOS deployments (Multiple Components One system) + Address common MCOD scenarios (e.g. ERP-CRM-BW, QA/DEV, Data Marts) * Cross scenario support: Fast federation between tenant databases (read only with SPS09) * Typically scenarios with a database with ‘relatively’ small number of tenants = Le. Typically for ~10s of tenants vs. 1000s of tenant databases SAP HANA System ‘System DB Tenant SAP HANA Multitenant Database Containers Ba Scale-out scenario with multitenant database containers SAP HANA System Tenant databases can spread over multiple \ “A odes (hosts) in scale-out systems Example: CoD ‘ana ancora) host 2 goes down, the standby host becomes . : active. The tenant DBs normally running on host 2 will become active on the standby host => ‘Tenant 0B At Tenant BC [ff Tenants D HOST 1 Host 2 Hosts SAP HANA Multitenant Database Containers Positioning multitenant database containers Multitenant Database Containers vs. jualization Multitenant Database Containers * Lower TCO, single software stack * Central configuration & administration (database level) * Direct database resource management * Optimized federation (performance benefits) = Performance advantages (no virtualization overhead) + Licensed via SAP HANA Virtualization * Strong isolation * Separate SAP HANA revisions option * Standard federation (SDA) * Additional virtualization license (e.g. VMWARE) SAP HANA Release Strategy Retrieve incremental, but non-disruptive SAP HANA innovation Updates shipped for SAP HANA are strictly downward compatible. Incompatible changes may be considered due to legal or security reasons, but follow a strict exception approval process (Time-less Software), ‘These Updates are shipped with SAP HANA Support Package Stacks (SPS), delivered from within one delivery stream and without additional ramp-up. SPS are planned to be released twice per year. The SAP HANA product stays in mainstream maintenance as long as application releases that are. built on top SAP HANA are in mainstream maintenance, extended maintenance, or priority-one support — (e.g. Release note 74.xx 1935871). ra78 Gere @ore Revisions are cumulative and strictly downward compatible SAP HANA Release Strategy Understand the Differences in SAP HANA Revisions SAP HANA Support Package (SP) Revisions Represents the individual software corrections and updates available for SAP HANA. Revisions are cumulative and strictly downward compatible, SAP HANA Maintenance Revisions Contain only major bug fixes found in key SAP HANA scenarios. The provisioning of new maintenance revisions ends with availability of SAP HANA production system verified revision, approx. 3 months after release of a successor SPS. From this date, customers must adopt the regular SP revisions to receive further fixes. SAP HANA Datacenter Service Point Outlines certain revisions which have been running in production enterprise applications at SAP before they are released to customers. Those revisions are planned approx. meoctns Gearon Pen 3months after release of the iatest SPS Teese ‘@ and are intended to allow better planning i ‘of maintenance windows for production environments running on SAP HANA wa 3 SP revisions Maintenance revisions SAP HANA Release Strategy Bo Expect stability and predictability for your SAP HANA maintenance The newly introduced SAP HANA Datacenter Service Point (DC service point) provides SAP HANA customers with more guidance when and based on which SAP HANA Revision to plan their SAP HANA maintenance stack on. ‘As most customers have to plan their maintenance window between their quarterly end closings, the DC service point had been defined to be between the SAP HANA SPS, af the end of March and af the end of ‘eptember. As prove of SAP’s commitment in its own software quality, the Revisions referenced by such DC service int wil also be running in production enterprise applications at SAP for al least one week before they are inally released, assuring customers even more stability and predictability, re Recommended SAP HANA Datacenter fr Service Points for planned maintenance Que of SAP HANA @a — f J) Recommended revision update / patching path = for key SAP HANA scenarios in production SAP HANA Platform Introducing SAP HANA Dynamic Tiering Prionty and Performance Data Volume and Price wn08 Inmemary Norestctons, al features evaitle noe Onaask No testretos, al fetures avaiable ae ‘ Neer ino Serag9 Rood acoss, no updates External 190 + Archive storage Noroad aeess or upstes SAP HANA Persistence | Regular Saving of In-Memory Data to Disk, Restart In-memory computing is secure The SAP in-memory database holds the bulk of its data in memory for maximum performance, but still uses persistent storage to provide a fallback in case of failure. The log is capturiig all changes by database transactions (redo logs) Data and undo log information (part of data) are automatically saved to disk at regular savepoints The log is also saved to disk continuously and synchronously after each COMMIT of a database transaction (waiting for end of disk write operation) After a power failure, the database can be restarted like a disk-based database + System is normally restarted (,lazy* reloading of tables to keep the restart time short) + System returns to its last consistent state (by replaying the redo log since the last savepoint) Time Savepoint: CContinously and after each COMMIT, Power failure Data & undo logis writen “redo log is written to disk (log area) to disk (data area) SAP HANA Persistence Startup in detail — possible optimization options +. Open Persistence files (Data Volume, Log Volume) + This and following stops aro executed por HANA servic indviually 2 Load RowStore with creating secondary indexes ‘Exezuon time about the same for oang complete store and creating ee. nexes in paral For HANA persistance Row Stor is siiar fa BLOB and aly opened logaly on engine vel 5. Initialize Hybrid LOBs (can be millions especially with SoH) + LOBs bigger than 1 Kbyte are usualy extracted to HANA deta volumes and organized via pines as soon as this database was created since SPSOT. Every [ABA tox! data type fancied info & LOB on te Gatabace level This produces efoto nai thie huge numberof small LOB drng tatup Wah nfive ‘pplicaions you could iy of wiiz0 more data types next fo LOB ko stueturos (arena. 4 Get open transactions to follow up on (Data Volumes) ‘Rolback information is located on Data Velumes, not Log Velumes (ows a consistont database recovery erly withthe help of @ HANA data backup) ‘Roll forward information (eo) 1 loatod onthe one Log Volume © Roll forward Log for Row and Columnar store Fist loads of columnar stvlures are exoovted 8 they ae 9ecessod to aoa ol forward ho 10g on hom “Alt end of this redo-og operaton the dalabaso i echnical avaiable —og-on posse © Start leading columns marked with the preload flag *Alows to load columns usod by important business process0s blero he next stop hey aro not etroadyloadod by tho ro forward in th stp Bofro 1 Start loading tables from the list of lastly used tables * Dung the normal operation before the restart HANA tracks ais of tables which are curently loaded (once per day) + Ths ists now the basis of fading the cessarytablas ito main momory & SAP HANA Smart Data Access Data virtualization for on-premise and hybrid cloud environments Benefits Transactions + Analytics Remote real-time query processing ‘Smart continuously selttuning system Secure access to heterogeneous data sources Heterogeneous data sources SAP HANA to Hadoop (Hive) Teradata SAP Sybase ASE SAP Sybase 1 Oracle 12¢ MS SQL-Server SAP MaxDB. Sizing Process with SAP HANA eed Deere vanes Ras ose) Sizing with SAP HANA installations ‘Sizing New Applications “Initial Sizing” 1 SAP Quekszer too Migrating to SAP HANA Applications. 1 San rn 0A SAN 84000 wo parpeuive Se) 3. SAP NetWeaver BW Powered by SAP HANA SAP Nolo 1730070 ‘Sidecar Scenarios Sizing 1. SAPHANAEntornse Soarch: SAP Note 18/247 2. COPAAseaIor HANA Sina lor COPA Accalaato 5. SAPAppbeatens on HANA SAP Quickie To Please check SAP HANA Sizing Overview for latest updates, 2 Consider s efor SAP HANA General statement “Prefer a scale-up before starting to scale-out to multiple boxes (GAP HANA Scafapiity document > Chapter 4.5) 4. Special requirements for BW and Scale-Out: SAP note 173 6 <> check attachments SAP Business Suite powered by SAP HANA Sizing Greenfield Sizing Sizing based on an existing System Expert sizing for ‘existing system on HANA Black Box Sizing HANA Reps Prootyping New implementation of Business Suite on HANA Standalone HANA ‘SAP Quek Sor to! ‘sizing roport (soe SAP Noto 1872170) ‘Database moraton ofan exsting {olorminos the overall database tabi Business Suit sytem to HANA footprint for both row store ana column SAP HANA Aecelerators sore. Estimates the requred memory for ‘SAP HANA Sting veriiction ‘Combination of ferent approaches: Now large of complex projects are 3 pianos Exraorcinary use cases : Deine customer specie sing gudeines = Roughrestimates forthe required HANA, ewer siza Gives an nial ncaion ‘Workload analysis of exsing HANA Syston ‘Analysis of sizing relevant inpct Volume ena eas testing ‘See SAP Nole 1704 Souee_0B/2"1 approximated HANA. DB. Information about the (expecta) data volume fs available. SAP Business Sut system on ‘AnyOB is oready in place Productive systam on SAP_ HANA\s already n place The source 085 uncompressed and Unicode The source OB ie well, For further details please refer to chapter Architecture —+ Sizing of HANA Deployment Best Practice. General Sizing Procedure for Landscapes on SAP HANA Determine basic Project size for Map system sizes to \ Project disk space Application layer, database size hardware planning» possible hardware. > for TDI (optional) > non-PRO (optional) Sizing guidelines for Check table sizes and Group systems Disk sizing: use Application layer greenteld possible eflecs of «sige (hysia) formulas for + Consider growin implementations * bataarchimng systems = Instataton = Housekeeping + System clusters (MOC, = Data volume ae Sizing reports vata) 1 fopswecopendson _* PRE, GAS, DEV, SBX * Suite on HANA Set target year for indviaual system size, * HADR * BWon HANA sizing projection ‘Assess appropriate go- ‘maximum is 512 GB + Temporary systems * Yearonyeargrown —_‘lvohardware in view of. Bocip Sizing formulas planned growth (eee ng tow Landscape systems ~ Ener Pol Include otherimpacts = Extensions ae posstie NOMOK-Szng flow ATT + SAP Mobile Patio = Adtionalfunctonaly Check CPU ieee + Process Oreestraton + Customreperting(e9. requirements ib sure ema HANA nats) Beer cecesper scorenet antoan Manual sizing + Adational business intany ietaelie aac: + Cave-outs(e9.HR) Unis egeciesmiced: Theos wo sas ae vey erpotant and boong srorune sues a eget inte proosion area ese (8° oaene) Determine the right Building Blocks Greenfield approach eed Beg etry Ce aed Migration approach Nero Cae Sealy ud (size at go-live) Increasing complexity and conjecture Cee eens ‘Challenging article: Dependew on te wotane and busines ‘comply an espe za isrequed Exper sizing fe done in Iterations along the development and test eele. Usual, ‘measurements are performed usd for he stag pjechon Apples o HANA Standalone systoms, Woud ao rete rataces. Most usvally covered by standard sizing guidelines and ool ke ‘Quick Stern cases of igh volume, an adSiena caper sina ‘eonmended On, custom an high volume go hand mand. “The relay ofthe calcustion depends moston in what way Te ran ig eBusiness vr canbe ado the The ng must be vad ora defined pont in une, § years 160 much, 1 yar canbe problematic becase of budget cosas. ‘Genera recommendation fs 3 years. Unt canbe oid GB, ‘Er hare ate sizing repos forte lvgr NeWoaver ABAP ‘ystems of hte ae rules of thumb, fornen-ABAP systems whore {he BB is wvaty not so rg, Tvs appes sto non-SAP systems, “stooge aly recommen an expe ig or HANA Standalone. Note: the building blocks are optional and need to be specified for each system in scope. Rena. DB Migration Workshop HANA Datacenter and Technical readiness Backup and recovery SAP HANA Backup and Recovery =a Memory > Disk > Backup SAP HANA database Data backups * Contain the current payload of the data volumes Memory » Any pages that are changed during the data backup written to different locations in the data volumes (shadow page he [COMMIT concept) : * Manual (SAP HANA studio, SQL commands), or scheduled (DBA Cockpit) Log backups * Contain the content of closed log segments * Automatic (asynchronous) whenever a log segment is full or DatalBackups Log Backups the timeout for log backup has elapsed ‘y SAP HANA Backup and Recovery =a Terminology Data * Data area = all data volumes * 1 data volume per service with persisted data (per node) Redo log * Log area = all log volumes + 1 log volume per service with persisted data (per node) Data Pr * Log volume contains log segments Number of pre-formatted log segments is configurable Log segments are closed when they are ful or the log backup timeout has elapsed Log Volume ‘After alog Segment has been successfully backed up, itis released for overwriting Log er) Norn) Sa Backup and Recovery oa Advantages for Backups with HANA Kernel involvement Structural knowledge of data in database kernel * Mini-verify of every page with relevant information during simple data and log backup « Header and Trailer verification of checksums ensures valid data in pages » Hardware problems get soon recognized and can be treated early enough wio further implications to, general data consistency * OS-related or external tools don't offer this structural knowledge into HANA data types Performance * Only occupied space is backed up + Throughput of up to 0.5 or 1 TB per hour and per host (scale-out case) reported in an optimal situation (There are a lot of ways like bad network throughput, slow NFS storage perf., no hardware separation etc. to ruin such a good B&R performance) Check Backup * General possibility to check also backups with data knowledge in kemel available (please check SAP note 1869119 and 1873247 for further information) SAP HANA Backup/Recovery = Data backup: Only payload is backed up Shared Backup Directory (staging area) SAP HANA Server DATA_BACKUP_0000, ) oy +> DATA_BACKUP_0001 SAP HANA Backup/Recovery Data backup: Single-node and scale-out systems SAP HANA automatically handles the synchronization of backups for all nodes © no special user interaction required * All services that persist data are backed up e.9. index servers, master name server) * Global data backup savepoint for all these services ‘Synchronized across all nodes and services Transactions are paused very briefly ‘Savepoint is kept until the backup is finished for all services. Ifa page is changed during the backup, is written to a different location (shadow page concept) * Data marked in the savepoint is read from data volumes and written to backup files ‘One backup file per service Parallelization Savepoint Savepoint Le Savepoint pan Savepoint ~~ Synchronized backup savepoint Shared Backup Directory SAP HANA Backup and Recovery =a Destinations for backups (1) Backups to the file system * For both data and log backups OOTY + Eg. toan NFS share evs + For information on file systems: SAP Note ed + Data backups triggered/scheduled using SAP HANA studio, SQL commands, or DBA Cockpit, s log backups written automatically (unless disabled) | SAP HANA : Database Coe! SAP HANA Backup and Recovery =a Destinations for backups (II) Backups to 3rd party backup server * For both data and log backups TITTY * "Backint for SAP HANA” API can be implemented, err frie & by a 3rd party backup agent (certification required) * Provides functions for backup, recovery, query, delete * 3rd party backup agent runs on the SAP HANA. ) server, communicates with 3rd party backup ore ‘SAP HANA * Backups are transferred via pipe etabass * Direct integration with SAP HANA: Data backups to Backit can be triggeredischeduled using SAP HANA studio, SQL commands, or DBA Cockeit Log backups are automatically wien to Backint i configured) SAP HANA Backup and Recovery =a Backint Certification In December 2012 SAP released the certification process for “Backint for SAP HANA”. Certification is an installation prerequisite for backup tools using the “Backint for SAP HANA" interface. ‘SAP Note 1730832 (‘Using backup tools with Backint’) + Release announcement Certified tools (as of 2014-June) n cor Eine Sie Symantec NetBackup 7.5 ‘SAP Note BM Tivol Storage Manager for Enterprise 6.4 ‘SAP Note 191 | | Commvaut| Simpana 10.0 SAP Note | HP Data Protector 8.0 SAP Note 19 EMC Data Domain ‘SAP Note EMC Networker 82 ‘SAP Note SEP ‘Sesam4.4 SAP Note 2024234 Online listing of certified tools: it * "SAP-Defined integration Scenarios" Information for tool vendors: htip:/son sap com/doos/DO0-34483 SAP HANA Backup and Recovery = Destinations for backups (III) Storage snapshots as backups SAP HANA also supports the creation of storage snapshots, which can later be used for recovery storage [i cl 1. Using SAP HANA studio, prepare the database for the storage snapshot. Technically this creates an internal data snapshot 2. Using the storage tool, create a storage snapshot of the SAP HANA data area 3. In SAP HANA studio, confirm the storage snapshot as successful. An entry including the extemal backup ID is written to the backup catalog SAP HANA Backup and Recovery =a Options for backup: Comparison ‘Advantages * Consistncy checks on lek lve * Consistncy checks on Heck ve * Fast + Ease of use no exc backup las + Negligible nto lad managemes,nlegaed nto Sido +s sore parers oer intexrtion in + Data contr integration ar tots + Adora features, eneypsan odo upicaton Backups mmesdatily available for veccvery Disadvantages |» Aditcval sorage weed 7 Naor 7 Ne consisiancy checks on block val + Fle system evel needs tobe mentrad + 2 pry back ol necessary + Atonal time nosed to make backups arab eroconery + Networked + Incase of ecoveas, back les must be retuned staging area Tae > Pasadena + Pecan 7 Sao daa aa ba waly ermeressadio dipheta by troge Duration 7 1O-bowna feadna fom data aur, wring |» 1O-boud Weeding om daa youne) 7 Neate aia arias a opheatea) totaget ‘+ Netwok-bound tog o becky seve) + Networkcbound (ting ole syst) Backup and Recovery =a Backups during normal operation of the database: Summary Tim hy e | ™ (2) 8 oe Data backups Log backups Most recent Crash (external backup (external backup log entries destination) destination) from log area Toloam mere about "Recovery with missing log backups" see SAP Not 1 oF about How to reraate the backip caalog’ Soe SAP Neto 1812057 SAP HANA Backup and Recovery = Backup catalog The backup catalog provides detailed information on data backups, log backups and storage snapshots, for example startiend time, duration, size, and throughput The backup catalog s stored within the SAP HANA database, and also backed up as part ofthe log backup (eyen in log mode OVERWRITE). This allows for offiine access to the backup catalog during recovery. SAP HANA Backup and Recovery =a Recovery steps when using a storage snapshot 4. Using the storage tool, transfer the storage snapshot to the data area of the SAP HANA database Using SAP HANA studio, recover the database using the storage snapshot as basis (available in the recovery wizard) Note: All recovery options are available, including point-incime recovery using log backupsilog from the log area ee - ic Note: Alll recovery options are available, including point-in-time recovery using log backups/log from the log area rca Bor Data snapshot Perro) SAP HANA Backup and Recovery so Database Copy with SAP HANA native backup files Using data and log backups — source and target databases may have different number of hosts Node n Node 2 G Node 1 a | (ntoxsonert) ( \ Source database Data backup Target database with n nodes + log backups with 2 nodes (e.g. PROD) (optional) (e.g. 04) SAP HANA Backup and Recovery sa Database Copy in combination with Storage Snapshots Using snapshot and log backups — source and target databases must have same number of hosts Noden | Node n = Node 2 | Node 2 a \ Node 1 Node 1 Cnt on (lndex Serer) \ t Source database Snapshot + Target database with n nodes log backups with n nodes (e.g. PROD) (optional) (eg. DEV) SAP HANA Backup and Recovery = More information Documentation SAP HANA Administration y SAP HANA Technical Operations Manual Overview presentation + Backup/recovery overview presentation Best practices + 2091951: Best practice: SAP HANA Backup and Restore Important SAP Notes * 1642148: FAQ: SAP HANA database backup and recovery + 4730932: Using backup tools with Backint + 1869119: Check backup integrity * For further notes on backup/recovery, see HAN-DB-BAC. Backint for SAP HANA certification * Certification announcement and description HA & DR Concepts in general Eg ‘Sfieor E RPO TO ira design & prepare foteel rozover. | port ramp KPIs: * Recovery Point Objective (RPO) = worst-case data-loss * Recovery Time Objective (RTO) = time to recover from outage Solution Usedfor_Cost_RPO_RTO Perf ramp Backup & Recovery HA&DR $ high high med SAP HANA Host Auto-Failover HA $ 0 med — ong SAP HANA Storage Replication w/QA,Dev. DR $$ 0 ~med —_long SAP HANA System Replication HA&DR $$$ 0° low short SAP HANA System Replication w/ QA, Dev. HA&DR $"/$$ 0" med _long High Availability - Disaster Recovery 5) Business Continuity ——I—_ High Availability Disaster recovery = per Data Center between Data Centers SAP HANA Host Auto-Failover ‘SAP HANA Storage Replication (Scale-Out with Standby) SAP HANA System Replication ‘SAP HANA System Replication « Performance Optimized « Performance Optimized + Cost Optimized +» Cost Optimized SAP HANA High Availability Scale-Out with Host Auto-Failover Scale-out clusters address two problems. * Seale to a setups, bigger than one host © Offer an easy HA option by putting one or more hosts as sparelstandby Host Auto-Failover is offered by the Name Service + The resulting cluster is managed by this name service inside of HANA * He regularly checks on the cluster members to be still active + Incase of problems he initiates a fully automated take-over to the standby hardware, * Together with the switched of mounts/disks also the identity of the failing cluster member is moved to the standby hardware Starting with shared storage, HANA Scale-Out today can use SAN storage with FibreChannel adapters * Storage Connector API ensures the possibilty of remounting necessary file systems to standby hosts * More details with: SAP Note 1900823 - Storage Connector API Please check its attachments for white papers ete SAP HANA High Availability Scale-Out with Host Auto-Failover Scale-out clusters address two problems. * Scale to a setups, bigger than one host © Offer an easy HA option by putting one or more hosts as sparelstandby Host Auto-Fallover is offered by the Name Service + The resulting cluster is managed by this name service inside of HANA «He regularly checks on the cluster members to be still active. * Incase of problems he initiates a fully automated take-over to the standby hardware, * Together with the switched of mounts/disks also the identity of the failing cluster member is moved to the standby hardware Starting with shared storage, HANA Scale-Out today can use SAN storage with FibreChannel adapters « Storage Connector API ensures the possibilty of remounting necessary file systems to standby hosts Please check its attachments for white papers ete HANA High Availability ce Host Auto-Failover (standby) Different implementation of High Availability by HW partners Using storage solution inside Using internal disk SAP HANA High Availability Ee) Minimal Setup for Host Auto-Failover Minimal setup for a Host Auto-Failover (Scale-Out): active standby 2 Servers including one Standby Extemal storage or similar technology necessary which ensures the data provisioning to second node via external data location This setup aims for High Availability not performance scaling or size. Note: Some use cases (e.g. SAP BW powered by HANA) might have different requirements or recommendations for minimal setups (e.g. BW has a defined setup for SAP HANA Scale-Out — SAP note 1736976 © attached PDF). SAP HANA High Availability a ==) Client Management with Scale-Out Clients: he * During installation the cents gt intial information about how to contact to HANA database — often only one host is offered * To prevent single point of failure, more host should be offered in case of Scale- Qu + The list is only necessary to establish a first connect to HANA cluster — afterwards the client gets the full topology from the database Name Server SQL clients Sa a round robin anyway hanat haraz haras —_-* The complete list of hostnames including the standby host should be stored fy HANA Scale-Out User store: * Contains the list of host names like “hana ;hana2;hana3" etc. next to user and encrypted password information * All tools based on this database interface named sqldbc (SAP Appl. Server, hdbsql, ODBC, python, etc.) can use this user store. Algorith * Round robin process is used to find this first contact point SAP HANA Disaster Recovery: Storage Replication pay Cluster across Data Centers = Application Clients saver! Data Center 2 OS: DNS, hostnames Secondary (inactive) HA Solution Partner HA Solution Partner SAP HANA Disaster Recovery: Storage Replication pay Cluster across Data Centers with QA & Dev. on 2" site =< zs Application Clients Saver! Data Center 2 = OS: = cs z OS: DNS, hostnames 3 ry 5 Secondary 5 a Prod finactive), QABDEV (active) OL © - c S 5 3s = 3 3 3 3 B o < < Be ae SAP HANA Disaster Recovery: System Replication Cluster across Data Centers with DB controlled transfer z Application Clients eerie Data Center 2 OS: DNS, hostnames, virt. IPs Secondary sonded) HA Solution Partner HA Solution Partner SAP HANA Disaster Recovery: System Replication go Cluster across Data Centers with QA & Dev on 2% site Data Center 1 4 c Data Center 2 5 OS: DNS, hostnames, virt. IPs 5 = Primary Sece y = a (ee | ee Transfer ‘PRD & 5 ~l » © shadow: & = am E Slin e 3 8 = 8B i =< = og + =< ARIE SAP HANA High Availability: System Replication Minimal setup in one Data Center for fast takeovers Lad 18 z Application Clients sanem Data Center 1 OS: DNS, hostnames, virt. IPs 5 Primary Secondary fe 2 sta — {2ctve, data predosdes) 5 rah ee Tmnsis | Name Serve £ o a & ie 7 a 5 = 2 5 3 interna Internal 3 bene ral = @ ao <= Data < Foie < SAP HANA in Data Centers go Cluster Manager with direct SAP HANA Support . hsm HP Service Guard rani * Directly available from HP and HP drives the implementation process Peng Mer ly *» Link for further information: manag 7 Reference Guide: HP ServiceGuard Extensions, March 2014 “rng User Guide: Managing HP ServiceGuard Extensions for SAP for Linux, December 2013 oa SUSE Cluster * Included with “SUSE SLES for SAP Applications” * Blog: Fall-Safe Operation of SAP HANA®: SUSE Extends Its Hi » Setup Guide: JANA System Replication of igh-Availability Solution P Applications SAP Landscape Virtualization Manager (SAP LVM) * Since Release 2.1 integrated, earlier releases need consulting package (Infrastructure Kit) + Adaptation to local environment or resources (virtual IP addresses) necessary Other cluster managers * In pipeline or can be adapted with individual consulting packages Zero Downtime maintenance cs Featured by SAP NetWeaver ABAP stack As an evolution of “Near Zero Downtime Maintenance”, SPS7 now offers Zero Downtime Maintenance = Based on connectivity suspend feature of the SAP NetWeaver ABAP stack (SAP note 1913302) o DBSL of the database interface decouples transaction management between ABAP and HANA database This keeps transaction on ABAP layer alive and allows to change components (software versions) on the layers below on secondary (shadow) HANA instance * Further information also in Step-by-Step Implementation Guide for SAP HANA System Replication: https://scn. sap.com/docs/DOC- + Hardware mix (SAP note 1984882 - Using HANA System Replication for Hardware Exchange with minimum Downtime) NNW NTN “stare Upgrade sap ian arson Worldwide Data Center Setups go Multi Tier System Replication — Cascading Systems Data Center Data Center Async a4 . Re Syne 4 Tier 1 Tier 2 Tier 3 Production Local shadow Remote system/shadow with data preload with or without preload (mixed usage together with non-prod. operation) SAP HANA in Data Centers Bandwidth considerations for System Repl SAP How-To Guide: Network requirements for System Replication: http://scn.sap.com/docs/DOC-56044 4. “Throughput: Out of practical reason it must be possible to transport the size of the persistently stored data within one day from the primary to the secondary. 2. “Latency’: In case of SYNC operation: The redo log shipping wait time for 4 KB log buffers must be less than a millisecond or in a low single-digit millisecond range — depending on the application requirements (relevant for synchronous replication only). © More info with SAP HANA Network Requlrement Paper or © SAP nate 1969700 contains among others an SOL statement (in Ep achive aache) to esta he average (pda), Bénawaath required for SAP HANA System Repicaton epending onthe dala and log amount por day continuous Besetine * Example for a bandwidth calculation: Given: 4.3 TB of persistently stored data (sum of data backup file sizes). ‘Throughput: 4.3 TB per day > ~ 50 MByte’s © ~0.5 GBit/s minimum connection required SAP HANA System Replication go New in SPS09: SAP HANA Multitenant Database Containers SAP HANA Multitenant Database Containers * SAP HANA System Replication can be used to replicate the ‘whole system * The replication process treats the complete collection of tenant containers as one * HA&DR is the intention ofthis first support * Replication of a single tenants to an individual location not possible Further information with SAP Note 209: SAP HANA Administration and Monitoring [em 2 Introduction HANA Studio is one administration & monitoring tool for managing SAP HANA. It enables customers to make sure their HANA system runs as expected and provides possibilities to analyze problems Italso houses the SAP HANA modeler and the user management for the SAP HANA database SAP Solution Manager can be used for basic administration and holistic monitoring of HANA systems within existing SAP landscapes. e Itis used by SAP support for early problem analysis and as backbone for CTS¢+ transport integration SAP HANA also integrates with SAP Landscape and Virtualization Manager (LVM) for basic operation of larger/more complex SAP landscapes (startistop & dependencies, etc.) SAP HANA Studio Ge Native Administration & Monitoring Console remiss » Administration 7 View Ne Navigator =a | | 3 os | | Properties =~ } | Vie SAP HANA Administration and Monitoring iL} Screenshots SAP HANA Studio DBA Cockpit in SAP Solution Manager SAP HANA Administration and Monitoring sal based Monitoring and Administration) SAP HANA Cockpit (w SAP HANA Administration and Monitoring 2 HANA DB Control Center ‘SAP DB Control Center * Lets you perform aggregate monitoring of SAP database products, including SAP HANA * Use control center to check the overall health of systems located within a data center or across your enterprise. * Status displays focus on four high-level areas: ‘Availabilty Performance ~ Capacity Aerts * Dril-down into details opens the system's cockpit (e.g SAPHANACcockpit) which provides more information about the availabilty, capacity, performance, and alent status of the system “ on - re * htp://: production system), SAP Identity Management and GRC Access control support ‘Authorization “Privilege concept based on standard SQL privileges + extensions for business applications Encryption * Communication encryption (SSL), data volume encryption (on disk), backup encryption via certified 3 party backup tools ‘Audit logging * Aut logging framework for logging crtcal events, e.g. userrole or configuration changes, data access logging, firefighter mode; aucit trail writen to Linux syslog or to SAP HANA database table Security ‘SAP HANA Studio, SAP HANA XS administration tool, additionally SQL interface for userrole management and ‘administration ‘other administration tasks (command line tool hdbsql available) SAP HANA Security — data center i Identity Management Infrastructure Compliance Infrastructure ‘Single Sign-On Infrastructure Logging Infrastructure sau sal Kerberos ‘SAML __sysiog tegration yO TTY User and role provisioning integration wih thor Sarl managerent Compliance infrastructure Out. he box connector fer Sar Access Contra Standards-based single sign-on infrastructure Eg Microsoft Active Directory Logging infrastructure Datasace aud tat ‘wren nn Linux syslog SAP HANA - security patching oa Operating systems ‘SUSE Linux Enterprise and RedHat Enterprise Linux Security patches ‘SAP HANA secufty patches are published as part ofthe SAP Security Patch strategy (SAP Security Notes) e + Delivered as SAP HANA revisions + Operating system security patches are provided and published by SUSE/RecHat SAP HANA security documentation * General information on SAP HANA security: SAP Helo Portal * Security whitepaper: hitp./4vww saphana.com/docs/DOC-3751 * Best practice document on SAP HANA roles (inc. role templates) /sen.sap.comidoes/DO% Important SAP Notes 08623: SAP HANA appliance: Securty (Central Security Note) 4967: SAP HANA appliance (Central Appliance Note) 730029: Using external tools in an SAP HANA appliance '30830: Using antivirus software in an SAP HANA appliance 7730999: Configuration changes in HANA appliance Change Management concept in HANA Introduction to repository The repository and lifecycle management of objects ‘SAP HANA Studio Modeling Perspective = Native feature of SAP HANA providing “backend” functionality for content lifecycle management OS upgrade not required * Only SAP MaxDB 7.9 is supported for SAP NetWeaver 7.31 > DB upgrade required Decision matrix: Technical requirement if. H, ff. & f, Od i, eau Classical Migration Transformation NODE wparade < DB upgrade causes c) Incase olepeial 400 tt eed © Neanenatcowntne © _reaurement Migration to HANA Guides Available at the following link https://proddps.hana.ondemand, com/dps/d/preview/6932132d32b54158a961a755e043e21e/1 O/en- US/index. htmifurl=a335bd4fdd634e48aaa7 1 1abab223fad.html SxS aa om tan oss Po Ba _ Aan Migration to HANA Guides Available at the following link https:/Awebsmp106.sap-ag.de/~sapial [3 DMO_RTC_10 Latest.pdf Upgrade Gulde cusTouen Software Update Manager Document Version: 10= 2015-04-27 Project planning aspects SAP Data Volume Management — migrate only required data 6 @Use SAP Data Volume Management (SAP DVM) to monitor and = control data growth and to minimize data volume 99 = * To improve system performance * To reduce infrastructure and operation cost Especially for migration to SAP HANA: * Benefit from shorter migration duration due to reduced load size =— * SAP DVM Workcenter in SAP Solution Manager offers special focus on SAPHANA: @ — Generate a best practice guide to determine data that can be reduced most efficiently in an SAP system before SAP HANA migration = Get overview + statistical data by simulating how much space you can save by migrating it to SAP HANA (or by using data reorganization and compression) Simulate your future system size and cost savings to get a forecast of impact of planned measures aR Co Project planning aspects Further important aspects and considerations 4 GDefine overall target system landscape 99 » Example: put development and QA system on one appliance? * Scale-up (scale vertically by increasing size of hardware) vs. scale-out (scale horizontally by adding nodes), 4 4SAP appliance or tailored datacenter integration 99 * Pre-installed software + support fully provided by SAP vs. more flexibility + reduced HW and operation costs GG Trigger SAP HANA hardware provisioning in time 9 9 * Make sure your product is released on SAP HANA and restrictions do not apply — see Product Availability Matrix (PAM) for your product at hitip://service sap.com/pam * Check if your add-ons and third-party products are supported on SAP HANA 4 4Plan transition and optimization of your custom code + test management 99 * See next slide for more information Project planning aspects Example of project plan for classical migration PRD to SAP HANA, “Sandbox” Source Target POT Copy > POT HW Purpose Tost uporage and migration stops wie 0py from production * Create upgrade ‘migration cookbook * Exacute mutiplo fectneal torations to faire th rocoss Note Perform ABAP code analysis, house Keeping before the gration DEV to SAP HANA DEV Source Target Dot > oH Purpose Estash SAP HANA ‘ov enwronmont on) * Refine cookbook Note * Uparade & maraton sts wl dior rom ‘roduton + Peron manstony code adaplations and ‘simple cod eplenizaions Ato SAP HANA QA Source (Target ‘G01 > aH Purpose © Estas SAP HANA ‘GA onarormont (aH) * Enhance cookbook + Tesing environment = Rocio resin = Cheracetnes PRDtoSAPHANA PRD to SAPHANA “Sandbox” “Sandbox” Source | Target Source (Target Pot Copy > PO1 HW POI Copy > POI HW Pupose Eupose © Mook ulover Final ress rehoarsal * Opimaaenty EE» Vala E2E Finalize cookbook Vale final « Finaize eutover cookbook " * Vanate euover plan Testing environment Feromanceesng PRO Migration '., Source | Target Pot > Por Purpose © Estabish now SAP HANA PRO onv + Utize downtime: mninzod approach ote © Exocute ond to-end business downtime reesely as defined ‘erin etover plan + Execute toenica stops prcisly as ‘etined in cookbook +» Pian code ‘opiization projets