Add -hostname to your to your docker run command to set a persistent hostname for the container. So in order to utilize a license, you'll need to make sure that both of these pieces of data do not change over time. You will then receive a file named one-token.json which can be supplied to Duplicacy when prompted. Duplicacy identifies the machine via the hostname and machine-id pair. I was using CrashPlan, and my discounted Continue. Thanks in advance for any insights on the matter. It will take you to the OneDrive website and ask you to log in to OneDrive and grant Duplicacy the permission to back up files to your OneDrive. After I migrated my home server to use Proxmox, I began searching for a new offsite, cloud backup solution. Should I then use the "on-failure" option for my container restart policies?Īre there any other issues with this approach that I should be aware of? hotio/ duplicacy on Docker Hub testing-32eeca2 testing-1.6.3 testing hotio/ autoscan on Docker Hub nightly. Is it okay to encrypt the "docker" shared folder or will this cause problems with the overall system? Maybe you can find something interesting in this list. I understand that - upon bootup - docker containers wouldn't be able to startup automatically, since I need to mount the shared folder first, but that would be okay for me.Īm I using the "docker" shared folder as intended (to put the persistent data of my containers there) or does the system use this folder for something else? Since duplicacy does and potentially future containers may store sensitive data such as passwords there, I'd prefer to encrypt the "docker" shared folder, just like my data folder are all encrypted. If I'm using other docker containers in the future I also plan to create a subfolder for each container under "docker" and put the persistant data for that container there. Duplicacy Autobackup Duplicacy Autobackup is a Docker. I noticed that the docker app created a shared folder "docker" and created a subfolder "duplicacy" in there with further subfolders for all persistent data that needs to survive the destruction of the container (e.g. :floppydisk: Painless automated backups to multiple storage providers with Docker and duplicacy.
(I know there is a solution to run Duplicacy natively on Synology, but I prefer docker for this). I’m thinking there must be a whole lot more hidden system files, but I’m also wondering about the Trash…how do I exclude that.After a long hiatus I'm back to using docker on my DS1819+ and I'm running Duplicacy-web for my backups in a container. Bind-mount a host directory into the container at /etc/duplicacy to view, edit, and/or backup your configuration files (i.e. I would never restore apps, just user files. I’m creating an hourly snapshot of /users/, using the default snapshot retention settings and using zstd-fastest compression, as I think I saw someone post that on a thread somewhere.Īnd then another snapshot of /users/Downloads, with zstd-fastest and snapshot retention of 3 months and 0 Annual. I realise it’s all customisable, which is great, but would love a ‘starter kit’ / hear what others do. I’d like to know what files to exclude, snapshot policies, compression settings… I’m excited to start using Kopia…had issues over the years with others and for the past couple of years have just been using rclone sync, but I’m keen for something that ‘just works’
0 kommentar(er)
