Export Database to Storage account - Error "The ImportExport operation failed because the storage blob already exists."

Question

Export Database to Storage account - Error "The ImportExport operation failed because the storage blob already exists."

Simona Pantini 65

I'm trying to export a database, by running the command through an Automation Account. I gave the Automation Account access to the SQL Server and to the storage account.

This is the command:

New-AzSqlDatabaseExport -AuthenticationType Sql -ResourceGroupName $sourceResourceGroupName -ServerName $sourceServerName -DatabaseName $sourceDatabaseName -StorageKeytype "StorageAccessKey" -StorageKey $secureKey -StorageUri $storageUri  -AdministratorLogin $cred.UserName -AdministratorLoginPassword $sourceSecurePassword

When I try to run the runbook with this command, this error appears:

The ImportExport operation failed because the storage blob already exists.

I've already checked that all the parameters are correct and the container is empty: there isn't any blob in the container.
Both the storage account and the database have network restrictions, but they are on the same subnet and there is a private link between their private endopint.

How can I solve this?

Accepted answer

1 additional answer

Your answer

Answer 1

RahulRandive 10,486 Volunteer Moderator

Hi @Simona Pantini

Is your Storage behind a firewall? if yes, it's currently not supported.

Please check the below limitations.

User's image Thank You

Simona Pantini 65 Reputation points

2024-04-10T09:19:57.0566667+00:00

It has a private endopoint. Can this be the problem?
It will work only with "Public network access" enabled?
RahulRandive 10,486 Reputation points Volunteer Moderator

2024-04-10T12:38:52.92+00:00
Hi Simona Pantini

No, private endpoint should not be the problem, but you have to approve the private endpoint at the storage and SQL server level.
Approve private endpoint connection on Azure SQL Database

Go to the Azure SQL logical server that hosts the database.

Navigate to the Networking page under Security

Select the Private access tab.

Select the private endpoint you want to approve.

Select Approve to approve the connection.

Approve private endpoint connection on Azure Storage

Go to the storage account that hosts the blob container where the .bacpac file exists.

Open the Private endpoint connections page in the Security menu.

Select the private endpoint for the import/export service.

Select Approve to approve the connection.

Hope this help!

Thank You!
Simona Pantini 65 Reputation points

2024-04-10T12:40:53.0833333+00:00

There is an already existing private endpoint.
Do i need to use the import/export with private endpoint which creates a new endpoint?
RahulRandive 10,486 Reputation points Volunteer Moderator

2024-04-10T12:45:02.4933333+00:00

Yes, and once the export/import completed, I believe it will get deleted automatically as it's created only for this process.

This one-
Simona Pantini 65 Reputation points

2024-04-10T12:55:28.6833333+00:00

Thank you for your help. Unfortunately I needed this solution in order to automate the export/import activities and, by needing to manually approve the private endpoint, it would no longer be the solution I was looking for.
RahulRandive 10,486 Reputation points Volunteer Moderator

2024-04-10T13:06:37.8866667+00:00

Hi Simona Pantini,

Understood. Please check the blog below to see if it helps in your scenario.

https://techcommunity.microsoft.com/t5/azure-database-support-blog/automate-exporting-of-azure-sql-database-as-bacpac-to-blog/ba-p/2409213

Thank you!
Simona Pantini 65 Reputation points

2024-04-10T15:13:58.3966667+00:00

Thank you.
I've already read this blog, but unfortunately it doesn't help.
I'll find another solution for my scenario.

Thank you so much for your help.
RahulRandive 10,486 Reputation points Volunteer Moderator

2024-04-10T16:33:41.9466667+00:00

Hi Simona Pantini,

You are most welcome. I appreciate your feedback, and I apologize that the shared automation did not meet your specific needs.

By any chance, if you find my answer and comments useful, please remember to mark them as the accepted answer.

Thank You!

Answer 2

Hi, Welcome to MS Q&A

The error message "The Import-export operation failed because the storage blob already exists" indicates that there might be a conflicting blob in the storage container with the same name as the one you're trying to export.

Here are some steps you can take to troubleshoot and potentially resolve this issue

Currently, the private link for import/export has the following limitations:

Import or Export of a database from Azure SQL Managed Instance using PowerShell isn't currently supported.
Check for Existing Blobs: Even if the container appears empty, there might be blobs with hidden or system properties. Use Azure Storage Explorer or another tool to inspect the container and ensure that there are no existing blobs with the same name as the one you're trying to export. If you find any, you may need to delete them or choose a different name for your export

Reference Image and docs are below

User's image

https://learn.microsoft.com/en-us/azure/azure-sql/database/database-import-export-private-link?view=azuresql&source=recommendations

Please check and let us know , kindly accept answer , if it helps, Thankyou!

Simona Pantini 65 Reputation points

2024-04-09T15:21:43.4233333+00:00

Hi!
-I'm not trying to export a database from Azure SQL Managed Instance, but from Azure SQL Database
-I've already checked for Existing Blobs and I assure that the container is empty.

What can be the problem?

Share via

Export Database to Storage account - Error "The ImportExport operation failed because the storage blob already exists."

1 additional answer

Your answer