Hello .

The delay was caused by the combination of products that must be updated in order to fix the issue (needed to update both managed portal and software). Full explanation has been provided in the ticket, we are sorry for this situation, it was exceptional and hard case to resolve, but thanks to your cooperation we could find out what could have caused it.

Once again, please take our apologies

Hi all,

The SAS (Shared Access Signatures) for Azure storage is now live for the MBS (web portal version 4.4)
https://forum.cloudberrylab.com/discussion/752/mbs-web-console-release-update-4-4-march-5-2019
and supported in our windows agent in 6.0.0.245.
https://forum.cloudberrylab.com/discussion/766/cloudberry-mbs-backup-agent-release-update-6-0-march-6-2019

Before now it worked the following way (and still works for older agents)
Backup Agent in APAC before sending data to the cloud storage in APAC has to sign all requests to the storage on MBS which is located in US East. Considering amounts of data to be transferred it turns to a huge wait.

Now, with SAS backup agents requests a token in our environment in US East and works with the token for a defined period of time of token validity.

For more information about SAS please read here:
https://docs.microsoft.com/en-us/azure/storage/common/storage-dotnet-shared-access-signature-part-1

Thank you.