Add Instruction for full restore

Dieser Commit ist enthalten in:
Noa J 2023-01-08 18:02:45 +01:00 committet von GitHub
Ursprung 9501c6b843
Commit 0ff4933801
Es konnte kein GPG-SchlĂĽssel zu dieser Signatur gefunden werden
GPG-SchlĂĽssel-ID: 4AEE18F83AFDEB23

Datei anzeigen

@ -166,6 +166,36 @@ docker compose restart borgmatic-mailcow
Restoring a backup assumes you are starting off with a fresh installation of mailcow, and you currently do not have
any custom data in your maildir or your mailcow database.
### Restore All
!!! warning
Running this command will overwrite all volumes and recreate the whole mailcow system! Do not run this unless you actually
intend to recover the mailcow system from a backup.
If you need to restore the whole mailcow system you need to start only three containers of the mailcow stack. Before running a restore you must make all volumes writeable in `docker-compose.override.yml` by removing the `ro` flag from the volume:
```
docker compose up -d mysql-mailcow borgmatic-mailcow
```
Execute following two commands, to restore the whole Mailcow Installation:
```
docker compose exec borgmatic-mailcow borgmatic extract --path mnt/source --archive latest
```
```
docker compose exec borgmatic-mailcow borgmatic restore --archive latest
```
Alternatively you can specify any archive name from the list of archives (see
[Listing all available archives](#listing-all-available-archives))
After the commands are executed successfully, you must stop the containers and restart the whole mailcow stack. The mailcow system should now be restored.
```
docker compose down && docker compose up -d
```
### Restore maildir
!!! warning
@ -259,4 +289,4 @@ To fetch the keyfile run:
docker compose exec borgmatic-mailcow borg key export --paper user@rsync.net:mailcow
```
Where `user@rsync.net:mailcow` is the URI to your repository.
Where `user@rsync.net:mailcow` is the URI to your repository.