That has been really handy with my compose deployment but would also work as a backup in case some containers are standalone. There was a really great script posted here which will backup all running containers into compose files. I need to get a rebuild process together if any of this want tits up but it should be quite easy to do although I’m going to be reviewing my backup process soon once I’m further down the road with compose. However I’m going to add the compose files to a backup too so I can quickly restore containers without faffing with gitea. These compose files are then stored in my self hosted gitea repository (which is backed up as part of the persistent volume backup). I’ve recently just started moving some containers into compose files and grouping containers together.
#Dropshare vs. duplicacy Pc#
Next I have a veeam backup from my desktop PC to my server backing up my photo libraries, duplicacy then in turn backs that veeam Backup into wasabi. This actually goes into google drive but I’m thinking of moving it to wasabi too. First is backing up my docker volumes so my persistent data is safe. Backups and restores are easy and it seems straight forward to adminster.
#Dropshare vs. duplicacy free#
So I moved across to duplicacy on my server which whilst isn’t free also doesn’t cost the earth. Problem was something happened to the database and i couldnt fix it. I used to use duplicati as it was free and supported S3 storage. If that's the case, and I do need Duplicacy on every host, it seems like I would need to spend some time documenting exactly where my config files are stored so that when shit hits the fan, I don't have to try and figure it out - or worse yet, fail to figure it out and be screwed. I've been experimenting with Duplicacy (UI and CLI).īacking up to local fileserver: Is Duplicacy the right tool for this? Or is there another tool I should consider using for local backups?īacking up to Cloud (B2): Should I push to the Cloud from each host? Or should I just back up from my fileserver? (Backup the backup)ĭocker Backups: When backing up Docker, it seems like I should just be backing up my docker-compose.yml and volumes - or is there a better way? Wanting to do a test restore to see how this works.ĭuplicacy Config Files: I noticed that if I try to run Duplicacy from a directory where my config file doesn't live, Duplicacy throws a "there are no backups" message, which was surprising the first time. I'm planning to back everything up locally to a fileserver, and then also back up to Backblaze B2.
#Dropshare vs. duplicacy archive#
Duplicacy can use the same backup archive for backup jobs on different machines. But there is another killer feature on the duplicacy side: cross-source deduplication. I have a simple setup, with 4 hosts (one being a vert). Another conclusion I draw from the above discussion is that, compared to duplicacy, duplicati saves a lot of remote storage space (which usually costs money). Recently posted here about the home lab that I've been working on.
0 kommentar(er)
