forked from TrueCloudLab/restic
faq: Add entry about Synology NAS' sftp path
This commit is contained in:
parent
89c2ed2a1c
commit
fae3c4d437
1 changed files with 25 additions and 0 deletions
25
doc/faq.rst
25
doc/faq.rst
|
@ -90,3 +90,28 @@ scheduling algorithm to give it the least favorable niceness (19).
|
|||
|
||||
The above example makes sure that the system the backup runs on
|
||||
is not slowed down, which is particularly useful for servers.
|
||||
|
||||
Creating new repo on a Synology NAS via sftp fails
|
||||
--------------------------------------------------
|
||||
|
||||
Sometimes creating a new restic repository on a Synology NAS via sftp fails
|
||||
with an error similar to the following:
|
||||
|
||||
::
|
||||
|
||||
$ restic init -r sftp:user@nas:/volume1/restic-repo init
|
||||
create backend at sftp:user@nas:/volume1/restic-repo/ failed:
|
||||
mkdirAll(/volume1/restic-repo/index): unable to create directories: [...]
|
||||
|
||||
Although you can log into the NAS via SSH and see that the directory structure
|
||||
is there.
|
||||
|
||||
The reason for this behavior is that apparently Synology NAS expose a different
|
||||
directory structure via sftp, so the path that needs to be specified is
|
||||
different than the directory structure on the device and maybe even as exposed
|
||||
via other protocols.
|
||||
|
||||
The following may work:
|
||||
|
||||
::
|
||||
$ restic init -r sftp:user@nas:/restic-repo init
|
||||
|
|
Loading…
Reference in a new issue