Restoring a policy database from a backup - PingAuthorize

Restoring a policy database from a backup - PingAuthorize - 9.1

PingAuthorize

bundle

pingauthorize-91

ft:publication_title

PingAuthorize

Product_Version_ce

PingAuthorize 9.1

To restore a policy database when not in a Docker environment:

Ensure the Policy Editor server is no longer running by either using bin/stop-server or killing the process.
Locate the backup .zip file that you want to restore.

The default location is SERVER_ROOT/policy-backup. However, the location might have been changed using the PING_H2_BACKUP_DIR environment variable.
Extract the .zip file to the configured database location overwriting the previous policy database file, if present.

The default location is the root of the Policy Editor server installation directory. If it's not there, check the location specified by the PING_H2_FILE environment variable.
Start the Policy Editor server.
```
$ bin/start-server
```

To restore a policy database in a Docker environment:

Locate the backup .zip file that you want to restore.

The location should be a directory specified using the PING_H2_BACKUP_DIR environment variable, as mentioned in Policy database backups.
Extract the .zip file to the database location that you will specify using the PING_H2_FILE environment variable when you start the Docker container.
Start the Docker container with a mounted volume that has the extracted backup file and use PING_H2_FILE to specify that backup file in the container file system.
For example, the following command assumes the uncompressed database file is named Symphonic.mv.db in the host file system. The PING_H2_FILE environment variable specifies the file name without the .mv.db extension.
```
$ docker run --network=<network_name> --env-file ~/.pingidentity/config \
  --env PING_H2_FILE=/opt/out/Symphonic \
  --volume <HOST_BACKUP_DIR>:/opt/out pingidentity/pingauthorizepap:<TAG>
```
Tip:
For proper communication between containers, create a Docker network using a command such as docker network create --driver <network_type> <network_name>, and then connect to that network with the --network=<network_name> option.

Note:
The Docker image <TAG> used in the example is only a placeholder.For actual tag values, see Docker Hub.