2024-08-03 16:03:17 +02:00
---
title: Restore database from SSH
layout: default
parent: How Tos
2024-09-30 00:40:35 +02:00
nav_order: 7
2024-08-03 16:03:17 +02:00
---
# Restore database from SSH remote server
2024-08-10 10:50:00 +02:00
To restore the database from your remote server, you need to add `restore` command and specify the file to restore by adding `--file store_20231219_022941.sql.gz` .
2024-08-03 16:03:17 +02:00
{: .note }
2024-10-12 11:13:45 +02:00
It supports __ .sql__,__.sql.gpg__ and __ .sql.gz__,__.sql.gz.gpg__ compressed file.
2024-08-03 16:03:17 +02:00
### Restore
```yml
services:
mysql-bkup:
# In production, it is advised to lock your image tag to a proper
# release version instead of using `latest` .
# Check https://github.com/jkaninda/mysql-bkup/releases
# for a list of available releases.
image: jkaninda/mysql-bkup
container_name: mysql-bkup
2024-08-10 10:50:00 +02:00
command: restore --storage ssh -d my-database -f store_20231219_022941.sql.gz --path /home/jkaninda/backups
2024-08-03 16:03:17 +02:00
volumes:
- ./backup:/backup
environment:
- DB_PORT=3306
- DB_HOST=postgres
- DB_NAME=database
- DB_USERNAME=username
- DB_PASSWORD=password
## SSH config
- SSH_HOST_NAME="hostname"
- SSH_PORT=22
- SSH_USER=user
- SSH_REMOTE_PATH=/home/jkaninda/backups
- SSH_IDENTIFY_FILE=/tmp/id_ed25519
## We advise you to use a private jey instead of password
#- SSH_PASSWORD=password
# mysql-bkup container must be connected to the same network with your database
networks:
- web
networks:
web:
```