diff --git a/docs/server/source/appendices/index.rst b/docs/server/source/appendices/index.rst
index 7beb27f5..a901b58a 100755
--- a/docs/server/source/appendices/index.rst
+++ b/docs/server/source/appendices/index.rst
@@ -22,5 +22,6 @@ Appendices
    firewall-notes
    ntp-notes
    example-rethinkdb-storage-setups
+   rethinkdb-backup
    licenses
    install-with-lxd
diff --git a/docs/server/source/clusters-feds/backup.md b/docs/server/source/appendices/rethinkdb-backup.md
similarity index 96%
rename from docs/server/source/clusters-feds/backup.md
rename to docs/server/source/appendices/rethinkdb-backup.md
index 5faf3465..732323ed 100644
--- a/docs/server/source/clusters-feds/backup.md
+++ b/docs/server/source/appendices/rethinkdb-backup.md
@@ -1,6 +1,6 @@
-# Backing Up & Restoring Data
+# Backing Up and Restoring Data
 
-There are several ways to backup and restore the data in a BigchainDB cluster.
+This page was written when BigchainDB only worked with RethinkDB, so its focus is on RethinkDB-based backup. BigchainDB now supports MongoDB as a backend database and we recommend that you use MongoDB in production. Nevertheless, some of the following backup ideas are still relevant regardless of the backend database being used, so we moved this page to the Appendices.
 
 
 ## RethinkDB's Replication as a form of Backup
diff --git a/docs/server/source/clusters-feds/index.rst b/docs/server/source/clusters-feds/index.rst
index 93258057..40e3b873 100644
--- a/docs/server/source/clusters-feds/index.rst
+++ b/docs/server/source/clusters-feds/index.rst
@@ -5,6 +5,5 @@ Clusters
    :maxdepth: 1
 
    set-up-a-cluster
-   backup
    aws-testing-cluster