Restore Docker container¶
You can restore PMM Server either from a manual backup or from an automated backup volume that was created during migration to PMM v3.
Before proceeding with restoration, ensure you have either a manual backup or an automated backup volume to restore from.
To restore the container from a manual backup:
-
Stop the container:
docker stop pmm-server
-
Remove the container:
docker rm pmm-server
-
Revert to the saved image:
docker rename pmm-server-backup pmm-server
-
Change directory to the backup directory (e.g.
pmm-data-backup
):cd pmm-data-backup
-
Copy the data:
docker run --rm -v $(pwd)/srv:/backup -v pmm-data:/srv -t percona/pmm-server:3 cp -r /backup/* /srv
-
Restore permissions:
docker run --rm -v pmm-data:/srv -t percona/pmm-server:3 chown -R pmm:pmm /srv
-
Start the image:
docker start pmm-server
To restore from an automated backup volume created during migration to PMM v3:
- Stop the current PMM v3 container:
docker stop pmm-server
- Remove the container (optional):
docker rm pmm-server
-
Start a PMM v2 container using your backup volume, replacing
<backup-volume-name>
with your PMM v2 backup volume name (e.g.,pmm-data-2025-01-16-165135
):docker run -d \ -p 443:443 \ --volume <backup-volume-name>:/srv \ --name pmm-server \ --restart always \ percona/pmm-server:2.44.0
-
Verify that your PMM v2 instance is running correctly and all your data is accessible.
Finding your backup volume name
- Your backup volume name was displayed during the automated upgrade process.
-
To list all available Docker volumes, use the following command, and look for volumes with names like
pmm-data-YYYY-MM-DD-HHMMSS
:docker volume ls