Still I am curious, there is no way to migrate from old to new PCs? I mean, it could be so easy, because from Win7 to Win10 we can have perfectly matching paths.įrom what you describe you didn’t upgrade your computer from Win7 to Win10, but you “migrated” to a fresh Windows installation. So the only “nuisance” is having to setup the various storages, backups and schedules again. So when you create a new storage and specify a location that already contains a Duplicacy backup, Duplicacy-Web will ask for the password of that storage and - assuming it’s correct - you’re once again connected to that storage and can proceed as before. Assuming that you still know password #2 (and of course have the credentials for #1) you can create a new storage that will connect to your old backup. This is an optional password that you can use to control access to the Duplicacy Web UI.Īs I gather, you’ve lost password #3, but that doesn’t mean that you have to redo all your backups from scratch. From your descriptions, this is the one that you didn’t remember, because it was stored in the keychain/keyring and you probably never had to enter it beyond setting it once during the initial setup. This is the one that is usually stored in a keychain/keyring (or similar) if possible. The master password that Duplicacy uses to encrypt all your storage encryption passwords.This is set (or not) on a per-storage basis. If you choose client-side encryption, then you can set a password on the Duplicacy backend storage. The encryption password (if any) for your Duplicacy backend storage.This would be handled by the gcd_token.json file in your case. The login credentials to your backend storage (where needed).So in principle you are dealing with (up to) 4 passwords/login credentials: ![]() Perhaps I am not getting your point, but there seems to be some confusion here re. Will all take massive time, because my repositories were quite complex. Will have to deal with Google Drive token again… Yeah, especially upload to Google Drive weighs like “100 hours”. I really hope I can configure my Local and Google Drive storages properly again. I think I could boot into the old OS again, but I have no clue yet how I can “export” the Duplicacy configuration. Unfortunately tried all my passwords, plus the stored in PW manager, plus the one which is stored in Chrome (it has stored a password named “GoogleOne”, yes, I have a GoogleOne store), but none works. Install Duplicacy (only for user, do not run it afterwards), thenĬ:\Disk\Windows_OLD\Users\Michel.duplicacy-webĬ:\Disk\Windows_OLD\Users\Michel\AppData\Local\DuplicacyWebEdition\Ĭ:\Users\Michel\AppData\Local\DuplicacyWebEdition\ĮDIT: Uninstalled and re-Tried all above steps. ![]() I have made the old C: accessible via c:\Disk\Windows_OLD\ and can copy all the nice stuff over to the new one. ![]() Hi, yes of course, I have kept all usernames and paths the same from Win7 to Win10, which usually makes life easy, but not here. “Failed to decrypt the testing data using the supplied password: cipher: message authentication failed” Well I can’t remember what kind of Password that was supposed to be… I’ve stored a password and a license key in my pw db, but does not seem to be related. I installed Duplicacy-web via installer and copied the following, before first run:Īnything else I can do? I then started Duplicacy - but the web interface says “Please enter the password to encrypt/decrypt the passwords/credentials stored in the configuration file.” Is there a way I can easily Migrate Duplicacy to the new Windows? If there’s no registry stuff, my preferred way to do it is copying application settings as in “%appdata%”, or whereever applications store their data, from the old storage device to the new one. Now I am finding the time to finally migrate to Windows 10, a lot of work to do, maaaany applications to be installed and reconfigured again.
0 Comments
Leave a Reply. |