From 0e4e4522e699f47b292eeaddde62355e9e7c6126 Mon Sep 17 00:00:00 2001 From: Peter Date: Sat, 4 Jan 2020 14:34:37 +0100 Subject: [PATCH] Update i_u_m_migration.md --- docs/i_u_m_migration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/i_u_m_migration.md b/docs/i_u_m_migration.md index c259ac777..25fd3ff4d 100644 --- a/docs/i_u_m_migration.md +++ b/docs/i_u_m_migration.md @@ -1,5 +1,5 @@ !!! warning - Please note: This guide assumes you intend to migrate an existing mailcow server (source) over to a brand new, empty server (target). It takes no care about preserving any existing data on your target server and will erase anything within `/var/lib/docker/volumes` and thus any Docker volumes you may have already set up. + This guide assumes you intend to migrate an existing mailcow server (source) over to a brand new, empty server (target). It takes no care about preserving any existing data on your target server and will erase anything within `/var/lib/docker/volumes` and thus any Docker volumes you may have already set up. !!! tip Alternatively, you can use the `./helper-scripts/backup_and_restore.sh` script to create a full backup on the source machine, then install mailcow on the target machine as usual, copy over your `mailcow.conf` and use the same script to restore your backup to the target machine.