Agentless, cloud-native backup for Microsoft Azure
Post Reply
NAP-LN
Influencer
Posts: 10
Liked: never
Joined: Feb 20, 2023 2:11 am
Contact:

Slow export of Azure SQL DB

Post by NAP-LN »

We have a 49GB SQL database hosted in Azure on a serverless tier on the Standard-series(Gen5) hard ware.

We had some initial issues with the backup timing out but we got this resolved by adjusting the worker instance size on the Veeam for Azure appliance. We are now using a Standard_L4s for our medium sized profile but the initial backup took over 7 hours to complete.

I came in this morning and ran the job again to see if it would complete faster however it seems just as slow.

The bottleneck in the VBR console say N/A and the processing rate initially starts at 31MB/s, drops to 6MB/s before finally falling down to 2 and then 1.

Any suggestions on the possible cause of this delay with Azure SQL?
lyudmila.ezerskaya
Veeam Software
Posts: 179
Liked: 54 times
Joined: Oct 04, 2021 4:08 pm
Full Name: Lyudmila Ezerskaya
Contact:

Re: Slow export of Azure SQL DB

Post by lyudmila.ezerskaya »

Hi!
The issue may be related to the Bacpac export process itself.
To improve performance, we recommend using a staging server configured with a performance tier adjustment via the appropriate configuration key. If you already use a staging server for backups, please open a support case for further investigation.
NAP-LN
Influencer
Posts: 10
Liked: never
Joined: Feb 20, 2023 2:11 am
Contact:

Re: Slow export of Azure SQL DB

Post by NAP-LN »

I have a ticket open so going through that as well.

Using a staging server saw no difference however the creation of the staging server was very quick.

I tried a BACPAC export via the Azure GUI, selected the temp storage location and started the job. 59GB DB too 6 hours and 30 odd minutes to create.
nielsengelen
Product Manager
Posts: 5883
Liked: 1232 times
Joined: Jul 15, 2013 11:09 am
Full Name: Niels Engelen
Contact:

Re: Slow export of Azure SQL DB

Post by nielsengelen »

Could you share your support case ID so we can look into it and understand if this could be improved?
GitHub: https://github.com/nielsengelen
Post Reply

Who is online

Users browsing this forum: No registered users and 3 guests