---
description: To restore a policy database in a Docker environment:
component: pingauthorize
version: 10.1
page_id: pingauthorize:pingauthorize_server_administration_guide:paz_restore_db_using_docker
canonical_url: https://docs.pingidentity.com/pingauthorize/10.1/pingauthorize_server_administration_guide/paz_restore_db_using_docker.html
section_ids:
  restoring-a-database-when-using-docker: Restoring a database when using Docker
  about-this-task: About this task
  steps: Steps
---

# Restoring a database when using Docker

## About this task

To restore a policy database in a Docker environment:

## Steps

1. Locate the backup `.zip` archive 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](paz_policy_db_backups.html).

2. Extract the `.zip` archive to the database location that you'll specify using the `PING_H2_FILE` environment variable when you start the Docker container.

3. Start the Policy Editor 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.

   ```shell
   $ docker run --network=<network_name>  --env-file ~/.pingidentity/config \
     --env PING_H2_FILE=/opt/out/Symphonic \
     --volume  <HOST_BACKUP_DIR>:/opt/out pingidentity/{PAP_CONTAINER_NAME}:<TAG>
   ```

   |   |                                                                                                                                                                                                                                           |
   | - | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
   |   | 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. |

   |   |                                                                                                                                                                   |
   | - | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
   |   | The Docker image *\<TAG>* used in the example is only a placeholder.For actual tag values, see [Docker Hub](https://hub.docker.com/r/pingidentity/pingauthorize). |