-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to properly backup docker container? #2355
Comments
If I'm not wrong, the volume is a storage for documents/photos you upload through Monica, so maybe that's why it's empty for you. About the database volume, you can backup the SQL like this: Backup Restore inside the directory containing your |
Thanks, that's exactly what I was looking for! |
Same setup. Except perhaps more recent stack: Monica v2.13, Docker Compose 1.24.0, Docker 18.09.5. I really appreciate OP asking and @Pitasi taking the time to answer so clearly. I can confirm that using
Of course, the containers were up and running at the time (as evidenced by the successful backup operation). I thought perhaps the dump I was trying to restore could be using an old format (it's from an older version of Monica) so I also tried restoring the just-now created dump. But that still gave the same error. I found an SO answer that suggested using
Perhaps someone more well-versed in Docker can explain why the |
This issue has been automatically locked since there |
I followed the instructions to run Monica and mysql docker containers via docker-compose, and I have mounted volumes for both of them. My current method of backup is a script that runs daily that zips the mounted volumes for the mysql container and uploads it to Google Drive. However, the volume has been empty ever since I made my container, something I noticed recently. I notice in the Monica dashboard there's an option to export SQL, and that seems be the best option for backing up. Is there a way I can do this automatically via a script on my server? I'd like to be able to generate these SQL dumps and upload them the way I've been doing with the mounted volume.
The text was updated successfully, but these errors were encountered: