mirror of
https://github.com/borgbackup/borg.git
synced 2026-05-21 17:41:22 -04:00
docs: sshfs + chroot does support different CPU architectures, fixes #6878
(cherry picked from commit 49365617c4)
This commit is contained in:
parent
316d774bbd
commit
f40878e1e7
1 changed files with 10 additions and 0 deletions
|
|
@ -52,6 +52,14 @@ completely in every aspect from such a backup.
|
|||
code from the client will be executed. Therefore, you should do this only when
|
||||
you fully trust the client.
|
||||
|
||||
.. warning::
|
||||
|
||||
The SSHFS + chroot method requires that the backup server and the client
|
||||
use the same CPU architecture (e.g. both x86_64), as binaries from the
|
||||
client (like ``/bin/sh`` or the ``borg`` binary) are executed on the
|
||||
backup server. If you have different architectures, use the :ref:`socat_method`
|
||||
instead.
|
||||
|
||||
.. warning::
|
||||
|
||||
The chroot method was chosen to get the right user and group name-id
|
||||
|
|
@ -205,6 +213,8 @@ Note that in this scenario the tar format is the limiting factor – it cannot
|
|||
restore all the advanced features that BorgBackup supports. See
|
||||
:ref:`borg_export-tar` for limitations.
|
||||
|
||||
.. _socat_method:
|
||||
|
||||
socat
|
||||
=====
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue