Reputation: 207
I tried to export Sql Database in azure to storage blob but the operation failed. I do this task daily last month and this issue is new. It shows as follows :
Error encountered during the service operation.Blob https://blob link/dbname-2019-1-16-14-24.bacpac is not writeable. The remote server returned an error: (403) Forbidden.The remote server returned an error: (403) Forbidden.
Upvotes: 9
Views: 7171
Reputation: 2478
In my case, I had Delete Lock on the resource group where storage was and every attempt to export one DB to that storage ended up with the error:
Failed to export the database: my_DB. ErrorCode: undefined ErrorMessage: undefined
Export of another DB on the same server was no problem. After deleting the Lock, the export started to work. I have no idea why it was like that, even though for a few years, everything was working with the Delete lock on RG.
Upvotes: 0
Reputation: 15694
Make sure a firewall rule does not exist. Please go to the Azure portal "Storage Accounts → "YourStorageAccountName" → Firewalls and Virtual Networks (left vertical panel). Put it to "Allow access" from "All networks". You can also configure the storage account with exceptions for trusted Microsoft services as explained here.
Upvotes: 0
Reputation: 9437
I had the same problem. I have contacted Azure support and this is their response.
We recently identified a regression in the import/export service that is generating incorrect SAS tokens to the storage accounts.
The engineering team has rolled out the fix, but it might take some time for the fix to get applied worldwide.
Please try the following link to access Azure portal and then perform the export operations:
https://portal.azure.com/?feature.canmodifystamps=trueµsoft_azure_storage=stage1
The portal shows an orange title bar if you open it via the above link, this is expected.
So, it should be already fixed by now.
Upvotes: 4
Reputation: 30035
If you're using sql scripts for back up following this link, then I suspect that the expired date of SHARED ACCESS SIGNATURE is reached.
Please re-generate SHARED ACCESS SIGNATURE, and then use the new key for backup.
Please let me know if any more issues.
Upvotes: 0