From 046d2b91c3fc0d5e0bfa5eec0678d3f5868c7849 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Matija=20=C5=A0uklje?= Date: Sun, 11 Feb 2024 17:23:44 +0100 Subject: [PATCH] Fix broken link in borgbackup.md Rogue space was the cause ;) --- .../20.backups/10.backup_methods/01.borgbackup/borgbackup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/02.administer/20.backups/10.backup_methods/01.borgbackup/borgbackup.md b/pages/02.administer/20.backups/10.backup_methods/01.borgbackup/borgbackup.md index cf19049c..11584f08 100644 --- a/pages/02.administer/20.backups/10.backup_methods/01.borgbackup/borgbackup.md +++ b/pages/02.administer/20.backups/10.backup_methods/01.borgbackup/borgbackup.md @@ -69,7 +69,7 @@ Then restore the archive in the usual way. ### Restore large archives If the available space is less than the weight of your archive, decompressed data and dependencies, you will have to restore part by part, app by app. -If restoring app by app is not enough OR if an archive is too big, it may be a good idea to generate a tarball without the "big" data of an app as if it had been generated with the [BACKUP_CORE_ONLY option] (/backup/include_exclude_files#don't-save-large-quantities-of-data). Example with Nextcloud: +If restoring app by app is not enough OR if an archive is too big, it may be a good idea to generate a tarball without the "big" data of an app as if it had been generated with the [BACKUP_CORE_ONLY option](/backup/include_exclude_files#don't-save-large-quantities-of-data). Example with Nextcloud: ``` app=borg; BORG_PASSPHRASE="$(yunohost app setting $app passphrase)" BORG_RSH="ssh -i /root/.ssh/id_${app}_ed25519 -oStrictHostKeyChecking=yes " borg export-tar -e apps/nextcloud/backup/home/yunohost.app "$(yunohost app setting $app repository)::ARCHIVE" /home/yunohost.backup/archives/ARCHIVE.tar ```