SQL Server backup to URL no mechanism to retry on backup errors Msg 3013, Level 16, State 1, Server, Line 1

Running Microsoft SQL Server 2016 (SP2-CU2) 13.0.5153.0 and below I can confirm that in August of 2018 there is currently no retry logic for Backup to URL.  If you use Backup To URL functionality natively or in conjunction with Ola Hallengren scripts  any blip, transient network issue/failure, or even Blob service issues/throttling during the backup process will cause a high level generic error failure code.  These errors are random at best, but the product unfortunately is working as designed and expected as retry logic is not currently built into the Backup To URL functionality.  It would be extremely beneficial and I would welcome the addition in any and all future SQL versions.

 Backup to URL was a new feature introduced in SQL Server 2012 so it has been around for 5+ years.  While this was a new feature, I would say very few truly use this even today.  If you are running an environment that is 100% Azure based then I feel that this is a feature that you need to look at as space is cheap and if the networking/VM instance is sized in the upper tier for Upload/Download bandwidth then the times for backup and restore are very much and can be faster than ISCI targets you might backup to today in a local environment.   
This issue "FIX: Intermittent failures when you run backups to Azure storage from SQL Server" was reported to be fixed in some SQL versions on Sept. 24, 2018.    This problem was supposedly fixed in an on-demand hotfixes for SQL Server 2016 Service Pack 2 Cumulative Update 2.  After you apply this hotfix, the SQL Server version is 13.0.5206.0.

 Additionally, the hotfix is also included in Cumulative Update 3 for SQL Server 2016 Service Pack 2.  I have yet to test if this is resolved but once updated to a patched SQL version I will report back the results and version it was tested in.  
Example of a random backup error:
Date and time: 2018-08-15 01:05:17
Command: BACKUP DATABASE [xxx_xx] TO URL = N'https://xxxxxxxxxxxxxxxxxx.blo
Msg 3201, Level 16, State 1, Server XXXXXXXXXXXX
Cannot open backup device 'https://xcczocccxxxxcc.blob.core.windows.net
Operating system error 50(The request not supported.).
Msg 3013, Level 16, State 1, Server XXXXXXXXXXX. Line 1
BACKUP DATABASE is terminating abnormally.
Outcome: Failed

Comments

Post a Comment

Popular posts from this blog

How to mass update all or some sql server agent job step commands

How to mass update all or some sql server agent job step and commands using TSQL.   This will use the built-in Replace function to search text in SQL agent jobs  SQL Agent Job information is stored in MSDB and can reviewed using some of the following queries: SELECT * FROM msdb.dbo.SysJobs SELECT * FROM msdb.dbo.SysJobSteps -- OR SELECT a.name as job_name, b.step_name, b.subsystem, b.command, b.database_name, a.enabled       ,a.description, a.date_created, b.job_id, b.step_id   FROM [dbo].[sysjobsteps] as b   INNER JOIN sysjobs as a ON a.job_id = b.job_id Since I will be focusing on the Commands column I will look at using this query to extract data into a temp table so that I can test any updates with the replace step before doing an update to MSDB. This would be your opportunity to archive or save any commands as needed.  Some people may prefer to generate all the syntax necessary to use EXEC sp_update_jobstep so you a...
Read more

SQL Monitoring for Blocking and Locking Capture and Log to table with sp_WhoIsActive or sp_BlitzWho

Image
You can use  sp_WhoIsActive or sp_BlitzWho and log the capture data to a table.   In my example I will use sp_whoisactive as I am more familiar with its use and data collection, however I will look at creating a future post using BlitzWho.  I will provide a few examples that were used to determine that the paid SQL monitoring products can be fancy tools but can be useless if you don't understand the basic concepts or even an understanding of how we capture similar data or in some cases more finely tuned to a specific scenario or use case.  Sometimes these paid solutions are incorrect or things can simply go wrong (Services Fail to start or the data is aggregated and misses something like the query commands and SQL Fragments) and it's always good to plan ahead and be prepared.   Sp_WhoIsActive is a procedure written by Adam Machanic. It can be found here:  sp_whoisactive downloads Sp_BlitzWho is a procedure written by the Brent Ozar team....
Read more

SQL Server General Index Naming Convention

SQL Server General Index Naming Convention  easy to follow:  PK_ for primary keys PK_  Primary Keys, which are logical constructs and not necessarily physical constructs, get tagged with a PK_ prefix. In most systems that I design the PK_ isn’t a clustered index.  IX_ for non clustered non unique indexes IX_  standard single or even multi-column indexes used for seeks or intersection just get prefixed with an IX_ (for  I nde X ). In cases where I need a composite index (i.e., multiple columns) but still explicitly ‘tolerate’ key/bookmark lookups, I’ll still call my seek/intersection/composite indexes IXes. UK_ for unique keys UK_  for unique key index UX_ for unique indexes UX_  for unique index. CLIX_ for Clustered Index (non PK) CLIX_  (non-PK) Clustered Index name is prefixed with CLIX (for  CL ustered  I nde X ) Additionally, I like to code all Create Indexes in SQL 2012 and above with an if not ...
Read more