Chunk size / Copy Compatible Question

[dwtp]

Hi, I currently have several TB backed up locally on ZFS and also into B2. I previously had this also backed up to Storj but my Storj backup was using the same default chunk sizes as B2/Local so I was paying a lot extra for the segment fees.

I just set up a new Storj backup with the init command and then re-added it to the Duplicacy GUI. I assume, based on the chunk sizes, that it is not possible to copy between local and Storj at this point. Is this correct? I’m wondering if my best recourse is to do a fresh local backup and then copy to Storj? (I’m trying to get rid of B2).

Also I wasn’t super clear on how to specify copy compatible (or bit identical, or both? Do I need both?) during the init command. I had run ./duplicacy_linux_x64_3.2.3 init -e -c 32M -max 64M -zstd -storage-name Storj -key /config/duplicacy-pub.pem all s3://us-1@gateway.storjshare.io/duplicacy

Thanks!

[saspus]

Chunk sizes specified when creating fresh destination in init only affect chunk creation during backup. Copying chunks does not meaningfully alter data sizes.

[dwtp]

What prompted my question was this:

2025-01-28 15:29:58.904 INFO STORAGE_SET Source storage set to /backups/duplicacy
2025-01-28 15:29:58.917 INFO STORAGE_SET Destination storage set to s3://us-1@gateway.storjshare.io/duplicacy
2025-01-28 15:29:59.481 ERROR CONFIG_INCOMPATIBLE Two storages are not compatible for the copy operation
Two storages are not compatible for the copy operation

I then dove into reading about both init and add. Add has the -copy flag for making the storages copy compatible, meaning it would also override the chunk size flags specified if I were to delete the config and re-run add in place of init?

I assume that implies that, regardless, if I want to be able to have all of my PCs and such back up to my ZFS file share, and then simply copy that into Storj instead of having to backup again to Storj, that I would need to destroy and recreate my local backup?

[saspus]

@dwtp

Add has the -copy flag for making the storages copy compatible, meaning it would also override the chunk size flags specified if I were to delete the config and re-run add in place of init?

Correct:

gilbertchen/duplicacy/blob/master/src/duplicacy_config.go#L256-L271

@dwtp

ZFS file share, and then simply copy that into Storj instead of having to backup again to Storj, that I would need to destroy and recreate my local backup?

Correct.

[dwtp]

Thanks for confirming!