![]() It’s just a lot of work to make that happen. Furthermore, you could copy between storages of different chunk sizes. You’d have to repack chunks and rewrite snapshot files, but you could theoretically do it on-the-fly, in memory. Encryption would be the easy part (it already re-encrypts when copying between copy-compatible storages, unless using -bit-identical?). Technically, it would be feasible (and quite useful imo) to add functionality to copy backups from any storage. With just a few clicks, you can effortlessly set up backup, copy, check, and prune jobs that will reliably protect your data while making the most efficient use of your storage space. So I ended up with copy- incompatible unencrypted storages, because I had copied them from an existing encrypted storage.Ī freshly-made unencrypted storage, however, will have the same chunk-seed, hash-key, and id-key hashes - all three, it appears, using “6475706c6963616379” as the magic number. Duplicacy comes with a newly designed web-based GUI that is not only artistically appealing but also functionally powerful. ![]() It didn’t work.īut not because of encryption! The chunk-seed and hash-key parameters are different (and obvious the chunks themselves, split on different boundaries). copy encrypted_store1 -> unencrypted_tmpstore1, copy encrypted_store2 -> unencrypted_tmpstore2, copy unencrypted_tmpstore2 into unencrypted_tmpstore1. ![]() Indeed, I had an idea from this discussion to see if we could use an unencrypted storage as an intermediary. Compare Duplicacy alternatives for your business or organization using the curated. Hope I don’t confuse things here, but I found out that not all unencrypted storages are necessarily copy-compatible… Duplicacy is available for Windows, Mac and Linux. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |