Support » Plugin: XCloner - Backup and Restore » Backblaze B2 Application Key vs Master Key

  • Resolved supahduck


    Setting up X-Cloner with the Backblaze B2 Remote Storage option.

    When verifying the B2 settings, it failed when using an application-specific key I had set up for it, but functioned properly when using my Master Application Key (which I’d prefer not to do, as I’d rather segregate each application’s bucket access).

    Is there a reason why the application key will not work? This has been noted as an issue on previous threads as well.

    Other than that one small issue, I’m very impressed and happy with the completeness, performance and clean interface on the plugin.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Liuta Ovidiu


    The library we are using for BackBlaze implementation does not support yet application key as stated on their page, as soon as support is added, we will add it as well. Might help to make a request on their page as well.



    Thanks for the info!

    Since we’re talking about B2 / Backblaze integration, I wanted to let you know about an issue with the connectivity.

    Much like the issue mentioned in this github post ( ), and with the same log entries, I am not able to get the B2 connector to successful complete a remote upload.

    No entries in the log other than the “initiation” of the job, when backing up one large file (~2GB).

    Breaking the backup into files of ~250MB resulted only two of the eleven files being uploaded.

    Breaking it up into files of ~50MB resulted in only nine of the 30+ files being uploaded, along with the CSV.

    Given that there’s nothing being recorded to the XCloner log, how do we troubleshoot this issue, given that there are so many layers to the connectivity (i.e. XCloner -> Flysystem -> Flysystem Backblaze connector -> B2)?

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Backblaze B2 Application Key vs Master Key’ is closed to new replies.