Based on the discourse_docker repository I have written a small script to automate using it inside a vagrant machine (run with set -x to see what is actually done) Did I copy the backup to the wrong location? And what the log line Making sure /var/www/discourse/tmp/restores/default/2020-05-13-190…

I meant: for now I recreated a brand new vagrant machine, no copying of any previous backups. Did the bootstrapping and starting the docker container. Did the backup. Nothing is seen in the vagrant machine outside of the docker machine. I think I’ve found the issue: I’ve mounted this docker-shared…

vagrant isn’t supported, but here’s some advice anyway. :wink: [image] pihentagy: rsync -P --verbose /home/pihentagy/infra/icontest-2020-05-12-033823-v20200506044956.tar.gz shared/standalone/backups/default I’m not sure how rsync works. Does the path need to end with a slash? If the file lan…

[image] 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 …

[image] RGJ: You could start a backup from within Docker ( discourse backup ) and see where it ends up on your host filesystem. Oddly it is not visible from the host filesystem. Should it? vagrant@ubuntu-xenial:~$ sudo docker exec -w /var/www/discourse -i discourse discourse backup Starting …

[image] pihentagy: any way to highlight lines in code blocks? ```bash The default here is text. I believe that the default for new installs is ‘guess the language’,

I meant “look ma, line 5 is important!”, so basically highlight specific line(s).

[image] pihentagy: Oddly it is not visible from the host filesystem. Should it? Well, usually /var/discourse/shared/standalone/backups is the directory that is visible in your container as /var/www/discourse/public/backups (hence the word shared). Your rsync command is putting the backup insi…

[image] pihentagy: I meant “look ma, line 5 is important!”, so basically highlight specific line(s). No. You can’t do that in a code block since everything is presented verbatim.

Well, now I just did a backup and checked if it can be found outside the docker machine and it cannot. vagrant@ubuntu-xenial:~$ sudo docker inspect -f "{{.Mounts}}" discourse [{bind /var/discourse/shared/standalone /shared true rprivate} {bind /var/discourse/shared/standalone/log/var-log /var/l…

[image] pihentagy: So my question: if I create a backup, should I see it from outside of docker? Yes, and this is the same thing as what your original problem is: “if you have a backup outside of docker and you put it in the shared directory, you should see it inside docker” (and you don’t). …

Restroring problems

Support

gerhard (Gerhard Schlager) May 13, 2020, 8:44pm 2

vagrant isn’t supported, but here’s some advice anyway.

I’m not sure how rsync works. Does the path need to end with a slash? If the file lands in the correct directory, make sure the copied file is readable by the server.

Topic		Replies	Views
How to backup and restore a whole /var/discourse app folder? Self-hosting	17	6046	June 19, 2020
How can I get the current version information from my backup? Support	14	544	May 31, 2025
How to backup Discourse when The backup has failed? Self-hosting	8	1100	August 5, 2020
Hangs discourse and discourse restore FAILED Self-hosting	24	2402	August 26, 2020
Move a Discourse site to another VPS with rsync Sysadmins migrations , how-to	55	8754	August 17, 2025

Restroring problems

Related topics