#Duplicacy black friday update#

saspus has done a wonderful job of making the image itself pretty straightforward to run. The data directories are set with read-only access, which further boosts my confidence that the data itself can’t get mangled by an error of some sorts. The second are the data directories I want backed up. Setting all 3 chunk size parameters to the same value makes Duplicacy switch to the fixed-size chunking algorithm which works more efficiently with virtual machine images. The first set of volumes are data directories for Duplicacy. The following init command is recommended for backing up VMWare images: duplicacy init -c 1M -max 1M -min 1M -max 1M repositoryid storageurl. Note that, although the above variables are named slightly differently, they follow the tried-and-true approach from LinuxServer.io that I appreciate so much. (I have the comment there so that, when I look at this file again three months later, I can remember why I have some hardcoded numbers typed into the file.) I also set the timezone so that timestamps are obvious to me. Here I set the user and group IDs for the local user I want backing up the data. GRP_ID=ABC # group id group on the system This is how we configure it while running the image. Hostname is the key used by Duplicacy’s Personal license.

#Duplicacy black friday update#

The next time I need to update this image, it’ll be easy to see what I’m coming from, where I’m going, and what the changes are. The author of this image (saspus) has done a great job providing versioned images over time. This way I won’t be surprised when, say, a new version of an image requires or breaks the current configuration. My personal preference is to lock images down to a specific version, if at all feasible. Let’s step through some of the interesting bits here, much of which is derived from the instructions in the saspus/duplicacy-web image’s README file. volume1/docker/duplicacy-web/cache:/cache volume1/docker/duplicacy-web/logs:/logs volume1/docker/duplicacy-web/config:/config USR_ID=XYZ # user account id on the system Here are the contents of the docker-compose.yml for this project:. I tend to use docker-compose to build and run my images and containers. Configuration is not difficult, and the Duplicacy Web interface works well enough to get the job done. About Duplicacyĭuplicacy describes itself as “a new generation cross-platform cloud backup tool.” I like it because it performs incremental backups on a regular basis. You can also read about how I run the Unifi controller, how I run Plex, and how I update DuckDNS. This is my fourth post documenting containers I use at home. In this post, I’ll explain how I have Duplicacy run nightly via Docker. Every night, I have Duplicacy backup data from my local NAS to Backblaze B2. Want ('context'.Context, string, string, io.Reader, bool, string, string, swift.My preferred remote backup solution is Duplicacy. Have (string, string, *RateLimitedReader, bool, string, string, nil) Src//gilbertchen/duplicacy/src/duplicacy_swiftstorage.go:237:39: not enough arguments in call to Want ('context'.Context, string, string, bool, swift.Headers) Src//gilbertchen/duplicacy/src/duplicacy_swiftstorage.go:226:47: not enough arguments in call to Src//gilbertchen/duplicacy/src/duplicacy_swiftstorage.go:210:45: not enough arguments in call to Want ('context'.Context, string, string, string, string) Src//gilbertchen/duplicacy/src/duplicacy_swiftstorage.go:198:38: not enough arguments in call to Src//gilbertchen/duplicacy/src/duplicacy_swiftstorage.go:193:40: not enough arguments in call to Want ('context'.Context, string, *swift.ObjectsOpts) Src//gilbertchen/duplicacy/src/duplicacy_swiftstorage.go:171:47: not enough arguments in call to Src//gilbertchen/duplicacy/src/duplicacy_swiftstorage.go:137:34: not enough arguments in call to connection.Container Setting the env var GO111MODULE=auto lets the build go past that error, but I am getting another one during compilation: src//gilbertchen/duplicacy/src/duplicacy_swiftstorage.go:132:31: not enough arguments in call to connection.Authenticate