Policy database backups
The Policy Editor uses a policy database to store its Trust Framework, policies, commit history, and other data needed for proper operation.
By default, the Policy Editor backs up the policy database to a compressed file once a day by making an HTTP request to an admin connector. The Policy Editor retains up to five policy database backups at a time. Older backups are automatically deleted after this limit is reached.
To customize the handling of policy database backups, configure the admin port, backup schedule, and output location.
|
If you are using a managed RDBMS, such as PostgreSQL, instead of the default H2 database, make sure you implement backup strategies in line with your organization’s best practices. |
Configure or disable policy database backups
Do one of the following to change the backup configuration:
-
Set the relevant environment variables and restart the Policy Editor.
-
Run the Policy Editor
setuptool with the relevant command-line options.
The following table describes the relevant environment variables and command-line options. Learn more about using the environment variables in Starting PingAuthorize Policy Editor.
| Environment variable | Command-line option | Description | ||
|---|---|---|---|---|
|
|
Specifies the admin port, where administrative task endpoints like periodic policy database backups are handled. |
||
|
|
Specifies a The default is Learn more in Quartz 2.3.0 cron format.
|
||
|
N/A |
Specifies the directory in which to place the policy H2 database backup files. The default is
|
||
N/A |
|
Turns off periodic policy database backups. |
Learn more about using a backup in Restoring a policy database from a backup.