Symptoms

Assume that you use the SQL Server Managed Backup to Microsoft Azure feature to manage and automate SQL Server backups to Microsoft Azure Blob storage in Microsoft SQL Server.

When you try to back up a database that's large, it takes a very long time and the retention thread might restore header only. In this scenario, you may notice that the Managed Backup fails because of SQLVDI error that resembles the following: 

ErrorCode=(183) Cannot create a file when that file already exists

Resolution

This issue is fixed in the following cumulative updates for SQL Server:

      Cumulative Update 1 for SQL Server 2017

      Cumulative Update 9 for SQL Server 2016 RTM

      Cumulative Update 6 for SQL Server 2016 SP1

      Cumulative Update 7 for SQL Server 2014 SP2

Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:

Latest cumulative update for SQL Server 2017

Latest cumulative update for SQL Server 2016

Latest cumulative update for SQL Server 2014

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information

To get more information about SQL Server Managed Backup to Microsoft Azure, see the following link: SQL Server Managed Backup to Microsoft Azure.

References

Learn about the terminologythat Microsoft uses to describe software updates.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×