RE: Data migration from one openLDAP server to another.

["Pandey, Vishal" <vpandey@verisign.com>]

Hey...
I asked about migration of ldap data before. I am going from a rh9 openldap
2.1.x server to fedora openldap 2.1.x server. The domain is different,
users/groups/aliases etc are same. I've got everything setup but for some
reason slapadd is not working as I had hoped it would.

What I did first was - on the original server (after shutting down slapd)
 
>> slapcat -v -l ldap_data.ldif
this seemed to work perfectly...and i had an ldif file with all information
which seemed pretty accurate. Now I changed it to suit my needs (chaged
domain/base/hosts etc and all)...so I dont think the problem lies there.
(correct me if i'm missing something though)

Now I got the file over to the new server. Here I did 

>> slapadd -v -l ldap_data.ldif
This gives out this :
>> added: "cn=mailer-daemon,ou=Aliases,dc=xxx,dc=xxxxx,dc=com" (00000012)
and then it stops. Now the entry above is the first entry in the
ldap_data.ldif file. I was hoping it wud add everything. My ldif file looks
something like this (first 3 entries - masked certain values here)

dn: cn=mailer-daemon,ou=Aliases,dc=xxx,dc=xxxx,dc=com
cn: mailer-daemon
objectClass: nisMailAlias
objectClass: top
rfc822MailMember: postmaster
structuralObjectClass: nisMailAlias
entryUUID: d1f27ad2-f6a2-1027-9129-e2768cb17aa5
creatorsName: cn=root,dc=xxx,dc=xxxx,dc=com
createTimestamp: 20040218211153Z
entryCSN: 2004021821:11:53Z#0x000e#0#0000
modifiersName: cn=root,dc=xxx,dc=xxxx,dc=com
modifyTimestamp: 20040218211153Z

dn: cn=postmaster,ou=Aliases,dc=xxx,dc=xxxx,dc=com
cn: postmaster
objectClass: nisMailAlias
objectClass: top
rfc822MailMember: root
structuralObjectClass: nisMailAlias
entryUUID: d1f7206e-f6a2-1027-912a-e2768cb17aa5
creatorsName: cn=root,dc=xxx,dc=xxxx,dc=com
createTimestamp: 20040218211153Z
entryCSN: 2004021821:11:53Z#0x000f#0#0000
modifiersName: cn=root,dc=xxx,dc=xxxx,dc=com
modifyTimestamp: 20040218211153Z

dn: cn=bin,ou=Aliases,dc=xxx,dc=xxxx,dc=com
cn: bin
objectClass: nisMailAlias
objectClass: top
rfc822MailMember: root
structuralObjectClass: nisMailAlias
entryUUID: d1fb7bc8-f6a2-1027-912b-e2768cb17aa5
creatorsName: cn=root,dc=xxx,dc=xxxx,dc=com
createTimestamp: 20040218211153Z
entryCSN: 2004021821:11:53Z#0x0010#0#0000
modifiersName: cn=root,dc=xxx,dc=xxxx,dc=com
modifyTimestamp: 20040218211153Z

All the data follows this same structure in their own proper way, i checked.
But as u can see it stops after adding the first entry.
Any tips anyone??..

Thanks
Vishal


-----Original Message-----
From: Tony Earnshaw [mailto:tonye@billy.demon.nl]
Sent: Monday, April 05, 2004 3:34 PM
To: Openldap list
Subject: Re: Data migration from one openLDAP server to another.


man, 05.04.2004 kl. 16.51 skrev Pandey, Vishal:

> Merry Monday folks,

:(

> Has anoyone ever migrated data from openLDAP server to another machine? 
> We are just building new boxes at work and so the old openLDAP redHAT 9
> server is being replaced by a new Fedora box. Just a short summary on what
> all to move over and any handy tips would be appreciated if anyone has
been
> through the process. 

What versions? Migrating a standard RH9 2.0 slapcat to Openldap 2.1.x
last summer was not pleasant; spaces that shouldn't have been there had
to be removed, intuition played a large role and ruthlessly deleting and
rewriting intransigent records was de rigeur. An extended knowledge of
vi's macro possibilities and/or sed is a great help. Mutating +- 300
Posix account/group/Samba 2 records by hand was half a day's work.

I've noticed that upgrades from Openldap 2.1 to 2.2 go much more easily.

--Tonni

-- 

mail: billy - at - billy.demon.nl
http://www.billy.demon.nl