May 8, 2014 at 10:50 am
I have a process that restores all my backups on a centralized server for testing. I have recently upgraded this server to SQL server 2012 and now I am getting an error when restoring master from SQL Server 2008 R2. Restores from SQL Server 2012 and SQL Server 2005 work fine. I get the same results when trying to restore to SQL 2014 as well.
this is my restore statement
RESTORE DATABASE masttest
FROM DISK = 'c:\temp\master.bak'
WITH MOVE 'master' TO 'c:\temp\masttest.mdf',
MOVE 'mastlog' TO 'c:\temp\masttest.ldf';
and this is the results. The database ends up in Recovery pending.
Processed 400 pages for database 'masttest', file 'master' on file 1.
Processed 3 pages for database 'masttest', file 'mastlog' on file 1.
Converting database 'masttest' from version 661 to the current version 706.
Database 'masttest' running the upgrade step from version 661 to version 668.
Database 'masttest' running the upgrade step from version 668 to version 669.
Database 'masttest' running the upgrade step from version 669 to version 670.
Database 'masttest' running the upgrade step from version 670 to version 671.
Database 'masttest' running the upgrade step from version 671 to version 672.
Database 'masttest' running the upgrade step from version 672 to version 673.
Database 'masttest' running the upgrade step from version 673 to version 674.
Database 'masttest' running the upgrade step from version 674 to version 675.
Database 'masttest' running the upgrade step from version 675 to version 676.
Database 'masttest' running the upgrade step from version 676 to version 677.
Database 'masttest' running the upgrade step from version 677 to version 679.
Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.
Msg 5570, Level 23, State 3, Line 1
FILESTREAM Failed to find the garbage collection table.
Filestream is not enabled on the source server or the server I am restoring to. Is there anything I can do to restore this successfully or does this look like a bug? thanks.
May 8, 2014 at 11:47 am
May 8, 2014 at 11:54 am
@SQLFRNDZ (5/8/2014)
Master database has a set of restrictions when moving from one version to another version, the standard rule is Master can be restored to same version and also more important is the same build number too.
He isn't restoring to master though, does that restriction still hold if he's restoring to 'masttest'?
May 8, 2014 at 12:08 pm
May 8, 2014 at 12:22 pm
yeah this is purely to test the backups and I only ever had issues previously restoring master from 2000 to a higher version (error: here is already an object named 'sysnsobjs' in the database). This looks to be an issue with 2008 R2 master backup to a higher major version. I had previously had the restore occurring a SQL 2008 R2 instance and different SP/CU builds were not an issue.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply