# Restroring problems

**URL:** <https://meta.discourse.org/t/restroring-problems/151369>\
**Category:** Support\
**Tags:** unsupported-install\
**Created:** [May 13, 2020, 7:21pm UTC](https://meta.discourse.org/t/restroring-problems/151369 "2020-05-13T19:21:25Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![RGJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rgj/32/523185_2.png) [@RGJ](https://meta.discourse.org/u/RGJ)\
**Post date:** [May 13, 2020, 9:58pm UTC](https://meta.discourse.org/t/restroring-problems/151369/4 "2020-05-13T21:58:51Z")

</div>

> [@gerhard](#):
>
> I’m not sure how rsync works. Does the path need to end with a slash?

It is not required, but not ending the path with a slash is bad practice since the result depends on the directory already existing or not.

If the destination directory already exists, there does not need to be a slash and the file is copied inside the directory.  
If the destination directory does not exist and there is no slash at the end, the file is copied to a file ‘default’  
If the destination directory does not exist and there is a slash at the end, the directory is created and the file is copied into it.

In this case the copying seems to go well (by luck).

However,

> [@pihentagy](#):
>
> ```plaintext
> + vagrant ssh -c 'sudo docker exec -w /var/www/discourse -i discourse discourse restore'
> You must provide a filename to restore. Did you mean one of the following?
> 
> Connection to 127.0.0.1 closed.
> 
> ```

Since there are no suggestions after “did you mean one of the following?”, the file is not in the correct place. It looks like the drives are mapped incorrectly to the docker container.

You could start a backup from within Docker (`discourse backup`) and see where it ends up on your host filesystem.

---

_[View the full topic](https://meta.discourse.org/t/restroring-problems/151369)._