how do i get an id&key for duplicacy cli access to b2? via the b2 web app? which isn’t available for linux? via the duplicacy gui? just to get cli access? via the b2 cli app? via the b2 android app?
Welcome to the forum!
You must generate the Key ID and Application Key via B2 web interface:
hmm, backblaze b2 seems to be their “storage” offering, as if a different product/service than “backup”, should i just shrug that off as marketing, is it all really just the same?
As you said yourself, they are different products. One is the storage service (B2) and the other a backup application/service (personal and business).
Duplicacy is an excellent solution for backing up to the cloud using B2 storage, with an excellent cost-benefit ratio.
1 Like
ok thanks, tried b2. now trying to try wasabi. but apparently need more help:
#: WASABI_KEY=... DUPLICACY_WASABI_SECRET=... DUPLICACY_PASSWORD=... duplicacy_linux_x64_2.4.0 -v backup -stats -threads=1 -storage=s3://us-east-2@s3.wasabisys.com/dustwi/0
No storage named 's3://us-east-2@s3.wasabisys.com/dustwi/0' is found
#: WASABI_KEY=... DUPLICACY_WASABI_SECRET=... DUPLICACY_PASSWORD=... duplicacy_linux_x64_2.4.0 init -e jw s3://us-east-2@s3.wasabisys.com/dustwi/0
The repository / has already been initialized
#: WASABI_KEY=... DUPLICACY_WASABI_SECRET=... DUPLICACY_PASSWORD=... duplicacy_linux_x64_2.4.0 backup -stats -threads=1 -storage=s3://us-east-2@s3.wasabisys.com/dustwi/0
No storage named 's3://us-east-2@s3.wasabisys.com/dustwi/0' is found
#: rename `/.duplicacy' -> `/_/.duplicacy~0'
#: WASABI_KEY=... DUPLICACY_WASABI_SECRET=... DUPLICACY_PASSWORD=... duplicacy_linux_x64_2.4.0 backup -stats -threads=1 -storage=s3://us-east-2@s3.wasabisys.com/dustwi/0
Repository has not been initialized
#: WASABI_KEY=... DUPLICACY_WASABI_SECRET=... DUPLICACY_PASSWORD=... duplicacy_linux_x64_2.4.0 init -e jw s3://us-east-2@s3.wasabisys.com/dustwi/0
Enter S3 Access Key ID:...
Enter S3 Secret Access Key:...
Failed to download the configuration file from the storage: BadRequest: Bad Request status code: 400, request id: B8C5EF6DD384D326, host id: lvp5dcDg+dE4D7+Ocf68A69tO/QrN41rJKzLAfRerqxOnjDVW+WF4eNOw4YgsRZapLoTtC67cd28
apparently it didn’t help that i put WASABI_KEY and DUPLICACY_WASABI_SECRET in the environment? and other problems? any help appreciated, thank you.
Try using wasabi backend: wasabi://...
Is “dustwi” the bucket?
Syntax:
wasabi://region@s3.wasabisys.com/bucket/path
wasabi://us-east-1@s3.wasabisys.com/bucket/path
wasabi://us-east-2@s3.us-east-2.wasabisys.com/bucket/path
wasabi://us-west-1@s3.us-west-1.wasabisys.com/bucket/path
wasabi://eu-central-1@s3.eu-central-1.wasabisys.com/bucket/path
See:
https://forum.duplicacy.com/t/supported-storage-backends/1107#wasabi
still getting
Failed to download the configuration file from the storage: BadRequest: Bad Request
status code: 400, request id: C453807C309D407F, host id: 9huf0snqKl249wQWqOeo4DOrUNYddU+j7REGgl5fWqcJtiZaCAOa3s4L1PNTEre7oPbSFnJA5R5G
i’m finding it a bit daunting to extract needed information re accessing wasabi from irrelevant information. is there anywhere a succinct guide to exactly how/where to create/find the needed id&key from wasabi, what environment variables to assign them to, and which duplicacy commands need them?
thanks again
Can you post the full command line that gave the error in your latest post? Please make sure that you use the correct endpoint for the region where the bucket is located.
BadRequest answered for right or wrong key so indeed likely the wrong endpoint:
0#: DUPLICACY_PASSWORD=… duplicacy_linux_x64_2.4.0 init -e jw wasabi://us-east-2@s3.wasabisys.com/dustwi/0
Enter Wasabi key:CORRECTWASABIKEY
Enter Wasabi secret:CORRECTWASABISECRET
Failed to download the configuration file from the storage: BadRequest: Bad Request
status code: 400, request id: 06709FC93C70B216, host id: /Aw93rwtdPXh8aqFuiuGXZRqaERc3xCt3uTKAv4TJkIIOHeisWl3HKCQ/fuvLTmZh7QdvechTxzb
east-1 likely the right endpoint, here’s what happens with the wrong key:
100#: DUPLICACY_PASSWORD=… duplicacy_linux_x64_2.4.0 init -e jw wasabi://us-east-1@s3.wasabisys.com/dustwi/0
Enter Wasabi key:INCORRECTWASABIKEY
Enter Wasabi secret:CORRECTWASABISECRET
Failed to configure the storage: InvalidAccessKeyId: The AWS Access Key Id you provided does not exist in our records.
status code: 403, request id: EF6D063620AE2283, host id: jOCeF/91/ZeDHEgwnJCfQStUgsBl2dygMXt9nPCJBBmdAImvOP2+0XiqA8eZrgq7eBLe4Yq218Rb
and here’s the right key but the wrong secret:
100#: DUPLICACY_PASSWORD=… duplicacy_linux_x64_2.4.0 init -e jw wasabi://us-east-1@s3.wasabisys.com/dustwi/0
Enter Wasabi key:CORRECTWASABIKEY
Enter Wasabi secret:INCORRECTWASABISECRET
Failed to configure the storage: SignatureDoesNotMatch: The request signature we calculated does not match the signature you provided. Check your key and signing method.
status code: 403, request id: 3860CA5EA7B3266A, host id: 3sb5DV5jz+vxljcRThpWux8WDApwzn3p3VPB8OiEspY8IH0tMO6FdW+5ufqSgdTNsXAHUyK2KzE/
but with what i believe are the right endpoint, key, and secret, why AccessDenied?:
100#: DUPLICACY_PASSWORD=… duplicacy_linux_x64_2.4.0 init -e jw wasabi://us-east-1@s3.wasabisys.com/dustwi/0
Enter Wasabi key:CORRECTWASABIKEY
Enter Wasabi secret:CORRECTWASABISECRET
Failed to configure the storage: AccessDenied: Access Denied
status code: 403, request id: 010759BDCBF6DEFA, host id: sY30vYVPiPQ2A5zjGxqHwx9W1XIwgVyWRw35lsEya1d/awv3O/3Rb4cvCEzi86CxP9Fiebj3snNn
100#:
So, that’s correct, isn’t it?
thank you, it’s off and running now.
is it safe to launch another instance of duplicacy on the same system to have a peek at what’s in storage already, or might that step on the cache or in some way confound the ongoing backup?
And what was the cause of the problem? What did you do to fix it?
This is important for the forum as a knowledge base.
storage url wasabi://us-east-2@s3.us-east-2.wasabisys.com/dustwi/0
is it safe to launch another instance of duplicacy on the same system to have a peek at what’s in storage already, or might that step on the cache or in some way confound the ongoing backup?
Do you mean another instance running check command? No problem!
But if you are still running the first backup (revision) there will be practically nothing to show. If you want to check the amount of data already sent, it may be better via the Wasabi interface. Another option is to follow up with the -verbose option.