From 258c36569a0edd87067c00d8d475a13b451e4569 Mon Sep 17 00:00:00 2001
From: Axon <axon@openmailbox.org>
Date: Wed, 14 Jan 2015 10:41:06 +0000
Subject: [PATCH] SoftwareUpdateVM changed

Added remarks regarding default template
---
 SoftwareUpdateVM.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/SoftwareUpdateVM.md b/SoftwareUpdateVM.md
index d5de0e31..1bca5e65 100644
--- a/SoftwareUpdateVM.md
+++ b/SoftwareUpdateVM.md
@@ -80,7 +80,7 @@ qvm-create <vmname> --standalone --label <label>
 Using more than one template
 ----------------------------
 
-It's also possible to have more than one template VM in the system. E.g. one could clone the default template using the `qvm-clone` command in Dom0. This allows to have a customized template, e.g. with devel packages, or less trusted apps, shared by some subset of domains.
+It's also possible to have more than one template VM in the system. E.g. one could clone the default template using the `qvm-clone` command in Dom0. This allows to have a customized template, e.g. with devel packages, or less trusted apps, shared by some subset of domains. It is important to note that the default template is "system managed" and therefore cannot be backed up using Qubes' built-in backup function. In order to ensure the preservation of your custom settings and the availability of a "known-good" backup template, you may wish to clone the default system template and use your clone as the default template for your AppVMs.
 
 When you create a new domain you can choose which template this VM should be based on. If you use command line, you should use the `--template` switch: