|Reference||Can provide answers for|
|2027537 Best Practice recommendations for SQL Server Database Backups||The best practice recommendations for working on database backups.|
|BACKUP (Transact-SQL)||Provides answers to basic questions that are related to backup. Provides examples of different kinds of backup and restore operations.|
|Backup Devices (SQL Server)||Provides a great reference for understanding various backup devices, backing up to a network share and related tasks.|
|Recovery models (SQL Server)||Covers in detail the various recovery models: Simple, Full, and Bulk-Logged. Proviodes information about how the recovery model affects backups.|
|Back Up and Restore of System Databases (SQL Server)||Covers strategies, and discusses what you must be aware of when you work on backup and restore operations of system databases.|
|Restore and Recovery Overview (SQL Server)||Covers how the recovery models affect restore operations. You should review this if you have questions about how the recovery model of a database can affect the restore process.|
|Manage Metadata When Making a Database Available on Another Server Instance (SQL Server)||Various considerations that you should be aware of when a database is moved or you encounter any issues that affect logins, encryption, replication, permissions, and so on.|
|Working with Transaction Log Backups||Presents concepts about how to back up and restore (apply) transaction logs in the full and bulk-logged recovery models. Explains how to take routine backups of transaction logs (log backups) to recover data. |
Hint In SQL Server 2005 and the later versions, you can back up the log while any full backup is running.
|SQL Server Managed Backup to Windows Azure||A new feature that was introduced in SQL Server 2014 that automates backups by offering support for point-in-time restore operations.|
RESTORE DATABASE successfully processed 315 pages in 0.372 seconds (6.604 MB/sec)
|Knowledge Base or Books Online link||Explanation and recommended actions|
|Optimizing Backup and Restore Performance in SQL Server||The Books Online topic covers various best practices that you can use to improve the performance of Backup/Restore operations. For example, you can assign the SE_MANAGE_VOLUME_NAME special privilege to the Windows account that is running SQL Server to enable instant initialization of data files. This can produce significant performance gains.|
|2920151 Recommended hotfixes and updates for Windows Server 2012 R2-based failover clusters|
2822241 Windows 8 and Windows Server 2012 update rollup: April 2013
|Current system rollups can include fixes for known issues at the system level that can cause performance issues that affect programs such as SQL Server. Installing these updates can help prevent these issues.|
|2878182 FIX: User mode processes in an application are unresponsive on servers that are running Windows Server 2012 ||Backup operations are I/O intensive and can be affected by this bug. Apply this fix to help prevent these issues.|
|309422 How to choose antivirus software to run on computers that are running SQL Server||Antivirus software may hold locks on .bak files. This can affect the performance of backup and restore operations. Follow the guidance in this article to exclude backup files from virus scans.|
|2820470 Delayed error message when you try to access a shared folder that no longer exists in Windows 8, Windows 8.1, Windows Server 2012, or Windows Server 2012 R2|
|967351 A heavily fragmented file in an NTFS volume may not grow beyond a certain size|
|304101 Backup program is unsuccessful when you back up a large system volume|
|2455009 FIX: Slow performance when you recover a database if there are many VLFs inside the transaction log in SQL Server 2005, in SQL Server 2008 or in SQL Server 2008 R2||The presence of many virtual log files could affect the time that is required to restore a database. This is especially true during the recovery phase of the restore operation. For information about other possible issues that can be caused by the presence of many VLFs refer to KB 2028436.|
|A backup or restore operation to a network location is slow||Isolate the issue to the network by trying to copy a similarly sized file to the network location from the server that is running SQL Server. Verify the performance.|
|Symptoms or scenario||KB article|
|Backups of case sensitive databases failing||2987610 FIX: Error when you back up a database that has case-sensitive collation by using VSS in SQL Server 2012 SP2|
|Questions about VSS||919023 SQL Server 2005 connectivity and Volume Shadow Copy Service (VSS)|
|Third-party backups that are made by using VSS writer may fail and return 8229 errors.||2987610 FIX: Error when you back up a database that has case-sensitive collation by using VSS in SQL Server 2012 SP2|
|Understanding how VDI backup works||How It Works: SQL Server - VDI (VSS) Backup Resources|
|SQL Server or SQL Agent is running under a local system account and the backups fail||Give permissions to computer account on the Domain\ComputerName$ share.|
Microsoft recommends that you use dedicated domain accounts that possess only the required privileges in order to isolate the services.
RESTORE DATABASE test='d:\test.bak' WITH NO_CHECKSUM, FILE=1, REPLACE, CONTINUE_AFTER_ERROR, MOVE 'test' TO 'C:\test.mdf', MOVE 'test_log' TO 'C:\test_log.ldf'
|Symptom/Scenario||Remedial actions or additional information|
|Backups may fail when change tracking is enabled on the databases and return errors that resemble the following:|
Error: 3999, Severity: 17, State: 1.
<Time Stampt> spid<spid> Failed to flush the commit table to disk in dbid 8 due to error 2601. Check the errorlog for
|See the following Microsoft Knowledge Base articles:|
|Issues restoring backups of encrypted databases||Move a TDE Protected Database to Another SQL Server|
|Tying to restore a CRM backup from the Enterprise edition fails on a Standard edition||2567984 "Database cannot be started in this edition of SQL Server" error when restoring a Microsoft Dynamics CRM database|
Article ID: 224071 - Last Review: 07/23/2015 01:16:00 - Revision: 23.0
var varAutoFirePV = 1; var varClickTracking = 1; var varCustomerTracking = 1; var Route = "76500"; var Ctrl = ""; document.write("