SAP HANA Landscape SAP HANA Architecture SAP HANA Tool Overview SAP HANA Pre & Post Installation SAP HANA Operation Backup and Recovery Maintaining Users and Authorizations Data Provisioning Using SLT Monitoring and Troubleshooting Software Lifecycle Management Migration to SAP HANA High Availability and Disaster Tolerance www.globusit.in It is intended to provide an overview of the various aspects that are most relevant and important to understand and consider when planning a system landscape which features SAP HANA. As they relate to SAP HANA and its system landscape: What is SAP HANA SAP HANA Components SAP HANA Scenarios Rapid Deployment Solutions RDS SAP HANA Information Sources What is SAP HANA? SAP HANA Enterprise 1.0 is an in-memory computing appliance that combines SAP database software with pre-tuned server, storage, and networking hardware from one of several SAP hardware partners. It is designed to support real-time analytic and transactional processing. What are the technical components that make up HANA? The heart of SAP HANA Enterprise 1.0 is the SAP In-Memory Database 1.0, a massively parallel processing data store that melds row-based, column-based, and object-based storage techniques. Other components of SAP HANA Enterprise 1.0 include: SAP In-Memory Computing Studio, SAP Host Agent 7.2, SAPCAR 7.10, Sybase Replication Server 15, SAP HANA Load Controller 1.00, and, SAP Landscape Transformation 1 - SHC for ABA. SAP HANA Architecture Overview: The SAP HANA database is developed in C++ and keeps running on SUSE Linux Enterprise Server. SAP HANA database consists of various servers and the most important component is the Index Server. SAP HANA database comprises of Index Server, Name Server, Statistics Server, Preprocessor Server and XS Engine. Index Server: Index server is the main SAP HANA database component It contains the actual data stores and the engines for processing the data. The index server processes incoming SQL or MDX statements in the context authenticated sessions and transactions. Persistence Layer: The database persistence layer responsible for durability and atomicity of transactions. It ensures that the database can be restored to the most committed state after a restart and that transactions are either totally executed or totally undone. Preprocessor Server: The index server uses the preprocessor server for analyzing text data and extracting the information on which the text search capabilities are based. Name Server: The name server owns the information about the topology of SAP HANA system. In a distributed system, the name server knows where the components are running and which data is located on which server. Statistic Server: The statistics server collects information about status, performance and resource consumption from the other servers in the system.. The statistics server also provides a history of measurement data for further analysis. Session and Transaction Manager: The Transaction manager coordinates database transactions, and keeps track of running and closed transactions. When a transaction is committed or rolled back, the transaction manager informs the involved storage engines about this event so they can execute necessary actions. SAP HANA Operation This Technical Operations Manual provides an end-to-end picture of the administration tools available with SAP HANA and the key tasks that a system administrator needs to perform. Links to the relevant administration documentation of each of the components included in the SAP HANA solution are provided for details and step procedures Migration of SAP Systems to SAP HANA? SAP HANA in an on-premise landscape. Beginning with an overview of available migration path options, we provide a general recommendation and further aspects and guidance how to identify the best procedure for your requirements. Take these aspects into the discussion with your cross-functional teams and use them as basis for an individual assessment based on the boundary conditions you are facing.