Hi,
We have a running openldap installation (2.4.39) - a single master - with cn=config and hdb backend.
So, config has the branches:
I know we must slapcat our data and slapadd it in mdb afterwards.
The question is: what changes should be done in the config DIT (and how) so that the config changes from hdb backend to mdb backend?
Is it enough to slapcat config, then change:
olcDatabase from {1}hdb to {1}mdb
and:
objectClass from olcHdbConfig to olcMdbConfig
...?
Anything else?
Can we safely delete all values of the olcDbConfig attribute which originate from converting from "DB_CONFIG"?
What attributes can we safely remove?
Thanks, Nick
Nick Milas wrote:
Hi,
We have a running openldap installation (2.4.39) - a single master - with cn=config and hdb backend.
So, config has the branches:
I know we must slapcat our data and slapadd it in mdb afterwards.
The question is: what changes should be done in the config DIT (and how) so that the config changes from hdb backend to mdb backend?
Is it enough to slapcat config, then change:
olcDatabase from {1}hdb to {1}mdband:
objectClass from olcHdbConfig to olcMdbConfig...?
That's a start.
Anything else?
Can we safely delete all values of the olcDbConfig attribute which originate from converting from "DB_CONFIG"?
Not only *can you* - you *must*.
What attributes can we safely remove?
Read the schema definition of the olcHdbConfig objectclass, and compare it to the definition of the olcMdbConfig objectclass. Delete anything that isn't present in the olcMdbConfig objectclass.
The schema has everything you need to know. Use it.
On 14/3/2014 3:08 μμ, Howard Chu wrote:
Read the schema definition of the olcHdbConfig objectclass, and compare it to the definition of the olcMdbConfig objectclass. Delete anything that isn't present in the olcMdbConfig objectclass.
The schema has everything you need to know. Use it.
Thank you for this info.
I have been able to find the definitions of these classes (as well as that of olcDatabaseConfig which is relevant) from our running Openldap, so I'll manage the migration.
By the way, is the (latest, at least) full config schema available online somewhere on the openldap documentation pages? (I have not been able to locate it.) It would be handy to have it easily accessible for reference.
(Googling around only located a zytrax.com page; however the schema published there is inaccurate - perhaps based on older openldap versions.)
Thanks and best regards, Nick
Hi,
On Fri, 14 Mar 2014, Nick Milas wrote:
Hi,
We have a running openldap installation (2.4.39) - a single master - with cn=config and hdb backend.
So, config has the branches:
I know we must slapcat our data and slapadd it in mdb afterwards.
The question is: what changes should be done in the config DIT (and how) so that the config changes from hdb backend to mdb backend?
Is it enough to slapcat config, then change:
olcDatabase from {1}hdb to {1}mdb
and:
objectClass from olcHdbConfig to olcMdbConfig
...?
Anything else?
Can we safely delete all values of the olcDbConfig attribute which originate from converting from "DB_CONFIG"?
you can safely remove olcDbConfig. There is no berkeley db environment to configure.
I would say the bare mimimum would be something on the order of:
dn: olcDatabase={1}mdb,cn=config objectClass: olcDatabaseConfig objectClass: olcMdbConfig olcDatabase: {1}mdb olcDbDirectory <directory> olcDbCheckpoint: <kbyte> <min> olcDbMaxSize: <bytes> olcDbIndex: ...
What attributes can we safely remove?
anything mdb specific.
Greetings Christian
openldap-technical@openldap.org
-
Christian Kratzer -
Howard Chu -
Nick Milas