Image courtesy SAP HANA Blog
Practical Guide on HANA System Replication including Setup, Operations and Monitoring HANA SR/DR
Setting up Scale Out, High Availability and Monitor HANAHANA scale out is unlike other database platforms, it can be simple but complex at the same time. Depending on the scenario, the in-memory nature of HANA services, the persistence layers and optional multi-tenancy (
BW Migration to HANA
We have taken careful steps to plan, prepare, perform and publish the process of upgrading and migrating BW to SAP HANA so that you will gain further understanding of the effort and major considerations. This week we continue with Part 2. These slides will be compiled into an eBook after we publish the final part 3, and be available for download then.
If HANA migration is in your roadmap for your current SAP environments (not new implementation), then they would likely fit into one of three scenarios below:
My Experience with the SAP HANA Certification Process
Have you tried monitoring your HANA multi-tenant environment? It's harder than it sounds. In prior posts, we wrote about:
- Multitenancy and how to convert HANA to a multi-tenant system, and
- What's up with HANA Multi-tenancy?
There are previously mentioned issues connecting the SAP HANA Administration Console to the tenant database because specific ports are required. There's not much documentation about connecting to a tenant for monitoring. Although most SAP Business Suite on HANA systems use DBACOCKPIT or Solution Manager (see our SAP Monitoring Tools Overview), it is typically connected to a single default tenant or automatically chosen during SAP installation.
It took a little detective work, but we've unraveled the mystery on how to connect locally, remotely via hdbsql and HANA studio to each tenant. Otherwise other monitoring tools can't be used, and we're left with tools like HANA Cockpit that only shows the first tenant as seen below (The indexserver on port 30003).
UPDATE 9/16/2015 Click here -> HANA Monitoring Multi-tenancy Environment
On June 23, 2015, I attended the SAP HANA Operations Summit at SAP Labs in Palo Alto and there was a lot of buzz around Multi-tenant Database Container (MDC) or Multi-tenancy. Recently, we also encountered some of our SAP monitoring customers who deployed MDC, so this publication will summarize some of the highlights and findings encountered with MDC.
There is a good summary of what Multitenancy and how to convert HANA to a multi-tenant system, so I won't restate them here, but if you have ever worked on a SAP MCOD (Multiple Component on One Database) system, it is similar. MDC is available as of SPS09 revision, either as new install or converted from a single database system.