Note that there are some explanatory texts on larger screens.

plurals
  1. PORestore Database from URL (Azure storage) fails without further details
    text
    copied!<p>On a Windows Azure VM running Windows 2008 R2 and SQL 2012 Enterprise SP1 CU5, I'm trying to restore a backup stored in Azure as a page blob with the new functionality RESTORE DATABASE FROM URL. So far I've done it several times with backups up to 60GB in size (uncompressed) and it works like a charm. However, there is a particular backup 32GB in size that I can't restore. It fails with the following error message:</p> <pre><code>Msg 3013, Level 16, State 1, Line 2 RESTORE DATABASE is terminating abnormally. </code></pre> <p>No further information is provided as to why it fails. If I download the same backup from to the local hard drive I can restore it without problem. I tried executing </p> <pre><code>dbcc traceon(3004,3605,-1) </code></pre> <p>to get more info and I can see that the DB is restored successfully, then it zeroes in the log file and after that completes is when it fails. There isn't any error message in the SQL logs, neither in Windows Event log. There is plenty of free space on that hard drive. VM and storage are in the same datacenter and I've followed all best practices in building the environment.</p> <p>EDIT> I noticed the following lines in Event viewer AFTER the database is restored and BEFORE it starts restoring the LOG file (in other words, while the log file is being zeroed)</p> <pre><code>SQLVDI: Loc=CVDS::Close. Desc=Open devices!. ErrorCode=(0). Process=2900. Thread=1104. Client. Instance=MSSQLSERVER. VD=Global\https://url/stuff/xx.bak_SQLVDIMemoryName_0. SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=2900. Thread=1104. Client. Instance=MSSQLSERVER. VD=Global\https://url/stuff/xx.bak_SQLVDIMemoryName_0. SQLVDI: Loc=TriggerAbort. Desc=invoked. ErrorCode=(0). Process=1508. Thread=2008. Server. Instance=MSSQLSERVER. VD=Global\https://url/stuff/xx.bak_SQLVDIMemoryName_0. </code></pre> <p>Is it possible that the connection to Azure storage times out before the zeroing finishes and thus the RESTORE fails? If so, how do I change this timeout?</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload