I am in the middle of an effort to move my duplicacy storage from google drive to backblaze b2. I read the duplicacy add command instructions carefully and did a
duplicacy add -e -copy default --bit-identical ... to add the b2 storage. As per the documentation, this option tells duplicacy to copy the
FileKey to the new storage from the old one to the effect that the names of the chunks generated during backup will be identical in the new storage.
When I ran the add command, with an empty b2 bucket, it just created an emtpy fossils, chunks, snapshots folder along with a new config file which was 330 bytes. The old config file (in gdrive) was 402 bytes.
I then rclone’ed the duplicacy storage files (snapshots, fossils, chunks, etc.) from google drive to b2 using
rclone. I backed up the new config file because
rclone sync would copy the old config file over to the B2. I believe it is the config file which contains the IDKey, ChunkKey, and FileKey, and also the encryption password/salt in some shape/form for an encrypted storage.
To my surprise, the new storage works perfectly with the old config copied to it - I am able to do
duplicacy list -a,
duplicacy list -a -files as well as
duplicacy check -a -stats and everything is giving me the same result for both the storages.
Should I copy back the correct newly generated config file to the b2 storage or is the old config file ok to use? If so, why is there a size difference between the two with the same settings and password? If not, then how does it work perfectly with the old config file? What was the purpose of the bit-identical and copy in add storage if all i had to do was copy the config file over?
The notes section does mention not copying the config file from an unencrypted storage to an encrypted one, but in my case both storages are encrypted (using the same password as well), have the same chunk size and all other settings.