From ef8f6af3bb7c4deed5fa0ce1241dd08c343f476d Mon Sep 17 00:00:00 2001 From: Maria Bermudez Date: Wed, 6 Mar 2019 14:53:00 -0800 Subject: [PATCH] Update restore-from-backup.md --- ee/dtr/admin/disaster-recovery/restore-from-backup.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/ee/dtr/admin/disaster-recovery/restore-from-backup.md b/ee/dtr/admin/disaster-recovery/restore-from-backup.md index 2c0b17d80c..0588502cca 100644 --- a/ee/dtr/admin/disaster-recovery/restore-from-backup.md +++ b/ee/dtr/admin/disaster-recovery/restore-from-backup.md @@ -79,10 +79,8 @@ Where: * `` is the hostname of the node where you've restored the images * `` 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. +Starting in DTR 2.6, switching storage backends will erase your existing tags. Make sure to perform a backup +before you do so. To restore your metadata, you need to manually create a volume and pass the `--dtr-storage-volume` flag instead. See [kbase article](fixmelink) for more details. ### Re-fetch the vulnerability database