From 3278d253c5f688c9879acb903b2e6dd875f83027 Mon Sep 17 00:00:00 2001 From: Guinness Date: Fri, 13 Nov 2020 10:31:05 +0100 Subject: [PATCH] Update the documentation on hacked backup client. Fixes #5480. --- docs/deployment/pull-backup.rst | 1 + docs/faq.rst | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/deployment/pull-backup.rst b/docs/deployment/pull-backup.rst index e738b59bac..42157d3305 100644 --- a/docs/deployment/pull-backup.rst +++ b/docs/deployment/pull-backup.rst @@ -1,5 +1,6 @@ .. include:: ../global.rst.inc .. highlight:: none +.. _pull_backup: ======================= Backing up in pull mode diff --git a/docs/faq.rst b/docs/faq.rst index cdb505c868..79e9adda02 100644 --- a/docs/faq.rst +++ b/docs/faq.rst @@ -616,7 +616,7 @@ C to delete all backups residing on S. These are your options to protect against that: - Do not allow to permanently delete data from the repo, see :ref:`append_only_mode`. -- Use a pull-mode setup using ``ssh -R``, see :issue:`900`. +- Use a pull-mode setup using ``ssh -R``, see :ref:`pull_backup` for more informations. - Mount C's filesystem on another machine and then create a backup of it. - Do not give C filesystem-level access to S.