From a29520488cd36fb9c894d5f1d171feba4d3a3b51 Mon Sep 17 00:00:00 2001 From: "Joe Xie [atlassian]" Date: Thu, 26 May 2016 04:49:41 +0000 Subject: [PATCH] changed README to mention backup methods --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index d9b43d2..c78957d 100644 --- a/README.md +++ b/README.md @@ -45,7 +45,7 @@ container and its volumes using the `-v` option._ For evaluating Confluence you can use the built-in database that will store its files in the Confluence Server home directory. In that case it is sufficient to create a backup archive of the directory on the host that is used as a volume (`/data/your-confluence-home` in the example above). -Confluence's [automatic backup](https://confluence.atlassian.com/display/DOC/Configuring+Backups) is currently not supported in the Docker setup. You can however use the [Production Backup Strategy](https://confluence.atlassian.com/display/DOC/Production+Backup+Strategy) approach if you're using an external database. +Confluence's [automatic backup](https://confluence.atlassian.com/display/DOC/Configuring+Backups) is currently supported in the Docker setup. You can also use the [Production Backup Strategy](https://confluence.atlassian.com/display/DOC/Production+Backup+Strategy) approach if you're using an external database. Read more about data recovery and backups: [Site Backup and Restore](https://confluence.atlassian.com/display/DOC/Site+Backup+and+Restore)