1
0
Fork 0
mirror of https://github.com/borgbackup/borg.git synced 2024-12-26 01:37:20 +00:00

Merge pull request #1769 from ThomasWaldmann/ssh-url-docs

repo url / archive location docs + typo fix
This commit is contained in:
TW 2016-10-29 00:46:13 +02:00 committed by GitHub
commit 9c071771fc
2 changed files with 76 additions and 3 deletions

View file

@ -247,9 +247,7 @@ is installed on the remote host, in which case the following syntax is used::
$ borg init user@hostname:/path/to/repo $ borg init user@hostname:/path/to/repo
or:: Note: please see the usage chapter for a full documentation of repo URLs.
$ borg init ssh://user@hostname:port//path/to/repo
Remote operations over SSH can be automated with SSH keys. You can restrict the Remote operations over SSH can be automated with SSH keys. You can restrict the
use of the SSH keypair by prepending a forced command to the SSH public key in use of the SSH keypair by prepending a forced command to the SSH public key in
@ -265,3 +263,7 @@ mounting the remote filesystem, for example, using sshfs::
$ sshfs user@hostname:/path/to /path/to $ sshfs user@hostname:/path/to /path/to
$ borg init /path/to/repo $ borg init /path/to/repo
$ fusermount -u /path/to $ fusermount -u /path/to
You can also use other remote filesystems in a similar way. Just be careful,
not all filesystems out there are really stable and working good enough to
be acceptable for backup usage.

View file

@ -12,6 +12,77 @@ command in detail.
General General
------- -------
Repository URLs
~~~~~~~~~~~~~~~
**Local filesystem** (or locally mounted network filesystem):
``/path/to/repo`` - filesystem path to repo directory, absolute path
``path/to/repo`` - filesystem path to repo directory, relative path
Also, stuff like ``~/path/to/repo`` or ``~other/path/to/repo`` works (this is
expanded by your shell).
Note: you may also prepend a ``file://`` to a filesystem path to get URL style.
**Remote repositories** accessed via ssh user@host:
``user@host:/path/to/repo`` - remote repo, absolute path
``ssh://user@host:port/path/to/repo`` - same, alternative syntax, port can be given
**Remote repositories with relative pathes** can be given using this syntax:
``user@host:path/to/repo`` - path relative to current directory
``user@host:~/path/to/repo`` - path relative to user's home directory
``user@host:~other/path/to/repo`` - path relative to other's home directory
Note: giving ``user@host:/./path/to/repo`` or ``user@host:/~/path/to/repo`` or
``user@host:/~other/path/to/repo``is also supported, but not required here.
**Remote repositories with relative pathes, alternative syntax with port**:
``ssh://user@host:port/./path/to/repo`` - path relative to current directory
``ssh://user@host:port/~/path/to/repo`` - path relative to user's home directory
``ssh://user@host:port/~other/path/to/repo`` - path relative to other's home directory
If you frequently need the same repo URL, it is a good idea to set the
``BORG_REPO`` environment variable to set a default for the repo URL:
::
export BORG_REPO='ssh://user@host:port/path/to/repo'
Then just leave away the repo URL if only a repo URL is needed and you want
to use the default - it will be read from BORG_REPO then.
Use ``::`` syntax to give the repo URL when syntax requires giving a positional
argument for the repo (e.g. ``borg mount :: /mnt``).
Repository / Archive Locations
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Many commands want either a repository (just give the repo URL, see above) or
an archive location, which is a repo URL followed by ``::archive_name``.
Archive names must not contain the ``/`` (slash) character. For simplicity,
maybe also avoid blanks or other characters that have special meaning on the
shell or in a filesystem (borg mount will use the archive name as directory
name).
If you have set BORG_REPO (see above) and an archive location is needed, use
``::archive_name`` - the repo URL part is then read from BORG_REPO.
Type of log output Type of log output
~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~