Name
backup — back up OpenDJ directory data
Synopsis
backup {options}
Options
The following options are supported.
-a, --backUpAll-
Back up all backends in the server
-A, --hash-
Generate a hash of the backup contents
-B, --incrementalBaseID {backupID}-
Backup ID of the source archive for an incremental backup.
-c, --compress-
Compress the backup content
-d, --backupDirectory {backupDir}-
Path to the target directory for the backup file(s)
-i, --incremental-
Perform an incremental backup rather than a full backup
-I, --backupID {backupID}-
Use the provided identifier for the backup
-n, --backendID {backendName}-
Backend ID for the backend to archive
-s, --signHash-
Sign the hash of the backup contents
-y, --encrypt-
Encrypt the backup contents
Task Backend Connection Options
--connectTimeout {timeout}-
Maximum length of time (in milliseconds) that can be taken to establish a connection. Use '0' to specify no time out.
Default value: 30000
-D, --bindDN {bindDN}-
DN to use to bind to the server
Default value: cn=Directory Manager
-h, --hostname {host}-
Directory server hostname or IP address
Default value: localhost.localdomain
-j, --bindPasswordFile {bindPasswordFile}-
Bind password file
-K, --keyStorePath {keyStorePath}-
Certificate key store path
-N, --certNickname {nickname}-
Nickname of certificate for SSL client authentication
-o, --saslOption {name=value}-
SASL bind options
-p, --port {port}-
Directory server administration port number
Default value: 4444
-P, --trustStorePath {trustStorePath}-
Certificate trust store path
-T, --trustStorePassword {trustStorePassword}-
Certificate trust store PIN
-u, --keyStorePasswordFile {keyStorePasswordFile}-
Certificate key store PIN file
-U, --trustStorePasswordFile {path}-
Certificate trust store PIN file
-w, --bindPassword {bindPassword}-
Password to use to bind to the server
Use
-w -to have the command prompt for the password, rather than enter the password on the command line. -W, --keyStorePassword {keyStorePassword}-
Certificate key store PIN
-X, --trustAll-
Trust all server SSL certificates
Task Scheduling Options
--completionNotify {emailAddress}-
Email address of a recipient to be notified when the task completes. This option may be specified more than once.
--dependency {taskID}-
ID of a task upon which this task depends. A task will not start execution until all its dependencies have completed execution.
--errorNotify {emailAddress}-
Email address of a recipient to be notified if an error occurs when this task executes. This option may be specified more than once.
--failedDependencyAction {action}-
Action this task will take should one if its dependent tasks fail. The value must be one of PROCESS, CANCEL, DISABLE. If not specified defaults to CANCEL.
--recurringTask {schedulePattern}-
Indicates the task is recurring and will be scheduled according to the value argument expressed in crontab(5) compatible time/date pattern.
-t, --start {startTime}-
Indicates the date/time at which this operation will start when scheduled as a server task expressed in YYYYMMDDhhmmssZ format for UTC time or YYYYMMDDhhmmss for local time. A value of '0' will cause the task to be scheduled for immediate execution. When this option is specified the operation will be scheduled to start at the specified time after which this utility will exit immediately.
Exit Codes
- 0
-
The command completed successfully.
- 1
-
An error occurred while parsing the command-line arguments.
Examples
The following example backs up all user data while the server is online.
$ backup -p 4444 -D "cn=Directory Manager" -w password -a -d /path/to/opendj/bak -t 0 Backup task 20110613143801866 scheduled to start Jun 13, 2011 2:38:01 PM CEST
The following example schedules back up of all user data every night at 2 AM when the server is online, and notifies diradmin@example.com when finished, or on error.
$ backup -p 4444 -D "cn=Directory Manager" -w password -a -d /path/to/opendj/bak --recurringTask "00 02 * * *" --completionNotify diradmin@example.com --errorNotify diradmin@example.com Recurring Backup task BackupTask-988d6adf-4d65-44bf-8546-6ea74a2480b0 scheduled successfully
The following example backs up all user data while the server is offline.
$ /path/to/opendj/bin/stop-ds Stopping Server... ... $ /path/to/opendj/bin/backup --backupAll --backupDirectory /path/to/opendj/bak ... [28/Sep/2012:12:14:22 +0200] ... msg=The backup process completed successfully $ /path/to/opendj/bin/start-ds [28/Sep/2012:12:15:48 +0200] ... The Directory Server has started successfully

