Hi all,
Is it safe to keep the same database files from one OpenLDAP server to another one, since the first one is 2.2.13 on ZLinux and the second one is 2.2.26 on an i386 architecture ?
Of course, the configuration files and file paths are the same
Thank you for your answer
François
Although there are some situations where copying the database will work, this is not always the case. For instance, a migration of a bdb/hdb from 32- to 64-bit architecture will not work. Therefore, most people recommend you treat the platform change as any other upgrade:
http://www.openldap.org/faq/data/cache/842.html
On Fri, 3 Nov 2006, Fran�ois Beretti wrote:
Hi all,
Is it safe to keep the same database files from one OpenLDAP server to another one, since the first one is 2.2.13 on ZLinux and the second one is 2.2.26 on an i386 architecture ?
Of course, the configuration files and file paths are the same
Thank you for your answer
Fran�ois
Hi Anton, thank you for your answer.
Do the slapadd tool keep the operational attributes values ?
If we try and copy the database, shall we see instantly if there is a problem, or can it occur at any time ?
Thank you,
François
2006/11/3, Aaron Richton richton@nbcs.rutgers.edu:
Although there are some situations where copying the database will work, this is not always the case. For instance, a migration of a bdb/hdb from 32- to 64-bit architecture will not work. Therefore, most people recommend you treat the platform change as any other upgrade:
http://www.openldap.org/faq/data/cache/842.html
On Fri, 3 Nov 2006, François Beretti wrote:
Hi all,
Is it safe to keep the same database files from one OpenLDAP server to another one, since the first one is 2.2.13 on ZLinux and the second one
is
2.2.26 on an i386 architecture ?
Of course, the configuration files and file paths are the same
Thank you for your answer
François
Do the slapadd tool keep the operational attributes values ?
It does not. See the slapadd man page.
If we try and copy the database, shall we see instantly if there is a problem, or can it occur at any time ?
slapadd has very little error checking versus adding through slapd. The restrictions are detailed in the slapadd man page. If you feed slapadd invalid data, but not so grossly invalid that slapadd errors out, it is quite possible that lingering effects (missing parents, schema violations, etc.) will "occur at any time" in the future. You basically want your data to be clean enough for ldapadd, whether you use slapadd or not.
By the way, if you're going to be migrating anyway, you really don't want to migrate from 2.2 to 2.2. Try the latest version of 2.3 available at www.openldap.org.
2006/11/6, Aaron Richton richton@nbcs.rutgers.edu:
Do the slapadd tool keep the operational attributes values ?
It does not. See the slapadd man page.
So the migration process bring you to a new directory, not a copy of the previous one. And if some LDAP application use the entryUUID attribute to refer to the users (in order to prevent problems when renaming a user), it does not work anymore after the migration. Am I right ? Is there still this problem in OpenLDAP 2.3 ?
If we try and copy the database, shall we see instantly if there is a
problem, or can it occur at any time ?
slapadd has very little error checking versus adding through slapd. The restrictions are detailed in the slapadd man page. If you feed slapadd invalid data, but not so grossly invalid that slapadd errors out, it is quite possible that lingering effects (missing parents, schema violations, etc.) will "occur at any time" in the future. You basically want your data to be clean enough for ldapadd, whether you use slapadd or not.
Ok, but I was speaking of the first way (copying the database files). Do the problems occurs immediately or not ?
By the way, if you're going to be migrating anyway, you really don't want to migrate from 2.2 to 2.2. Try the latest version of 2.3 available at www.openldap.org.
Of course, but in this project I am working with a customer who is changing its platform and I am not responsible of the migration process at all (actually I am supporting an application using the directory).
Aaron Richton wrote:
Do the slapadd tool keep the operational attributes values ?
It does not. See the slapadd man page.
Wrong. slapadd stores operational attribute values, also generating any that are missing.
If we try and copy the database, shall we see instantly if there is a problem, or can it occur at any time ?
slapadd has very little error checking versus adding through slapd. The restrictions are detailed in the slapadd man page. If you feed slapadd invalid data, but not so grossly invalid that slapadd errors out, it is quite possible that lingering effects (missing parents, schema violations, etc.) will "occur at any time" in the future. You basically want your data to be clean enough for ldapadd, whether you use slapadd or not.
By the way, if you're going to be migrating anyway, you really don't want to migrate from 2.2 to 2.2. Try the latest version of 2.3 available at www.openldap.org.
.
--On Monday, November 06, 2006 9:30 AM -0500 Aaron Richton richton@nbcs.rutgers.edu wrote:
Do the slapadd tool keep the operational attributes values ?
It does not. See the slapadd man page.
I think the man page needs some updating, it definitely keeps at least some of the operational attributes, provided they are in the LDIF file.
--Quanah
-- Quanah Gibson-Mount Principal Software Developer ITS/Shared Application Services Stanford University GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html
openldap-software@openldap.org
-
Aaron Richton -
François Beretti -
Howard Chu -
Quanah Gibson-Mount