![]() If you have a symmetric passphrase for the backups, an attacker doesn’t get control over your data by gaining access to your backup server. This reduces the attack surface drastically. You just need to copy the two docker volumes to a secure location.ĭedicated backup tools usually have the option to encrypt the files. Instead of rsync, you can also use your favorite backup tool, like BorgBackup or Duplicati – the principle is the same. owncloud_backup/įinally, you can restart the container: docker-compose start Using a Dedicated Backup Tool They can not only be important for restoring, it is always good to document how you set up the service.Īs they don’t change often, you don’t have to backup them every time – it suffices to backup them when you edit them. You should also copy the docker-compose file and. Sudo rsync -r /var/lib/docker/volumes/owncloud_mysql. sudo rsync -r /var/lib/docker/volumes/owncloud_files. Otherwise, if the disk gets corrupted, the backup would be affected, too. This example uses a folder on the docker host itself in production, you should save the files somewhere else. The other 2 docker volumes can be left out, they only carry temporary data. In the default case this should be owncloud_files and owncloud_mysql. You can do this by copying the docker volumes. Now you can copy the files and database to a secure location. With docker it makes sense to just shut down the container. The documentation recommends to enable the maintenance mode and stop the web server – but in this guide it’s not necessary. This was tested with Linux only – if you run docker on a Mac or Windows machine, you may have to adjust the volume paths. After this blog covered the installation of ownCloud with docker-compose, and the use of Traefik as a reverse proxy, you asked for a how-to about backup & restore strategies.
0 Comments
Leave a Reply. |