mirror/borg
1
0
Fork 0
mirror of https://github.com/borgbackup/borg.git synced 2025-02-22 14:11:27 +00:00
Code Issues Releases Wiki Activity

Merge pull request #5911 from KN4CK3R/forwardport-5902

Browse source 
Forwardport pull request #5902
This commit is contained in:
TW 2021-07-19 23:04:48 +02:00 committed by GitHub
commit 96af6dd144
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 16 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
docs/deployment/pull-backup.rst
View file

@ -32,7 +32,7 @@ file system will probably change, and you may not have access to those files if
BorgBackup is not run with root privileges.
SSHFS is a FUSE file system and uses the SFTP protocol, so there may be also
other unsupported features that the actual implementations of ssfs, libfuse and
other unsupported features that the actual implementations of sshfs, libfuse and
sftp on the backup server do not support, like file name encodings, ACLs, xattrs
or flags. So there is no guarantee that you are able to restore a system
completely in every aspect from such a backup.
@ -46,6 +46,21 @@ completely in every aspect from such a backup.
client. Therefore, pull mode should be used only from servers you do fully
trust!
.. warning::
Additionally, while being chrooted into the client's root file system,
code from the client will be executed. Thus, you should only do that when
fully trusting the client.
.. warning::
The chroot method was chosen to get the right user and group name-id
mappings, assuming they only come from files (/etc/passwd and group).
This assumption might be wrong, e.g. if users/groups also come from
ldap or other providers.
Thus, it might be better to use ``--numeric-owner`` and not archive any
user or group names (but just the numeric IDs) and not use chroot.
Creating a backup
-----------------