-
Technical Assistance
Request product support from SAP
-
Non-Technical Assistance
Request non-product support or provide feedback on SAP Support Portal site
Technical Assistance
Request product support from SAP
Non-Technical Assistance
Request non-product support or provide feedback on SAP Support Portal site
LMDB Tools comprises several pages that allow you to report on the LMDB content or to maintain advanced configurations, like disaster recovery (DR)
LMDB Reporting for technical systems offers information about the header data of technical systems such as EXTSID, system type, Installation Number, short display text, Lifecycle status, and IT Admin role. Additionally, the system database, status of data supplier completeness checks, and consistency checks are provided. You can customize the columns and order of the result set and export it to Microsoft Excel.
LMDB Reporting for Technical Instances offers information about technical instances for ABAP, JAVA, and HANA systems like instance host, type, and name. You can customize the columns and order of the result set and export it to Microsoft Excel.
The LMDB Reporting for Products and Software Components offers reporting in the LMDB for software components and product versions. Based on a reporting use case, different filter options are available to perform searches and create reports on the objects in LMDB. You can customize the columns and order of the result set and export it to Microsoft Excel.
LMDB Reporting for Hosts provides an overview of all currently existing hosts. In addition to the default columns, you can also display specific additional attributes of the hosts. Furthermore, you can perform searches, customize columns, sort, and export the table content to Microsoft Excel.
Cross Datacenter Database Replication Association Maintenance enables you to maintain associations across different namespaces in the LMDB.
This concerns the "Disaster Recovery of Databases" use case, where the whole database setup is done in multiple data centers, resulting in a setup using multiple namespaces. An overall description of disaster recovery of SAP HANA is provided here.
For the technical implementation in the LMDB, you should consider the following example:
For disaster recovery (DR), we assume there are two data centers: one in Rot, where the primary and secondary databases are located, and one in Amsterdam, where the tertiary database is located.
The registration information from Rot is sent via reverse proxy. It arrives in the persistence layer via the WBEM client and CIMOM. The databases are stored in Namespace 1. In LMDB, the primary database is associated with the secondary database. The secondary database is also associated with the tertiary database. However, since the tertiary database is not in Namespace 1, it is only an empty placeholder.
The data center in Amsterdam reports the information for the tertiary database via the reverse proxy into LMDB. The database is reported for Namespace 2. The database appears to be complete. There are no associations to the databases in Namespace 1. This is our starting point.
We have enhanced the LMDB with the LMDB tool Cross Data Center Database Replication Association Maintenance to realize associations between databases in different namespaces. In this tool, you can create the namespace-independent associations.
In case of a failover, the primary and disaster recovery databases are exchanged.