PingDirectory

LDIF export as a recurring task

You can create a recurring task to schedule the export of LDIF data.

With the default configuration, the server exports LDIF data every day at 1:05 AM in the default time zone for the Java Virtual Machine (JVM), which is usually the time zone configured for the underlying operating system. At the scheduled time, the server exports the contents of each public backend to a file in the <server-root>/ldif directory.

Public backends are non-administrative backends containing user-supplied data.

The server compresses and encrypts the LDIF exports if the global configuration is set to encrypt LDIF exports by default, which is enabled if encryption is configured during setup. The LDIF exports are rate limited to ten megabytes per second to minimize the impact on server performance, and exports are retained for seven days.

When you update a server instance to this release, if the recurring task chain that exports LDIF data isn’t present, the update tool creates the task chain. However, the recurring task chain created by the update tool isn’t enabled by default. You need to enable it using either dsconfig or the admin console.

Learn more in Scheduling LDIF export as a recurring task.

LDIF export can export multiple backends in the same recurring task. You can use the backend-id property to include multiple backends. You can use the exclude-backend-id property to exclude one or more backends. These optional properties are mutually exclusive:

  • If the backend-id property has one or more values, only the backends with those IDs are exported.

  • If the exclude-backend-id property has one or more values, all public backends except those listed are exported.

  • If neither the backend-id property nor the exclude-backend-id property supply values, all public backends are exported.