From 30b5aed1003fd38d4a9bc12ea13236aad4ff5adb Mon Sep 17 00:00:00 2001 From: Joao Fernandes Date: Tue, 20 Mar 2018 15:38:37 -0700 Subject: [PATCH] Add note about restoring with NFS (#553) --- ee/dtr/admin/disaster-recovery/restore-from-backup.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/ee/dtr/admin/disaster-recovery/restore-from-backup.md b/ee/dtr/admin/disaster-recovery/restore-from-backup.md index fe337f414a..678047d173 100644 --- a/ee/dtr/admin/disaster-recovery/restore-from-backup.md +++ b/ee/dtr/admin/disaster-recovery/restore-from-backup.md @@ -84,6 +84,10 @@ Where: * `` the id of the replica you backed up * ``the url that clients use to access DTR +If you're using NFS as a storage backend, also include `--nfs-storage-url` as +part of your restore command, otherwise DTR is restored but starts using a +local volume to persist your Docker images. + ### Re-fetch the vulnerability database If you're scanning images, you now need to download the vulnerability database. @@ -91,4 +95,4 @@ If you're scanning images, you now need to download the vulnerability database. After you successfully restore DTR, you can join new replicas the same way you would after a fresh installation. [Learn more](../configure/set-up-vulnerability-scans.md). -{% endif %} \ No newline at end of file +{% endif %}