[Date Prev][Date Next]
Re: OpenLDAP-Database Backup Strategies/Software
I use slapcat to an ldif file. I also have replication to 3 other
servers. So I have 4 copies plus an ldif file that goes on tape by an
autoloader at night.
I have had to replace one slave LDAP server. I'm not using Sleepycat
backend. I'm using ldbm on all servers. To restore a broken server I
shutdown the master, sftp the db files to the directory on the new
machine, restart the master ensuring that the new server is listed in
the master's slapd.conf file and the slave lists the updateref as the
master.Then start the slave.
It's worked fine so far.
I'm just guessing on this but if you had OpenLDAP running on 2 or more
machines with different DB backends, you may have to restore a server
with ldapadd and an ldif file generated from slapcat. I don't believe
you could directly copy the DB files between different DB backends.
On Fri, 2004-03-26 at 10:27, Karsten Gorling wrote:
> Since several sysadmins are subscribed here, who uses OpenLDAP on
> regular basis, I wanted to know, if there is a known solid hot backup
> strategy for the OpenLDAP database. We will use sleepycat DB 4.2 as
> DB-Backend. As far, as I understand the sleepycat documentation, a
> simple tar of the database-files and logs is prune to error, quiet
> understandable since the database might change during the backup.
> Is a routinely slapcat to a backup-medium safe enough, or has something
> like that several pitfalls, I'm not aware yet?
> Any pointer for known functional backupsolutions of the database?
Kent L. Nasveschuk <email@example.com>