389 Directory Server
“389 Directory Server” is the new name of “Fedora Directory Server”; “Red Hat Directory Server” is the certified version by Red Hat, they all share the same codebase. Backup 389 Directory Server's data it's pretty simple.
1) On the server that run 389 Directory Server install bacula-fd and then create the file /etc/bacula/scripts/make_389_backup :
#!/bin/sh # execute a dump of 389 /usr/lib/dirsrv/slapd-soasi/db2bak /var/lib/dirsrv/slapd-soasi/bak/dump
# chmod 755 /etc/bacula/scripts/make_389_backup
You have to replace “slapd-soasi” with “slapd-xxx” where “xxx” it's your slapd istance name. This script will create the dump directory and then create some dump files (that contains the directory's data) on the directory /var/lib/dirsrv/slapd-soasi/bak/dump .
2) On the server that run 389 Directory Server create the cleanup script /etc/bacula/scripts/delete_389_backup :
#!/bin/sh # remove dump rm -rf /var/lib/dirsrv/slapd-soasi/bak/dump
# chmod 755 /etc/bacula/scripts/delete_389_backup
You have to replace “slapd-soasi” with “slapd-xxx” where “xxx” it's your slapd istance name.
3) On the Bacula Director server create the job entry that must contain something like that:
Job {
Name = "389"
Client = 389-fd
Write Bootstrap = "/var/lib/bacula/389.bsr"
**FileSet = "389"**
JobDefs = "default"
# create 389's dump
**Client Run Before Job = "/etc/bacula/scripts/make_389_backup"**
# delete the dump
**Client Run After Job = "/etc/bacula/scripts/delete_389_backup"**
}
The FileSet named “389” must contain:
File = /var/lib/dirsrv/slapd-soasi/bak/dump
You have to replace “slapd-soasi” with “slapd-xxx” where “xxx” it's your slapd istance name.
References:
