Contact Us
×
How you can contact us:

LMDB Tools

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 Systems

The LMDB Reporting for systems 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.

  1. Open LMDB Tools
  2. Select "LMDB Reporting for ABAP, JAVA and HANA systems"
  3. Select the "Reporting Use Case" you want to use
  4. Enter the filters depending on the selected use case
  5. Click the "Go" button

LMDB Reporting for Hosts

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.

  1. Open LMDB Tools
  2. Select "LMDB Reporting for Hosts"
  3. Enter the filters to restrict the reported hosts
  4. Click the "Go" button

Cross Data Center Database Replication Association Maintenance

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.

  1. Open LMDB Tools
  2. Go to "Cross Data Center Database Replication Association Maintenance"
  3. Click "Create Cross Association"
  4. Select the database in the Primary Data Center, that has the logical association to the database in the Disaster Recovery Data Center (in our example the secondary DB)
  5. Select the database that belongs to it in the Disaster Recovery Data Center
  6. Click the "Create" button