Hmm... If you mean your production server can't be restored from any of your backups, it might be worth it to give RedHat a call and book some professional services to assist in the recovery. Linux Admin wrote: > I can not really create a new dir on the original. I am doing DR. > So if that does not work, what are my options in building the DR? > > > On 10/24/07, *George Holbert * <gholbert at broadcom.com > <mailto:gholbert at broadcom.com>> wrote: > > db2bak (binary backup) is pretty specific to the machine on which > it was > created. > At least a few dependencies: > - architecture of the machine (e.g., sparc to intel, or 32 to 64 bit). > - hostname is sprinkled throughout o=NetscapeRoot. > - index and other configuration in the server's cn=config. > > Unless you're restoring on an identical machine with identical > directory > server configuration, I would expect quirks when attempting what > you've > described. > On the bright side, since it does work on the new server, it > sounds like > you've isolated the problem to something with the original server. > What happens when you create a fresh new directory server instance on > the original, and try to backup and restore that instance? > > > Linux Admin wrote: > > It get really bad: > > on new clean server: > > Backup from CLI: db2bak > > Restore CLI: works OK > > then I bring the dir produce by db2bak from the server I am > trying to > > restore to new box and teh same restore commad fails > > > > > > On 10/24/07, *Linux Admin* <sysadmin.linux at gmail.com > <mailto:sysadmin.linux at gmail.com> > > <mailto:sysadmin.linux at gmail.com > <mailto:sysadmin.linux at gmail.com>>> wrote: > > > > Using the refernace for redhat site even command line does work > > error 43: Failed to read backup file set > > > > > > > > On 10/24/07, * George Holbert* < gholbert at broadcom.com > <mailto:gholbert at broadcom.com> > > <mailto:gholbert at broadcom.com > <mailto:gholbert at broadcom.com>>> wrote: > > > > Backup/Restore: Creates / restores from a copy of the > > server's binary > > database files. > > Export/Import: Creates / imports from ASCII text LDIF files > > representing the data in the directory server. > > > > It's actually a good idea to do both (if possible), as this > > will give > > you the most flexibility when you're in the heat of a > restore. > > > > > http://www.redhat.com/docs/manuals/dir-server/ag/7.1/dbmanage.html#1055147 > <http://www.redhat.com/docs/manuals/dir-server/ag/7.1/dbmanage.html#1055147> > > > <http://www.redhat.com/docs/manuals/dir-server/ag/7.1/dbmanage.html#1055147> > > > > > I get error 53 (failed to read the backup file set) > > > > Is the backup file set still there? > > > > > > Linux Admin wrote: > > > If I want to do through GUI: which option do I use: > > Backup/Restore or > > > Import/Export > > > When I sued Backup....I tried to restore into vanilla LDAP > > specifying > > > the top level directory which contains NetascapeRoot > and userRoot > > > subdirs, I get error 53 (failed to read the backup > file set) > > > > > > > > > On 10/18/07, *Linux Admin* < sysadmin.linux at gmail.com > <mailto:sysadmin.linux at gmail.com> > > <mailto:sysadmin.linux at gmail.com > <mailto:sysadmin.linux at gmail.com>> > > > <mailto:sysadmin.linux at gmail.com > <mailto:sysadmin.linux at gmail.com> > > <mailto: sysadmin.linux at gmail.com > <mailto:sysadmin.linux at gmail.com>>>> wrote: > > > > > > Please forgive the newbee question here. > > > What is the best way to backup/dump--restore/import a > > fedora ldap > > > server > > > (without downtime) > > > TIA > > > > > > > > > > ------------------------------------------------------------------------ > >
