Hey guys,
I installed duplicacy-web yesterday to test it out. I created an SSH storage and a Google Drive storage.
I set two different passwords, the same Erasure Coding setting (10:1) and the same RSA public key for both storages. I also checked the box “make it compatible with” for the Google Drive storage, after the SSH storage was already created.
Now I made a backup job for the Google Drive and created a schedule to move the backup after completion to the ssh storage.
The second step fails.
The error message is, that there’s no private key available.
This seems odd: I don’t want to restore anything and both storages use the same public key. There should be no need to decrypt and encrypt the data between both storages.
Additionally, there was no way to specify a private key - so it’s obviously impossible that it’s not missing.
Running copy command from /home/rubenk/.duplicacy-web/repositories/localhost/all
Options: [-log copy -from GoogleDrive -to xxx]
2022-04-14 14:08:26.430 INFO STORAGE_SET Source storage set to gcd://Backup/Duplicacy
2022-04-14 14:08:35.600 INFO STORAGE_SET Destination storage set to sftp://xxxx/backups/duplicacy
2022-04-14 14:08:36.821 INFO BACKUP_ERASURECODING Erasure coding is enabled for the destination storage with 10 data shards and 1 parity shards
2022-04-14 14:08:36.821 INFO BACKUP_KEY RSA encryption is enabled for the destination
2022-04-14 14:09:40.079 INFO SNAPSHOT_COPY Chunks to copy: 2241, to skip: 894, total: 3135
2022-04-14 14:09:43.431 ERROR CHUNK_DECRYPT An RSA private key is required to decrypt the chunk
An RSA private key is required to decrypt the chunk