Cyberduck Mountain Duck CLI

#11252 closed defect (worksforme)

Azure Blob container metadata

Reported by: Kremit72 Owned by:
Priority: highest Milestone:
Component: azure Version: 7.7.0
Severity: blocker Keywords:
Cc: Architecture:


Hi there, Trying out Mountain Duck to be able to throw data directly from G Suite vault extraction into an azure blob container, the tool thusfar has worked great, however i have noted that standard metadata files/attributes etc are not created when "downloading" the data into the attached containers, unlike AZCopy etc would create them. I have looked at the advanced options to do this however it is a bit confusing. I am currently trying to work through the steps provided however they seem to be tailored towards mac's rather than a windows environment. Any assistance would be appreciated, if i can work this out i will recomend BitTitan recomend you in future for GSuite migrations.

Attachments (1)

BlobMetadata.png (52.6 KB) - added by Kremit72 on Nov 19, 2020 at 5:14:40 AM.

Download all attachments as: .zip

Change History (3)

Changed on Nov 19, 2020 at 5:14:40 AM by Kremit72


comment:1 Changed on Nov 19, 2020 at 5:16:32 AM by Kremit72

the uploaded image shows the metadata on two files one added to the azure blob container using MountainDuck (left) and one using azcopy (right)

comment:2 Changed on Nov 22, 2020 at 4:22:39 PM by dkocher

  • Resolution set to worksforme
  • Status changed from new to closed

Not sure but it looks like these additional metadata are proprietary keys added by another software. We do not add any default metadata when writing files with Cyberduck or Mountain Duck. Also refer to Windows Azure Blob Storage.

Note: See TracTickets for help on using tickets.