Troubleshooting SQL Server 2014 backup/restore problems
If you have problems with SQL Server 2014 backup or restore, review this troubleshooting
checklist to find potential solutions.
1. Install the latest SQL Server 2014 service pack.
Because many SQL Server 2014 backup/restore bugs were fixed in SQL Server service packs,
you should install the latest SQL Server service pack.
At the time this article was written the latest SQL Server 2014 service pack was service
pack 1. You can download the SQL Server 2014 service pack 1 at here:
https://www.microsoft.com/en-us/download/details.aspx?id=46694
2. The Volume Shadow Copy Service (VSS) backup operations are not successful
when they run at the same time.
This problem occurs when the auto-recovery option is enabled. This bug was first fixed
in Cumulative Update package 1 for SQL Server 2014. You can download the Cumulative
Update package 1 for SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/2931693
3. When you set up a Transactional replication and Initialize a transactional
subscription from a backup then during the initial synchronization the
Distribution Agent fails.
In this case, the error message occurs: “Could not find stored procedure ‘sp_MSins_”.
This bug was first fixed in Cumulative Update package 1 for SQL Server 2014.
You can download the Cumulative Update package 1 for SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/2931693
4. The error 3456 occurs when you try to restore the full database backup
that is taken from the secondary.
This is the error message text: “Could not redo log record (7699660:807911:68), for
transaction ID (7:-1072820627), on page (3:2044928), allocation unit”. This bug was
first fixed in Cumulative Update package 1 for SQL Server 2014. You can download
the Cumulative Update package 1 for SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/2931693
5. Cannot remove backup file after you restore the database from Windows Azure
Blob storage service.
This problem occurs when you use the RESTORE HEADERONLY or RESTORE FILELISTONLY
command to restore a database. This bug was first fixed in Cumulative Update
package 5 for SQL Server 2014. You can download the Cumulative Update package 5
for SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/3011055
6. Cannot restore database by using the full backup and differential backup files
when one of the transaction log files were removed.
This problem occurs when you have a database that has two transaction log files
and then you remove one of the transaction log files, perform a full backup and
a differential backup and then try to restore the database. This bug was first
fixed in Cumulative Update package 5 for SQL Server 2014. You can download the
Cumulative Update package 5 for SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/3011055
7. The “out-of-range” error occurs when you use SQL Server Managed Backup to
Windows Azure.
This problem occurs when the default order for date is mdy in SQL Server 2014,
but the date order of the operating system differs from this. This bug was first
fixed in Cumulative Update package 5 for SQL Server 2014. You can download the
Cumulative Update package 5 for SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/3011055
8. When SQL Server 2014 database contains a large transaction log file, you
cannot restore the database in the Microsoft Azure binary large objects
(BLOB) storage service.
This problem occurs when if the transaction log file is so large that it takes
longer than 3 minutes to restore it. This bug was first fixed in Cumulative
Update package 7 for SQL Server 2014. You can download the Cumulative Update
package 7 for SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/3046038
9. The error occurs, when you try to use Clustered Shared Volumes (CSV) as a
source or destination in performing a backup or restore database activity
in Microsoft SQL Server 2014 Management Studio (SSMS 2014).
This is the error text: “Cannot access the specified path or file on the server”.
This bug was first fixed in Cumulative Update package 8 for SQL Server 2014.
You can download the Cumulative Update package 8 for SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/3067836
To work around this problem, you can use Transact-SQL statements to perform
the backup or restore database activity in a new query window.