Thanks for this have been trying to get nextcloud aio to backup for 4 hours without success. But this method is so much better and now I have learned to backup my dockers :)
That is extremely useful! Can you suggest how to modify the lines so i can do the back up on another ssd dor example. Can use these commands with cron jobs?
Happy to help, feel free to join the discord and we can help you there :) for the latest link go to one my of newer videos and my discord link is in the description :)
Was on my watch later list for two weeks, in the mean time I found own solution. I tried to add podman solution to comment, but youtube doesn't like it and does not like links. Interesting platform, indeed. Most "fun" part about podman is remapping user ids. But I just put NC into maintenance mode run mysqldump and volume export trough zstd pipeline. podman volume export/import are likely commands specific to podman which consume/produce tar on input/output and work with pipes. Maybe stopping containers and doing volume exports is easier, cause restoration process is more simple and it can combined into weekly maintenace task (backup, pull, prune)
Great that you found your own way via Podman. I really want to automate the way I showed in the video by creating a pipeline to do it. Will see how that goes!
@@Techdox Thanks, I was thinking about using syncthing to synchronize backup folder between two servers or ask my friend who mentioned using rsync. At least some use for zimaboard 216, which i replaced by Fujitsu Esprimo Q956.
I'm thinking of using bind mounts for my nextcloud containers to simplify this backup process, is this a right way to approach this or are there drawbacks.
Hey, you can use bindmounts but another suggestion would to use standard volumes and then use something like duplicati to backup. It’s one of my recent videos
I've decided to use kopia in stead of duplicati after some research@@Techdox now i have succesfully snapshots of all my important data, including the docker volumes.
Thanks a lot for the video. It has a very clear explanation. One key challenge is observe is the image that you created the first time is not destroyed. So all persistent data still exists. Can you try deleting the image on your local machine or rebuilding it using docker compose up -d --no-deps --build.? I have the data and mariadb folders along with the doccker compose yaml file. however when i try to rebuild the image, the whole links are lost and i am unable to relink my mariadb and data folders. This is especially an issue if we want to move the server to a new computer or restore the installation from back up. Thanks a lot.
I might not be 100% understanding your comment but I did remove all content that was being used and restored it. The image itself the docker image shouldn’t really matter much as all I’m doing is pulling the same one if it was deleted
Nextcloud AIO may have some solutions for backup but keep in mind this is how to backup and restore Docker volumes in general. It would be great to have a guy front end to do these steps though. Might look into making something
I hope you enjoyed this video! Make sure to Subscribe if you did! - 96% of my viewers are not subscribed 🫣
Thanks for this have been trying to get nextcloud aio to backup for 4 hours without success. But this method is so much better and now I have learned to backup my dockers :)
That is extremely useful! Can you suggest how to modify the lines so i can do the back up on another ssd dor example. Can use these commands with cron jobs?
Happy to help, feel free to join the discord and we can help you there :) for the latest link go to one my of newer videos and my discord link is in the description :)
Thanks for a great video. I will be implementing this process today.
Glad it was useful
Was on my watch later list for two weeks, in the mean time I found own solution. I tried to add podman solution to comment, but youtube doesn't like it and does not like links. Interesting platform, indeed. Most "fun" part about podman is remapping user ids. But I just put NC into maintenance mode run mysqldump and volume export trough zstd pipeline. podman volume export/import are likely commands specific to podman which consume/produce tar on input/output and work with pipes.
Maybe stopping containers and doing volume exports is easier, cause restoration process is more simple and it can combined into weekly maintenace task (backup, pull, prune)
Great that you found your own way via Podman. I really want to automate the way I showed in the video by creating a pipeline to do it. Will see how that goes!
Made a Python script to do just the backups so far, plan to keen working on this - github.com/Techdox/docker_backup
@@Techdox Thanks, I was thinking about using syncthing to synchronize backup folder between two servers or ask my friend who mentioned using rsync. At least some use for zimaboard 216, which i replaced by Fujitsu Esprimo Q956.
I'm thinking of using bind mounts for my nextcloud containers to simplify this backup process, is this a right way to approach this or are there drawbacks.
Hey, you can use bindmounts but another suggestion would to use standard volumes and then use something like duplicati to backup. It’s one of my recent videos
I've decided to use kopia in stead of duplicati after some research@@Techdox now i have succesfully snapshots of all my important data, including the docker volumes.
Thanks a lot for the video. It has a very clear explanation. One key challenge is observe is the image that you created the first time is not destroyed. So all persistent data still exists. Can you try deleting the image on your local machine or rebuilding it using docker compose up -d --no-deps --build.?
I have the data and mariadb folders along with the doccker compose yaml file. however when i try to rebuild the image, the whole links are lost and i am unable to relink my mariadb and data folders. This is especially an issue if we want to move the server to a new computer or restore the installation from back up. Thanks a lot.
I might not be 100% understanding your comment but I did remove all content that was being used and restored it. The image itself the docker image shouldn’t really matter much as all I’m doing is pulling the same one if it was deleted
So there is no gui to do the whole backup and restore docker volume etc in Nextcloud AIO? Can it do history version like Duplicati?
Nextcloud AIO may have some solutions for backup but keep in mind this is how to backup and restore Docker volumes in general.
It would be great to have a guy front end to do these steps though. Might look into making something
How can i combine it with borg or restic to use incremental backups?
Hey, feel free to join the discord. I can help you better there :)