The following pull request was submitted through Github.
It can be accessed and reviewed at: https://github.com/lxc/lxd/pull/4457

This e-mail was sent by the LXC bot, direct replies will not reach the author
unless they happen to be subscribed to this list.

=== Description (from pull-request) ===
Signed-off-by: St├ęphane Graber <stgra...@ubuntu.com>
From 79624f97b77d72a9a7debd38effa87aeaee3874e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?St=C3=A9phane=20Graber?= <stgra...@ubuntu.com>
Date: Mon, 16 Apr 2018 17:57:51 +0200
Subject: [PATCH] doc: Tweak backup.md
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Signed-off-by: St├ęphane Graber <stgra...@ubuntu.com>
---
 doc/backup.md | 18 ++++++++++++++----
 1 file changed, 14 insertions(+), 4 deletions(-)

diff --git a/doc/backup.md b/doc/backup.md
index 0f7b7d76d..91b122ee8 100644
--- a/doc/backup.md
+++ b/doc/backup.md
@@ -3,12 +3,13 @@
 To backup a LXD instance different strategies are available.
 
 ## Full backup
-This requires that the whole `/var/lib/lxd` folder will be backuped up.
+This requires that the whole `/var/lib/lxd` or
+`/var/lib/snap/lxd/common/lxd` (for the snap) folder be backuped up.
 Additionally, it is necessary to backup all storage pools as well.
 
-In order to restore the LXD instance the old `/var/lib/lxd` folder needs to be
-removed and replaced with the `/var/lib/lxd` snapshot. All storage pools
-need to be restored as well.
+In order to restore the LXD instance the old `lxd` folder needs to be
+removed and replaced with the `lxd` snapshot. All storage pools need to
+be restored as well.
 
 ## Secondary LXD
 This requires a second LXD instance to be setup and reachable from the LXD
@@ -37,6 +38,15 @@ accessible before the container can be imported.  For 
example, if the
 container's storage volume got unmounted the user is required to remount it
 manually.
 
+The container must be available under
+`/var/lib/lxd/storage-pools/POOL-NAME/containers/NAME` or
+`/var/lib/snap/lxd/common/lxd/storage-pools/POOL-NAME/containers/NAME`
+in the case of the LXD snap.
+
+LXD will then locate the container and read its `backup.yaml` file,
+creating any missing database entry.
+
+
 If any matching database entry for resources declared in `backup.yaml` is found
 during import, the command will refuse to restore the container.  This can be
 overridden running 
_______________________________________________
lxc-devel mailing list
lxc-devel@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-devel

Reply via email to