OK, I found a stragegy that worked. I took vmware and prepared a virtual machine. I did the RPM install of the same directory server 1.0.4. that was installed on the old server. Luckily I had retrospect on the machine. I used restrospect to do a full disk restore of the old system onto the new one. I stopped networking on the server first for fear that the system would start up and try to join the live systme and corrupt data. The server did startup but the data was not as it was that day. This was probably due to the fact that retrospect backed up open files of the FDS. That is ok though. I also had been running db2bak every night. I used back2db.pl to restore one of the backups over the current. Then I ran db2ldif and moved the ldif files out. Then I did an rpm -e fedora.1.0.4. Then I reinstalled FDS again and used the ldif to restore the data. The long way around. Having VMWare was nice because I was able to shut down networking but still access the VMWARE console from the network. :) Edward On 4/9/07, Eddie C <edlinuxguru at gmail.com> wrote: > > Unfortunately I only have the db2bak from the day I need to restore. No > ldif files. And I need to restore them to a new server. I do not need all > the configuration data. I only need two of our data trees. > > > > > > On 4/9/07, Oscar A. Valdez <oscar.valdez at duraflex.com.sv > wrote: > > > > El lun, 09-04-2007 a las 14:22 -0400, Eddie C escribi?: > > > Every night I run a db2bak. > > > Can this backup be safely restored to a different server? using > > > bak2db? > > > > It won't. > > > > I had to do a restore by necessity, and here's what I had to do (by > > Noriko Hosoi's gracious recommendation): > > > > 1. on the current directory server, export the data into ldif files. > > go to your <server_root>/slapd-<id>; run "db2ldif -n <backend>" for each > > backend (e.g., userRoot) EXCEPT NetscapeRoot > > 2. install new FDS > > 3. go to the <new_server_root>/slapd-<id> > > 4. stop the directory server > > 5. import the ldif files from the current directory server > > repeat "ldif2db -n <backend> -i > > <server_root>/slapd-<id>/<date_time>.ldif" for each <date_time>.ldif file > > exported in (1). > > 6. start the directory server > > > > The issue is documented in this thread: > > https://www.redhat.com/archives/fedora-directory-users/2007-February/msg00024.html > > > > > > The NetscapeRoot instance is server-specific, and it won't restore > > properly on a new server. > > -- > > Oscar A. Valdez > > > > > > -- > > Fedora-directory-users mailing list > > Fedora-directory-users at redhat.com > > https://www.redhat.com/mailman/listinfo/fedora-directory-users > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.fedoraproject.org/pipermail/389-users/attachments/20070409/d20fd772/attachment.html
