Hi,
We are in the middle of a move from 2.4/bdb to 2.5/mdb, and I am working on implementing monitoring for the new systems.
In the 2.4/bdb environment, we run several scripts to check sanity of the servers:
* checks of the contextCSN value across the masters/slaves * regular db_verify on the actual bdb files * compare all DN & entryCSN in the DB across all the masters/slaves * do a write on a master, and verify that it is replicated everywhere
Most of these things can be done similarly in 2.4/bdb and 2.5/mbd but not the db_verify, which is bdb specific.
I don't find a lot of info on the maintenance / integrity checks that can be done on mdb databases. In fact: Mostly what I can find is: "MDB uses no caching and requires no tuning to deliver maximum search performance"
That is very good. :-) We have already discovered that we need to increase maxsize, as our database is (much) larger than 10MB.
Two questions:
- Is there really nothing else to tune or adjust?
- Is there really no way to verify the internal structures within the MDB file, to make sure everything is valid and healthy? Perhaps things I have missed with our four checks above?
Anyone else with tips and tricks on daily maintenance or monitoring? Scripts to share..? Perhaps zabbix templates..?
If anyone would be interested in (for example) my script to verify the complete directory contents based on DN&entryCSN across a (multi)master/(multi)slave setup, I'd be happy to share too, of course.
Thanks!