Provided by: 389-ds-base_1.3.4.9-1_amd64 bug

NAME - Directory Server perl script for creating a backup

SYNOPSIS  [-Z serverID] [-D rootdn] { -w password | -w - | -j filename }  [-t dbtype] [-a
       backupdir] [-A backupdir] [-P protocol] [-v] [-h]


       Creates a backup of the Directory Server database.  The Directory Server must  be  started
       prior to running this script.


       A summary of options is included below:

       -Z Server Identifier
              The  server  ID of the Directory Server instance.  If there is only one instance on
              the system, this option can be skipped.

       -D Root DN
              The Directory Manager DN, or root DN.  If not specified, the script will search the
              server instance configuration for the value.

       -w password
              The rootdn password.

       -w -
              Prompt for the rootdn password.

       -j password filename
              The name of the file that contains the root DN password.

       -t database type
              The backend database type (default: ldbm database).

       -a backupdir
              The directory where the backup should be stored.

       -A backupdir
              This is similar to -a, except that a sub-directory of backupdir will be created for
              the backup, and the name of the sub-directory will  be  a  timestamp  of  the  form

       -P Protocol
              The  connection  protocol  to  connect  to  the  Directory  Server.   Protocols are
              STARTTLS, LDAPS, LDAPI, and LDAP.  If this  option  is  skipped,  the  most  secure
              protocol  that is available is used.  For LDAPI, AUTOBIND is also available for the
              root user.

              Display verbose output

              Display usage

EXAMPLE -Z instance1 -D 'cn=directory manager' -w password -a /LDAP/backups/20130305  -P

              Note:  LDAPI  must  be  enabled to use this protocol.  If LDAPI is not available it
              will default to next strongest/available protocol automatically.


       Exit status is zero if no errors occur.  Errors result in a non-zero  exit  status  and  a
       diagnostic message being written to standard error.

AUTHOR was written by the 389 Project.


       Report bugs to


       Copyright © 2013 Red Hat, Inc.

                                           Mar 5, 2013                               DB2BAK.PL(8)