Does anyone know how to get uSync to download media from Azure blob storage when serialising data for transfer? Thanks

Hi, It should 'just' work. there can be some fiddly things if you are using Umbraco 8 and your container names are certain things, but for later .net core. it picks them up and works.

It doesn't work sadly. It only creates the reference files but doesn't download the media itself.

is this 'core' uSync (as in the free one) or uSync.Complete (as in the paid one)

it's the free one

ahh the free one doesn't copy the actual media, it leaves that as an "exercise for the reader" , you can copy the files between azure blogs using something like storage explorer and then when you run the import uSync will add the media elements to the DB and everything will appear as if by magic.

This is relevant to me.. as we look to migrate from v8 with media on azure to v13

We just copy the whole storage container when needed. This is usually only from dev to test to "pre-fill" a test environment. Works fine. We wouldn't want uSync to copy the actual BLObs to be honest. We use Azure Storage in dev/test/live and uSync all the things.

It's ready and built , I am just having lunch 🙂

TANSTAAuSyncL

If we migrate the media with usync, (manually copying the files), I assume that it will allow is to maintain the URLs?

Yes, the "media ID" and "filename" part will be intact. But if you add other stuff it will have to match. CDN, container name, etc.

Hit presumably 256 char path lengths when trying to export

Not sure what you mean. Who imposes that limit and what on? Just to clarify, we always "migrate" media from dev to test to live using uSync + copying the BLObs manually and it works fine.

Windows file system limit 😭

Our uSync media files are e.g.,

uSync\v9\Media\foobar.config

. So paths are exactly as lengthy as other uSync files

Yes, but "foobar" here is the name of the media... and I have media which 250+ names in the char it fails to export.

Sounds like you need to set use guid filenames. then all the names will be the keys and the length won't matter. (v8 config docs - https://docs.jumoo.co.uk/usync/8.x/reference/config)