docker container ls | grep redmine_mariadb_1 | cut -d' ' -f1: Get the ID (first field of the output cut -d' ' -f1) of the running docker container named redmine_mariadb_1.docker exec -it (container ID) (command): Run a command on a running docker container.See below on instructions how to do that.įull command: docker exec -it $(docker container ls | grep redmine_mariadb_1 | cut -d' ' -f1) mysqldump -uroot bitnami_redmine | xz -e9 -zc - > redmine-database-dump-$(date -I).sql.xz You need to determine the appropriate ID each time you do a backup. Important note: The container ID can change so it is not sufficient to just find the container ID once and then use it. This part is slightly more complicated, since we need to access the MariaDB server running in a different container. To me, this seems like a good compromise between the ability to recover deleted files and the used storage space. Note that old versions of files in redmine_data will be overwritten, however files that are deleted locally will not be deleted on the backup server. You can sync it using rsync -checksum -Pavz /var/lib/redmine/redmine_data my.rver:~/redmine-backup/ This is pretty easy, as the data is all in just one directory. We assume that the redmine is installed as shown in my previous post in /var/lib/redmine. and that you want to backup to my.rver:~/redmine-backup/ using rsync. Note that automating the backup is not within the scope of this post. This post will teach you how to easily make an online backup of your Redmine installation. In a previous post I detailed how to install Redmine on Linux using the excellent Bitnami docker image.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |