"Invalid storage location" when trying to move data to Backblaze B2

usegalaxy.eu support
, ,
1

I’m trying to move the datasets in a history (8228344521d4e949) to my Backblaze B2 storage but when I try and do this with the “Manage storage location” option, I get told that “The selected storage location is not available or is invalid.”. However when I test on the “Test Instance” option in user storage preferences, all tests pass and I have been using this storage from Galaxy for some time. Can someone advise on what to do?

2

Hi @Peter_van_Heusden

The EU team can clarify more about how this particular B2DROP repository is set up, but from what I know, you’ll need to use these tools to export data to the location:

  • Tool panel → Export datasets to repositories
  • History menu → Export History to File (includes a repository destination)

In short, repositories options are available for asynchronous import and export steps. FAQ: How do I manage my repositories on Galaxy? More external resources will work this way.

And then storage options are available for direct reading/writing of data. FAQ: How do I manage my Galaxy storage? This is the group that will work with the Job Details → Dataset Storage → Relocate Dataset function. It is smaller group of external resource options (so far!) as it is dependent on how well live data sync is supported.

Does this help? Would you like to test the dataset export tool and let us know if it works or not? Thanks! :slight_smile:

3

This could also be a bug, I recommend opening an issue in the upstream repo. I will loop in one of our developers as well.

4

Thank you @Peter_van_Heusden for letting us know! I will investigate what is flagging your remote storage as invalid and hopefully fix it. Unfortunately, it is a bit of bad timing with the holidays around the corner, so the fix might take longer to land… sorry for the inconvenience.

5

Thanks @davelopez - I have opened an issue here. Unfortunately I couldn’t quite make sense of which API calls are involved in this operation so I couldn’t debug very deeply.

6

No worries! The fix was very simple in the end and it is already ready for review. Hopefully it will be merged and deployed soon!

Thanks again!