Backup of azure SQL managed instances

There are a couple of methods of protecting SQL instances in Azure. The old method is the ‘bacpac’ method which Azure imposes a max 200GB limitation. However, from version 2023+ (11.30) there is a new method which I think supports up to 8TB in size. Use this option instead and you wont have the 200GB issue:

https://documentation.commvault.com/2023e/essential/using_staging_path_export_method_for_secure_transfer_of_data.html

​@Damian Andre 

So on this methode you are not using storage account to export the DB. But i am not seeing the option to use staging path:

​@Damian Andre Ok i found the staging path, this option is available on the client self where sql agent installed or on Access node which used to backup the sql.

After setting up and starting new backup i am still getting error that can't export the database

here is the log from the job.

Hi ​@Egor Skepko 

Good day!

At the moment. We use BACKUP To URL mechanism for Managed Azure SQL Backups. For this mechanism, connecting to Azure Storage Account via a Storage Connection String from CV and Connecting to Azure Storage Account via a SAS token from Managed Azure SQL Instance is a must.

 

Please find detailed explanation below.

We support BACKUP TO URL (Azure Storage) mechanism for “Azure SQL Database Managed Instance” protection and do NOT have any plans on supporting Using the Staging Path Export Method for a Secure Transfer of Data mechanism for “Azure SQL Database Managed Instance” protection.

We have two different entities being protected on Azure side – Azure SQL Database and Azure SQL Database Managed Instance. As explained earlier, we use different mechanisms to protect these 2 different entities.

Using the Staging Path Export Method for a Secure Transfer of Data mechanism is used ONLY for Azure SQL Database and NOT for Azure SQL Database Managed Instance. As seen in BOL screenshot below, you see this mechanism included under “Azure SQL Database” protection section only.

Whereas BACKUP TO URL (Azure Storage) mechanism is used ONLY for Azure SQL Database Managed Instance and NOT for Azure SQL Database. As seen in BOL screenshot below, you see this mechanism included under “Azure SQL Database Managed Instance” protection section only.

Due to following reasons, we support BACKUP TO URL (Azure Storage) mechanism for “Azure SQL Database Managed Instance” protection. Accordingly, we do NOT have any plans on supporting Using the Staging Path Export Method for a Secure Transfer of Data mechanism for “Azure SQL Database Managed Instance” protection.

1. BACKUP TO URL is more efficient widely adopted mechanism for “Azure SQL Database Managed Instance” protection because it is natively supported by MS for this very purpose.

2. MS even discourages the use of Using the Staging Path Export Method for a Secure Transfer of Data mechanism for backup and restore due to a few limitations of this mechanism compared to BACKUP TO URL mechanism
   1. BACPACs are not intended to be used for backup and restore operations
   2. As per MS prerequisites, we need to create copy of the Azure SQL Database being backed up to first create transactionally consistent copy of it and then we can export from this copy. So customers need to pay for the storage of copied database that resides on Azure side for the duration of the export.
   3. For larger databases, BACPAC export/import might take a long time, and might fail for various reason.
   4. If the export operation exceeds 20 hours, it might be cancelled

​@Syed_S Thank you for explanation, but with  BACKUP TO URL (Azure Storage)  i am getting same error, that can't export database.

Before generating SAS token i added to allow object and containers en i past the connection string to storage connection string under sql cloud configuration. And still getting ame error. 

​@Egor Skepko Following up on this thread.

First make sure you are running the latest MR release.

In the logs you shared it looks like this is specific to this storage account we are seeing. Do you know if this was reviewed on your side?

StatusMessage:Key based authentication is not permitted on this storage account.

ErrorCode:KeyBasedAuthenticationNotPermitted