The Backup Backend provides read-only access to the set of backups that are available for OpenDJ.
It is provided as a convenience feature that makes it easier to determine what backups are available to be restored if necessary.
The Backup Backend component inherits from the Backend
A description of each property follows.
| Basic Properties: | Advanced Properties: |
|---|---|
| ↓ backend-id | ↓ java-class |
| ↓ backup-directory | ↓ writability-mode |
| ↓ base-dn | |
| ↓ enabled |
| Description | Specifies a name to identify the associated backend.The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server. |
| Default Value | None |
| Allowed Values | A String |
| Multi-valued | No |
| Required | Yes |
| Admin Action Required | None |
| Advanced Property | No |
| Read-only | Yes |
| Description | Specifies the path to a backup directory containing one or more backups for a particular backend.This is a multivalued property. Each value may specify a different backup directory if desired (one for each backend for which backups are taken). Values may be either absolute paths or paths that are relative to the base of the OpenDJ directory server installation. |
| Default Value | None |
| Allowed Values | A String |
| Multi-valued | Yes |
| Required | Yes |
| Admin Action Required | None |
| Advanced Property | No |
| Read-only | No |
| Description | Specifies the base DN(s) for the data that the backend handles.A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN. |
| Default Value | None |
| Allowed Values | A valid DN. |
| Multi-valued | Yes |
| Required | Yes |
| Admin Action Required | None. No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used. |
| Advanced Property | No |
| Read-only | No |
| Description | Indicates whether the backend is enabled in the server.If a backend is not enabled, then its contents are not accessible when processing operations. |
| Default Value | None |
| Allowed Values | true false |
| Multi-valued | No |
| Required | Yes |
| Admin Action Required | None |
| Advanced Property | No |
| Read-only | No |
| Description | Specifies the fully-qualified name of the Java class that provides the backend implementation. |
| Default Value | org.opends.server.backends.BackupBackend |
| Allowed Values | A java class that implements or extends the class(es) : org.opends.server.api.Backend |
| Multi-valued | No |
| Required | Yes |
| Admin Action Required | The Backup Backend must be disabled and re-enabled for changes to this setting to take effect |
| Advanced Property | Yes |
| Read-only | No |
| Description | Specifies the behavior that the backend should use when processing write operations. |
| Default Value | disabled |
| Allowed Values | disabled - Causes all write attempts to fail. enabled - Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability-mode property is also enabled). internal-only - Causes external write attempts to fail but allows writes by replication and internal operations. |
| Multi-valued | No |
| Required | Yes |
| Admin Action Required | None |
| Advanced Property | Yes |
| Read-only | No |