• Save
Integrating SAP HANA into Your Landscape
 

Integrating SAP HANA into Your Landscape

on

  • 3,050 views

Discuss the various landscape options and supporting architecture that show how SAP HANA connects and provisions data, from both SAP and non-SAP systems. Understand the different sizing options and ...

Discuss the various landscape options and supporting architecture that show how SAP HANA connects and provisions data, from both SAP and non-SAP systems. Understand the different sizing options and partner platforms with basic and extended scenarios,including SAP NetWeaver Business Warehouse powered by SAP HANA, that show the integration of SAP HANA into your data center. With Matt Kangas.

Statistics

Views

Total Views
3,050
Views on SlideShare
3,050
Embed Views
0

Actions

Likes
11
Downloads
0
Comments
2

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Integrating SAP HANA into Your Landscape Integrating SAP HANA into Your Landscape Presentation Transcript

  • Hong Gun Cho / CSA TechnologyMatt Kangas / CSA – AmericasDennis Schwerer / CSA TechnologyOctober, 2012TEC110Integrating SAP HANA into Your Landscape
  • © 2012 SAP AG. All rights reserved. 2DisclaimerThis presentation outlines our general product direction and should not be relied on in making apurchase decision. This presentation is not subject to your license agreement or any other agreementwith SAP. SAP has no obligation to pursue any course of business outlined in this presentation or todevelop or release any functionality mentioned in this presentation. This presentation and SAPsstrategy and possible future developments are subject to change and may be changed by SAP at anytime for any reason without notice. This document is provided without a warranty of any kind, eitherexpress or implied, including but not limited to, the implied warranties of merchantability, fitness for aparticular purpose, or non-infringement. SAP assumes no responsibility for errors or omissions in thisdocument, except if such damages were caused by SAP intentionally or grossly negligent.
  • © 2012 SAP AG. All rights reserved. 3AgendaWhat is SAP HANA?SAP HANA – ScenariosDeploying SAP HANA – Landscape OptionsData ProvisioningSAP HANA Data Center Readiness Sizing, Installation Update Backup and Recovery Disaster Tolerance and High Availability
  • © 2012 SAP AG. All rights reserved. 4AgendaWhat is SAP HANA?SAP HANA – ScenariosDeploying SAP HANA – Landscape OptionsData ProvisioningSAP HANA Data Center Readiness Sizing, Installation Update Backup and Recovery Disaster Tolerance and High Availability
  • © 2012 SAP AG. All rights reserved. 5What is SAP HANA?HW technology innovations64 bit address space – 2 TB incurrent servers100 GB/s data throughputDramatic decline inprice/performanceMulticore architecture (8 x 8 core CPU perblade)Massive parallel scaling with many bladesOne blade ~$50,000 = 1 enterprise classserverRow and column storeCompressionPartitioningNo aggregate tablesInsert only on deltaSAP SW technology innovationsConvergence of improved hardware economics and technology innovations enables SAP to deliver on itsvision of the real-time enterprise with in-memory business applications
  • © 2012 SAP AG. All rights reserved. 6SAP HANAAn ideal platform for real-time businessSAP HANA AcceleratorsSpeed up business suitefunctionality through aside-by-side scenario withSAP HANA. Caching asubset of Suite Data inSAP HANASAP HANA AppsFunctional applicationswith indirect access toBusiness Suite data viareplication into SAPHANABusiness Warehousepowered by SAP HANAApplications build nativelyon SAP HANA thatenable on the fly insights,simulations and actions inhigh data volumeBusiness Suite powered bySAP HANABusiness Suite solutionfully integrated with SAPHANA as the optimizeddatabase solutionSAP HANA New AppsInteractive applicationsbased on SAP HANAdatabase withoutrequiring Business Suiteor Business One – butcan integrate with themSAPBusi-nessSuiteAnyDBCustomerMart AppHANA DBSAPBusi-nessSuiteAnyDBAppsHANA DBAnyDBOD/SF SolutionsAnyDBHANA DBMSQLHANA DBSAP Business OneHANA DBBWHANA DBSAP BusinessSuiteHANA DBAppsHANA DBHANA DBSAPBusi-nessSuiteAnyDBClient(Views)HANA DBClientSAPBusi-nessSuiteClientClientSAPBusi-nessOneERPCRMSCMSRMPLMViewsBWAppsSide-by-side scenarios Integrated scenariosSide-by-side scenarios Transformation scenariosHANAPlatform(Datamart)HANAAppsHANA Content(Reporting &Analytics)HANAAcceleratorsCloud onHANABusiness OneAnalytics onHANABusiness Oneon HANABW onHANABusinessSuite onHANAHANANew AppsOD: On Demand; SF: Success Factor
  • © 2012 SAP AG. All rights reserved. 7SAP In-Memory Strategy
  • © 2012 SAP AG. All rights reserved. 8AgendaWhat is SAP HANA?SAP HANA – ScenariosDeploying SAP HANA – Landscape OptionsData ProvisioningSAP HANA Data Center Readiness Sizing, Installation Update Backup and Recovery Disaster Tolerance and High Availability
  • © 2012 SAP AG. All rights reserved. 9Side-by-side scenariosAgile data martsSAP BusinessSuiteSAP BusinessWarehouse (BW)SAP HANADSDS/DXCDatabaseDatabaseAgile Data Marts Based on analytic data models(dimensional) Data has been transformed, in favor ofthe business problem at hand Typically contains no time critical dataand therefore utilize traditional ETLCore Value Proposition SAP HANA More Flexibility compared to EDWenvironmentDS: Data Services; DXC: Direct Extractor Connector
  • © 2012 SAP AG. All rights reserved. 10Side-by-side scenariosOperational data martsSAP HANADSSLTDatabaseOperational Data Marts Views calculate results for reports in realtime on the actual operational data No transformation during load step (onlyselection of relevant data if applicable) Real-time replication of time critical data(SLT)Core Value Proposition SAP HANA Real time reporting on operational dataDS: Data Services; DXC: Direct Extractor Connector; SLT: SAP Landscape TransformationSAP BusinessSuite
  • © 2012 SAP AG. All rights reserved. 11Side-by-side scenariosSAP HANA based acceleratorsSAP HANASLTDatabaseHANA Accelerators Turnkey solution to accelerate– Standard ABAP reports– Business processes in ERP Flexible reporting using Business ObjectsBI ClientsCore Value Proposition SAP HANA Turnkey accelerator for ERP customersDXC: Direct Extractor Connector; SLT: SAP Landscape Transformation; DBSL: Database Shared LibrarySAP BusinessSuiteDXCDBSL
  • © 2012 SAP AG. All rights reserved. 12Integration scenariosSAP HANA as primary persistenceSAP HANASAP NetWeaver BW, powered by SAP HANASAP Business Suite, powered by SAP HANA* SAP HANA Database becomes primarypersistence of ABAP Application server All Objects and BW loading procedures areaccelerated by in-memory technologyCore Value Proposition SAP HANA Speed and simplification for SAP BW /Business Suite*) planned; BW: Business WarehouseSAP NetWeaverAS ABAP
  • © 2012 SAP AG. All rights reserved. 13Transformation scenariosSAP HANA as platformSAP HANANext Generation HANA Apps NetWeaver AS ABAP leveraging HANA iOS apps running against HANA Java applications running against HANACore Value Proposition SAP HANA Simplification: lean code – mean appsXS EngineNew Apps(HTML5/JavaScript)New Apps (ODBC,JDBC, …)
  • © 2012 SAP AG. All rights reserved. 14SAP HANAOne OLTP & OLAP data store
  • © 2012 SAP AG. All rights reserved. 15AgendaWhat is SAP HANA?SAP HANA – ScenariosDeploying SAP HANA – Landscape OptionsData ProvisioningSAP HANA Data Center Readiness Sizing, Installation Update Backup and Recovery Disaster Tolerance and High Availability
  • © 2012 SAP AG. All rights reserved. 16SAP HANA editionsThe different flavors of SAP HANA product offering
  • © 2012 SAP AG. All rights reserved. 17SAP HANADeployment viewSAP HANA ApplianceSoftware Update ManagerSAP Host AgentSAP HANA Studio RepositorySAP HANA Database Node 2 Node n…Name ServerIndex ServerStatistics ServerPreprocessorIndex ServerPreprocessorIndex ServerPreprocessorSingle host configurationMulti-node cluster configurationMaintains landscape informationHolds data and executes all operationsCollects performance data about HANAText analysis pre-processorRepository for HANA Studio updatesEnables remote start/stopManages SW updates for HANAShared persistency for fail-over and recoverySAP Host Agent SAP Host AgentName Server Name Server
  • © 2012 SAP AG. All rights reserved. 18SAP HANAAppliance software packagingAvailable in 3+ flavors SAP HANA Platform Edition SAP HANA Enterprise Edition– Including data provisioning (SLT) SAP HANA for BW– BW database onlyAvailable through 7+ hardware partners
  • © 2012 SAP AG. All rights reserved. 19SAP HANA system landscapeConnectivity overviewSAP HANASAP BusinessObjects BI SuiteFor analytical scenariosusing BI suite productsHANA UI forInformation AccessFor search and textcapabilities inside SAPHANAHANA InformationComposerFor easy data upload intoSAP HANASAP NW 7.3Business WarehousePowered by SAP HANA asprimary persistence belowSAP NW 7.3 AS ABAPSAP BusinessSuite**) Planned: SAP HANA asprimary persistence also forSAP Business Suite systemsHANA AppsApplications runningnatively on / against SAPHANA DatabaseR runtimeFor direct integration withR-runtime librariesSAP SolutionManagerFor Monitoring andAdministration (DBACockpit,LVM, CTS+)HANA StudioFor administration,modeling and lifecyclemanagement of the SAPHANA systemSAP ServiceMarketplace (SMP)For downloading SP-stacks and patchesSAP Support(OSS)For remote support of theSAP HANA systemSAP HANADatabaseHostagent/SMD AgentSUM forSAP HANA…Side-by-SidePrimary Persistence Platform / RuntimeDirect ExtractorConnection (DXC)Data acquisition from SAPBusiness ContentDataSource Extractorse.g. SAP NW BWSAP Data ServicesFor ETL basedloadinge.g. 3rd party EDWSAP LandscapeTransformation(SLT)For real-time replicatione.g. SAP ERP
  • © 2012 SAP AG. All rights reserved. 20Landscape consolidation optionsSupport for multiple application on SAP HANA (MCOD) SAP generally does not support the deployment of multiple applications (or scenarios) within a single SAPHANA system in a production enviornment SAP does support running certain application types together in one production SAP HANA system. This“White List” of applications that can run together with other applications on one productive SAP HANA system ismaintained in SAP Note 1661202HANA DB Node HANA DB Node HANA DB Node HANA DB Node HANA DB Nodee.g. CO-PA Accelerator (Non-BW Schema)e.g. BW Schema
  • © 2012 SAP AG. All rights reserved. 21SAP HANA “classic” scenario1x SAP HANA database, 1x application, 1x schemaImplications/Remarks: Dedicated Scenario Ownership Independent Lifecycle Management (SP, revisions, backups…) Common setup for productive system landscapesExamples Production NW 7.3 BW, powered by SAP HANA Production Business Suite / ERP, powered by SAP HANA*SAP HANA<HDB>Schema ABCAS ABAPSID: ABCApp App App*) planned
  • © 2012 SAP AG. All rights reserved. 22SAP HANA “MCOD” scenario1x SAP HANA database, n- applications and schemasImplications/Remarks: Lower TCO / hardware usage Applications reside in same database installation SAP generally does not support the deployment of multipleapplications (MCOD), besides explicit listed scenarios withinSAP Note 1661202 (Support for multiple applications on SAPHANA)Examples SAP NW 7.3 together with Business Suite Accelerators Smaller customer projects & POCsSAP HANA<HDB>Schema ABCAS ABAPSID: ABCApp AppSchema XYZApplicationXYZApp
  • © 2012 SAP AG. All rights reserved. 23SAP HANA “MCOS” scenarion- SAP HANA databases, applications and schemasImplications/Remarks: Lower system provisioning costs for non-production systems Individual lifecycle for the individual databases No CPU/Memory resource management SAP does support running multiple SAP HANA databases onlyfor non-production (DEV, QA, test, etc.) SAP HANA appliances,as stated in SAP Note 1681092 (Multiple SAP HANA databaseson a SAP HANA appliance) for more detailsExamples Combine Dev / Q / Demo – Systems in one physical SAPHANASAP HANA<HDB1>Schema ABCAS ABAPSID: ABCApp AppAS ABAPSID: XYZApp App<HDB2>Schema XYZ
  • © 2012 SAP AG. All rights reserved. 24AgendaWhat is SAP HANA?SAP HANA – ScenariosDeploying SAP HANA – Landscape OptionsData ProvisioningSAP HANA Data Center Readiness Sizing, Installation Update Backup and Recovery Disaster Tolerance and High Availability
  • © 2012 SAP AG. All rights reserved. 25Data Provisioning with SAP HANA 1.0SAP In-Memory Computing StudioSAP In-Memory DatabaseCalculation andPlanning EngineRow & ColumnStorage* SAP HANA –SP05SAP LTReplicationServerSAP BusinessSuiteSAP BWNon SAPData SourcesActivationQueueIn memory DSOSAP BOBJData ServicesSAP SybaseReplication ServerSAP HANA DirectExtractorConnection**SAP Event StreamProcessor *Trigger Based,Real TimeETL, BatchExtractorBatchXS EngineLog BasedTrading & OrderManagement SystemsODBCSAP HANAHttp/HttpsDB ConnectionODBC** SAP ERP & BW ExtractorsEvent StreamsData SourcesSAP BusinessObjectstoolsOther query toolsSQL BICS SQL MDXECDA/ODBC
  • © 2012 SAP AG. All rights reserved. 26SAP HANA Data Provisioning: PositioningSAP LT Replication ServerSAP LT Replication Server (SLT) is positioned for real-time data replication from SAP and non-SAP sources(SAP supported data bases only)-> Mainly recommended for real-time data replication business scenariosSAP Business Objects Data ServicesSAP Business Objects Data Services (DS) is positioned for batch load-based data replication from non-SAPsources and SAP sources (with complex ETL requirements)-> Mainly recommended for batch type data replication business scenariosOther Data Provisioning Options: SAP HANA Direct Extractor Connection (DXC) is available as a simple option in ETL (batch) scenarios fordata replication from existing SAP Data Source extractors into SAP HANA Sybase Event Stream Processor (ESP)*: will be available for replicating real time event streams fromSybase ESP into SAP HANA* As part of SAP HANA Roadmap
  • © 2012 SAP AG. All rights reserved. 27LT Replication Server Leverages Proven SLO TechnologiesApplication Lifecycle Management SLO* technologies have been used sincemore than 10 years in hundred of projectsper year Key offerings foster SAP‘s ApplicationLifecycle Management concept SAP LT Replication Server leveragesseveral SLO technologies*) System Landscape Optimization
  • © 2012 SAP AG. All rights reserved. 28SAP HANA systemSAP non-SAP source systemOverviewSAP LT Replication ServerApplication TableTrigger BasedDelta RecordingReplication EngineApplication TableRFCConnectionHANA StudioDBConnectionReplication ConfigurationConnection(s) between source system and SAP HANA system aredefined as “Configuration” on the SAP LT Replication ServerData load and replication aretriggered via SAP HANA StudioSAP LT Replication Server does not have to be a separate SAPsystem and can run on any SAP system with SAP NetWeaver 7.02ABAP stack (Kernel 7.20EXT)
  • © 2012 SAP AG. All rights reserved. 29The Set-up of LT Replication Server is Fast and SimpleConfiguration steps for SAP LT Replication Server Define a schema for each source system Define connection to source system Define DB connection into SAP HANA Define replication frequency (real-time; frequency for scheduled replication) Define maximum number of background jobs for data replicationInstallation aspects Source system(s): use respective DMIS add-on LT Replication Server: use add-on DMIS_2010_1_700 with SP07;other system requirements (NW 7.02; SAP Kernel 7.20EXT) apply Apply SPS04 for SAP HANA 1.0Set-up of data replication in SAP HANA Select relevant source system Start (initial load only and / or continuous replication)
  • © 2012 SAP AG. All rights reserved. 30SAP HANA systemSAP LT Replication ServerSAP source systemLT Replication Concept: Trigger-Based Approach Architecture and keybuilding blocksEfficient initialization of datareplication based on DB triggerand delta logging concept(as with NearZero downtime approach)Flexible and reliable replication process, incl.data migration(as used for TDMS and SAP LT)Fast data replication via DB connectLT replication functionality is fullyintegrated with HANA Modeler UIApplication table Logging tableDB triggerRead module Structure mapping &TransformationApplication tableWrite moduleRFCConnectionDBConnection
  • © 2012 SAP AG. All rights reserved. 31SAP HANA systemSAP LT Replication ServerNon SAP source systemLT Replication Concept: Trigger-Based ApproachReplication from non-SAP sourcesIn a first step, SAP LT Replication Server transfers all metadata table definitions from the non-SAP source system tothe HANA system. From the HANA Studio perspective, non-SAP source replication works as for SAP sources.When a table replication is started, SAP LT Replication Server creates logging tables within the source system. As adifference, the read modules are created in the SAP LT Replication Server. The connection the non-SAP sourcesystem is established as a database connection.Application table Logging tableDB triggerRead moduleStructure mapping &TransformationApplication tableWrite moduleDBConnectionDBConnection
  • © 2012 SAP AG. All rights reserved. 32Multi System Support 1/2SAP HANA systemSource systemsSystem ASystem BSchema 1Schema 2Source systems areconnected to separateHANA schema on thesame HANA SystemSAP HANA systemSource systemsSystem ASystem BSchema 1Schema 1Source systems areconnected to separateHANA systems. Schemaname can be equal ordifferentSAP HANA systemSource systemsSystem ASystem BSchema 1Source systems areconnected to sameHANA system and alsothe same schema
  • © 2012 SAP AG. All rights reserved. 33SAP HANA systemsSAP Source systemSchema 1Schema 2System AMulti-System Support 2/21:N Replication for SAP source systemsIf one source system is connected toseveral target schemas (currently up to 1:4supported), the relevant target schemacan be selected in the data provisioningUI.SAP source system isconnected to separateHANA systems or to thesame system withdifferent schema name.
  • © 2012 SAP AG. All rights reserved. 34AgendaWhat is SAP HANA?SAP HANA – ScenariosDeploying SAP HANA – Landscape OptionsData ProvisioningSAP HANA Data Center Readiness Sizing, Installation Update Backup and Recovery Disaster Tolerance and High Availability
  • © 2012 SAP AG. All rights reserved. 35SAP HANA Data Center ReadinessQuick Overview3rd party tooling Backups to 3rd partybackup tools such asIBM Tivoli, HP DataProtector, SymantecNetbackup etc. Integration with 3rdparty monitor-ingtools like IBM Tivoli,HP Service Guardetc.(In preparation)HighAvailability In case ofhardware orsystem failure thestandbynode/systemtakes over in onedata centerDisaster Tolerance Failover to adifferent HANAinstance inanother datacenter in case ofa catastrophe. Automatic andmanualprocedurespossibleBackup &Recovery Full Data Backup Log BackupDisaster Recovery Deal with pointfailures and bringback a system toa consistent statefrom backup(Bare MetalRestore)Data Center ReadinessSAP HANAAvailable today Available today Available today Available soon In preparationMonitoring &Administration Holisticmonitoring,alerting andscheduling withE2E support bySAP Solutionmanager for SAPHANA as anapplianceSecurity & Auditing
  • © 2012 SAP AG. All rights reserved. 36AgendaWhat is SAP HANA?SAP HANA – ScenariosDeploying SAP HANA – Landscape OptionsData ProvisioningSAP HANA Data Center Readiness Sizing, Installation Update Backup and Recovery Disaster Tolerance and High Availability
  • © 2012 SAP AG. All rights reserved. 37SAP HANA - Implications of being an ApplianceClassic software deliveryon-premise solutions SAP ships only the software Customer is responsible for entire product lifecycleAppliance deliverykind of “SaaS on-site customer” SAP defines the solution together with its partners SAP & partners control product lifecycleApplianceOperationConceptsInfrastructure *Operation *Setup / ConsultingSupport(Software, Maintenance andInfrastructure)SAP Development Software and LicensesHW- and TechnologyPartnersInfrastructureOperationSetup/ ConsultingSupport(Software, Maintenance andInfrastructure)SAP Development Software and Licenses* Might be outsourced or owned by customerSAP responsibilityCustomer’sresponsibilityPartnersresponsibility
  • © 2012 SAP AG. All rights reserved. 38SAP HANA: HW Platforms Single Node• 2 x 10 core Westmere EX (Intel 2 socket system)• 128 GB Main memory• 160 GB PCIe-Flash / SSD for Log volume• 1 TB SAS / SSD for Data volume• 3 x 1 GB n/w or 1 x 10GB n/w (trunk), Redundant n/w infrastructure• 2 x 10 core Westmere EX (Intel 2 or 4 sockets system)• 256 GB Main memory• 320 GB PCIe-Flash / SSD for Log volume• 1 TB SAS / SSD for Data volume• 3 x 1 GB n/w or 1 x 10GB n/w (trunk), Redundant n/w infrastructure• 4 x 10 core Westmere EX (Intel 4 or 8 socket system)• 512 GB Main memory• 640 GB PCIe-Flash / SSD• 2 TB SAS / SSD for Data volume• 3 x 1 GB n/w or 1 x 10GB n/w (trunk), Redundant n/w infrastructure• 8 x 10 Westmere EX core Intel (Intel 8 socket system)• 1 TB Main memory• 1.2 TB PCIe-Flash / SSD• 4 TB SAS / SSD for Data volume• 3 x 1 GB n/w or 1 x 10GB n/w (trunk), Redundant n/w infrastructureXSSMLPlease check the SAP HANA product availability matrix for more information about the validated hardware platforms:https://service.sap.com/pam (search for HANA)
  • © 2012 SAP AG. All rights reserved. 39SAP HANA applianceDefined T-shirt sizesSAP HANA appliance – T-Shirt sizesS – Model (2 CPU sockets) 2 x 8/10core CPU, 128GB RAM, 320GB Flash log volume, 1TB SSD/SAS data volumeS+ - Model (4 CPU sockets enabling scale-up) 2 x 8/10core CPU, 256GB RAM, 320GB Flash log volume, 1TB SSD/SAS data volumeM – Model (4 CPU sockets) 4 x 8/10core CPU, 512GB RAM, 640GB Flash log volume, 2TB SSD/SAS data volumeM+ - Model (8 CPU sockets enabling scale-up) 4 x 8/10core CPU, 512GB RAM, 640GB Flash log volume, 2TB SSD/SAS data volumeL – Model (8 CPU sockets) 8 x 8/10core CPU, 1TB RAM, 1.2TB Flash log volume, 4TB SSD/SAS data volumeXL – Model (n CPU sockets) Scale out solution based on multiple nodesFor sizing informationsee Notes 1514966(SAP HANA 1.0:Sizing SAP In-Memory Database)and 1637145 (SAPBW on HANA: SizingSAP In-MemoryDatabase)
  • © 2012 SAP AG. All rights reserved. 40The SAP HANA appliance software from an installation point of view:Enablement for factory pre-installation & on-site configurationSAP HANA Installation Following the SAP appliance delivery model– The HW vendor provides factory pre-installation for HW, OS and SAP software– The HW vendor may add specific best-practices and SAP HANA software configuration– The HW vendor finalize installation by an on-site setup and configuration of the HANA components*– Customer starts with establishment of replication / connectivity to data source systems and BI clients**HW deliveredto customerHANA Systemset upHANA Scenariorunsfactory pre-install on-site serviceon-site setupHW & OS assemblySAP SWinstallationFactorySmoke testOn-sitesetupTechnicalconfigurationOn-sitesmoke testSetupReplicationBusinessConfiguration* Includes deployment of SAP HANA system in customer data center, connectivity to network, SAP system ID adaption, Solution Manager and SAP Router connectivity, SSL enablement** Includes deployment of additional replication components e.g. on source system and/or BI client components like BI 4.0 and SBOP Explorer
  • © 2012 SAP AG. All rights reserved. 41SAP HANA SP Stack Update – Process DescriptionSAP HANA appliance software SAP HANA database & client SAP HANA studio repository SAP HANA load controllerSAP Host AgentSUM for SAP HANASAP HANA studio (Eclipse)LM perspectiveMaintenance OptimizerService MarketplaceAll remote connections are done via secure web services.1. Perform Software Update Manager for SAP HANA self-update2. Detect components in the SAP HANA landscape3. Get latest SP stack information from SMP4. Download required component updates5. Update components on the SAP HANA systemInternet
  • © 2012 SAP AG. All rights reserved. 42AgendaWhat is SAP HANA?SAP HANA – ScenariosDeploying SAP HANA – Landscape OptionsData ProvisioningSAP HANA Data Center Readiness Sizing, Installation Update Backup and Recovery Disaster Tolerance and High Availability
  • © 2012 SAP AG. All rights reserved. 43HANASAP HANA Persistence:In-Memory Data Is Regularly Saved to DiskData: SQL data and undo log information Additional HANA information,such as modeling data Kept in-memory to ensure maximum performance Write process is asynchronouslyLog: Information about data changes (redo log) Directly saved to persistent storage when transactionis committed Cyclical overwrite (only after backup)Savepoint: Changed data and undo log is written from memoryto persistent storage Automatic At least every 5 minutes (customizable)MemoryDataPersistent StorageRegular automaticsavepointsInformation aboutdata changesLogVolumeDataVolumes
  • © 2012 SAP AG. All rights reserved. 44In-memory computing is secureThe SAP in-memory database holds the bulk of its data in memory for maximum performance, but stilluses persistent storage to provide a fallback in case of failure. The log is capturing all changes bydatabase transactions (redo logs)Data and undo log information (part of data) are automatically saved to disk at regular savepointsThe log is also saved to disk continuously and synchronously after each COMMIT of a databasetransaction (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)SAP HANA Persistence:Regular Saving of In-Memory Data to Disk, RestartSavepoint:Data & undo log is writtento disk (data area)1Continously and after each COMMIT,redo log is written to disk (log area)2Power failure3Time
  • © 2012 SAP AG. All rights reserved. 45Backup and RecoveryData backupsData backups save the content of the data area to a different location in the file system. Dependingon the usage scenario, this includes the replicated business data from ERP and all the modelingdata.Data backups are carried out manually: SAP HANA studio DBA Cockpit SQL commands (command line)Scheduling: Using scripts (via the SQL interface) Planning calendar in DBA CockpitBackup frequency Regular data backups required, but no general guidelines available(depends on the usage scenario)Space requirements Only occupied space is backed up
  • © 2012 SAP AG. All rights reserved. 46SAP HANA ServerSAP HANA Backup/RecoveryData backup: Only payload is backed upShared Backup Directory(staging area)Name ServerDataIndex ServerStatistics ServerDATA_BACKUP_0001DATA_BACKUP_0002DATA_BACKUP_0003DataBackupSavepointDataBackupSavepointDataBackupSavepointDATA_BACKUP_0000
  • © 2012 SAP AG. All rights reserved. 47Backup and RecoverySupport for external backup toolsAvailable today via Backup Staging AreaFurther integration planned for HANA SPS5 (End 2012):Use of operating system pipes to connect directly to external backup toolsNew interface standard to be defined: Backint for HANA Backint (in general) is an established standard by SAP and extended over time Extended for pipes for some years (e.g. Backint for MaxDB) Further minor extends for the use with SAP HANA Description and simulator already available to start adoption process on external tools nowFirst contacts to Symantec (Netbackup) IBM (Tivoli) HP (Data Protector) etc.
  • © 2012 SAP AG. All rights reserved. 48AgendaWhat is SAP HANA?SAP HANA – ScenariosDeploying SAP HANA – Landscape OptionsData ProvisioningSAP HANA Data Center Readiness Sizing, Installation Update Backup and Recovery Disaster Tolerance and High Availability
  • © 2012 SAP AG. All rights reserved. 49High Availability – Disaster ToleranceBusiness ContinuityHigh Availabilityper DataCenterDisaster Tolerancebetween DataCentersScale-Out with Standby e.g. MetroClusterDisaster Recovery: Recovery of HANA as a complete rebuild of a server(Bare Metal Restore)
  • © 2012 SAP AG. All rights reserved. 50Scale OutHigh AvailabilityHigh Availability configuration N active servers in one cluster M standby server(s) in one cluster Shared file system for all serversServices Name and index server on all nodes Statistics server (only on one active server) Name server active on StandbyFailover Server X fails Server N+1 reads indexes from shared storage andconnects to logical connection of server XServer 1Server 2Server 3Server 4Server 5Server 6Standby ServerSharedStorage
  • © 2012 SAP AG. All rights reserved. 51HANA High AvailabilityNode failover (standby)Different implementation of High Availability by HW partnersHP, Fujitsu, etc. IBMNameServerIndexServerStandbyNameServerIndexServerNameServerIndexServerDataDisksLogDisksDataDisksLogDisksDataDisksLogDisksGPFSGPFS
  • © 2012 SAP AG. All rights reserved. 52SAP HANA Disaster ToleranceDifferent ideas of solutions1. Storage based mirroring of SAP HANA disk areas controlled by storage technology First synchronous implementation (available soon, currently in validation) Afterwards asynchronous implementation following (planned)2. WARM standby: DATA and LOG content is continuously transferred to secondary site undercontrol of SAP HANA database Fast switch-over times because secondary site has preloaded DATA First synchronous implementation (planned for SAP HANA SPS5, End 2012) Afterwards asynchronous implementation following (planned)3. HOT Standby: DATA content is only initially transferred to secondary site, afterwardscontinuous LOG transfer and LOG replay on secondary site LOG is provided to secondary site on transactional basis (COMMIT) controlled by SAP HANA database (including initialDATA transfer) Fastest switch-over times, sec. site preloaded and rolled forward on COMMIT basis First synchronous implementation (mid term planning) Afterwards asynchronous implementation following (mid term planning)
  • © 2012 SAP AG. All rights reserved. 53Data Center 2Data Center 1SAP HANA Disaster Tolerance: Storage MirroringCluster across Data CentersOS: MountsDataVolumesLogVolumeOS: DNS, hostnamesPrimaryNameServerIndexserverNameServerIndexserverNameServerIndexserverSecondary(inactive)NameServerIndexserverNameServerIndexserverNameServerIndexserverHASolutionPartnerStorageMirroringClients Application ServersHASolutionPartnerDataVolumesLogVolumeDataVolumesLogVolumeDataVolumesLogVolume
  • © 2012 SAP AG. All rights reserved. 54Data Center 2Data Center 1SAP HANA Disaster Tolerance: Storage MirroringCluster across Data Centers with QA & Dev. on secondary site (planned)OS: MountsDataVolumesLogVolumeOS: DNS, hostnamesPrimaryNameServerIndexserverNameServerIndexserverNameServerIndexserverSecondaryProd. (inactive), QA&DEV (active)NameServerIndexserverNameServerIndexserverNameServerIndexserverHASolutionPartnerStorageMirroringClients Application ServersHASolutionPartnerDataVolumesLogVolumeDataVolumesLogVolumeDataVolumesLogVolumeDataVolumesLogVolumeDataVolumesLogVolume
  • © 2012 SAP AG. All rights reserved. 55SAP HANA Disaster Tolerance: WARM StandbyCluster across Data Centers with SAP HANA controlled transfer (planned)Data Center 2Data Center 1OS: MountsDataVolumesLogVolumeOS: DNS, hostnamesPrimary(active)NameServerIndexserverNameServerIndexserverNameServerIndexserverSecondary(active, data pre-loaded)NameServerIndexserverNameServerIndexserverNameServerIndexserverHASolutionPartnerClients Application ServersHASolutionPartnerDataVolumesLogVolumeDataVolumesLogVolumeDataVolumesLogVolumeTransferbyHANAdatabasekernel
  • © 2012 SAP AG. All rights reserved. 56SAP HANA Data Center Readiness:Availability of solutionsHigh Availability per Data Center – Scale-Out with StandbyAvailable todayHW partners: Fujitsu, HP, IBM, more to comeHigh Availability across Data Centers – Disaster ToleranceStorage Mirroring: Planned for Mid 2012HW partners, planned: Fujitsu, HP, IBM, more to comeMirroring solutions depend on HW partner technologyFurther detailed information about the solutions offered by HW partners.WARM standby: Planned for SPS5, End of 2012Partly HW partner related, especially external cluster management (network)Similar outside implementation like storage mirroringThis is the current state of planning and may be changed by SAP at any time.
  • © 2012 SAP AG. All rights reserved. 57SAP HANA TimelineSPS227. June 2011SPS4Mid 2012SPS37. Nov 2011SPS5End 2012SAP BW powered by SAP HANASAP HANA Data Marts Round-Off ReleaseThis is the current state of planning and may be changed by SAP at any time.
  • © 2012 SAP AG. All rights reserved. 58SAP HANA Timeline – Data Center Readiness relatedSPS227. June 2011SPS4Mid 2012SPS37. Nov 2011SPS5End 2012Scale-Out with StandbyPoint in Time RecoverySolution Manager IntegrationSSL connection encryptionNew PersistenceScale-OutDisaster ToleranceSystem Copy via B&RBackup CatalogExternal Backup toolsWARM Standby…This is the current state of planning and may be changed by SAP at any time.
  • Thank You!Matt Kangas Hong Gun Cho Dennis SchwererCSA Americas CSA Technology CSA Technology
  • © 2012 SAP AG. All rights reserved. 60The BW on SAP HANA CookbookThe Cookbook provides an overviewand consolidates guides and notesrelevant to moving BW to SAP HANAin one location.It was created together withcustomers and has features to takenotes and ask questions withincontext.https://cookbook.experiencesaphana.com
  • © 2012 SAP AG. All rights reserved. 61Further InformationRelated Workshop/Lectures at SAP TechEd 2012ALM105 SAP HANA – Operations, High Availability, and Data Center Readiness Lecture (1h)ALM161 SAP HANA operations – Basics Hands-on Workshop (2hr)ALM360 SAP HANA operations – Advanced Hands-on Workshop (2hr)EIM106 SAP HANA – Data Provisioning for Replication with SAP and non-SAP Lecture (1hr)ApplicationsEIM109 Search-Based Applications on Unstructured Content in SAP HANA Lecture (1h)EIM160 Landscape Transformation Replicaiton Server – Real-Time Data Lecture (2h)Integration into SAP HANAEIM163 Loading Data in Batch Mode into SAP HANA with Data Services and Lecture (2h)ConnectionsEIM201 SAP HANA Architecture and Technology Lecture (1h)EIM204 Applications Powered by SAP HANA Lecture (2h)SIS201 All You Need To Know About Security with SAP HANA Lecture (1h)TEC105 SAP HANA Database for SAP Business Suite Lecture (1h)
  • © 2012 SAP AG. All rights reserved. 62Further InformationSAP Public Webscn.sap.com/hanaexperiencesaphana.comscn.sap.com/community/hana-in-memoryhelp.sap.com/hana_applianceSAP Education and Certification Opportunitiestraining.sap.com/de/en/cirriculm/hana-sap-hanatraining.sap.com/bundles/product/sap-hanaWatch SAP TechEd Onlinewww.sapteched.com/online
  • FeedbackPlease complete your session evaluation for TEC110.Thanks for attending this SAP TechEd session.
  • © 2012 SAP AG. All rights reserved. 64No part of this publication may be reproduced or transmitted in any form or for any purpose without the expresspermission of SAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components ofother software vendors.Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registered trademarks ofMicrosoft Corporation.IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, Systemz10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture, Power Systems, POWER7,POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC, BladeCenter, System Storage, Storwize,XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere,Tivoli, Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation.Linux is the registered trademark of Linus Torvalds in the United States and other countries.Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of AdobeSystems Incorporated in the United States and other countries.Oracle and Java are registered trademarks of Oracle and its affiliates.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks orregistered trademarks of Citrix Systems Inc.HTML, XML, XHTML, and W3C are trademarks or registered trademarks of W3C®, World Wide WebConsortium, Massachusetts Institute of Technology.Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C, Retina, Safari, Siri,and Xcode are trademarks or registered trademarks of Apple Inc.IOS is a registered trademark of Cisco Systems Inc.RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerryStorm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App World are trademarks or registeredtrademarks of Research in Motion Limited.© 2012 SAP AG. All rights reserved.Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads,Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater, Google Voice,Google Mail, Gmail, YouTube, Dalvik and Android are trademarks or registered trademarks of Google Inc.INTERMEC is a registered trademark of Intermec Technologies Corporation.Wi-Fi is a registered trademark of Wi-Fi Alliance.Bluetooth is a registered trademark of Bluetooth SIG Inc.Motorola is a registered trademark of Motorola Trademark Holdings LLC.Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork,SAP HANA, and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and other countries.Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, WebIntelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objectsis an SAP company.Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and servicesmentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc.Sybase is an SAP company.Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks of Crossgate AGin Germany and other countries. Crossgate is an SAP company.All other product and service names mentioned are the trademarks of their respective companies. Datacontained in this document serves informational purposes only. National product specifications may vary.The information in this document is proprietary to SAP. No part of this document may be reproduced, copied,or transmitted in any form or for any purpose without the express prior written permission of SAP AG.