Additional info: http://blogs.msdn.com/b/psssql/archive/2013/11/07/all-about-rollbacksnapshottempdb.aspx

We are facing a problem with SQL 2014 (12.0.4416 SP1 CU1).  It's being used to host SharePoint 2013 databases, which when backing up use the autorecovered snapshots option.

This fails and we get loads of RollbackSnapshotTempDBGUID databases left behind in failed/pending recovery mode.

We're narrowed down the issue to the drive that the database log files are located on.  If the log files are located on a drive with 4K sectors then the backups fail, if we move the logs to 512 or 512e drives then the backups work.

Normal backups are fine all the time, regardless of the drive sector size.

We've tried attaching the databases without the log file so SQL created new logs on the 4K disks (in case this was an allignment/4K sector detection issue) but it didn't help

Has anyone come across this? or have any ideas for a solution?  It's looking a bit like a bug.

• Edited by DJL Wednesday, July 22, 2015 10:29 AM

Thanks I had seen that, but it's a bit old and doesn't mention native 4k support

According to this: https://support.microsoft.com/en-us/kb/926930 4K native is supported. 

• Edited by DJL 18 hours 24 minutes ago

Hi DJL,

Regarding to this SQL Server 2014  backup issue, personally I would recommend you submit a feedback to the Microsoft Connect at this link https://connect.microsoft.com/SQLServer/Feedback  . Your feedback enables Microsoft to offer the best software and deliver superior services.

Thanks,
Lydia Zhang

If you have any feedback on our support, please click here.