Moving backed up files to new hardware and relinking the existing backup

Support
,
#1

I’m moving files, photos to a new server. These files are presently backed up the Backblaze B2. I plan to relocate the folder hosting these files, along with its .duplicacy folder, without changing its subdirectory structure. I hope to do this so that its backup schedule runs as before.

My concern is that Duplicacy will see these as modified files, and re-upload all to B2. Or otherwise download the B2 content to compare file hash.

How can I best prevent this? I’m using Duplicacy Web running is a docker container. Thanks!

#2

It won’t do either of those things.

If you change files modification date while copying (don’t do that — use tools that keep timestamps, such as rsync -a) duplicacy will process the file and generate the same chunks that already exist on the target and it will skip upload.

Otherwise duplicacy simply won’t notice it has been moved.

#3

Thanks. Before I do all that, I have to relocate the docker container. Hopefully that is simple, but as there are no configuration folder mappings, I presume this will involve a full container rebuild (I’m using saspus/duplicacy-web:mini)

Since my typical volume mapping looks like:

    volumes:
      - /volume/library:/data/library:ro

I’ll be changing it to :

    volumes:
      - /mnt/newnas/library:/data/library:ro

Hopefully that, and redefining the “host” is all that is involved

#4

Configuration shall be outside of the container, containers are disposable

There is nothing typical in volume mappings, it’s specific to the container. Refer to the user guide/readme file from the container your are using.