June 10, 2015 at 3:04 pm
So my scenario is this: I'm practicing migrating to a new server, simulating what I might have to do if my existing hardware was destroyed and I sit down in front of a new machine with only my backups.
I install SQL on the new machine, get the service packs up to the same version as what I'm attempting to restore.
Restart in single user mode.
Restore master.
Try bringing it up, get some tempdb/model issues. Ok, restart with -T3608 and -T3609, and attempt to restore model.
I get this:
13 percent processed.
22 percent processed.
31 percent processed.
40 percent processed.
54 percent processed.
63 percent processed.
72 percent processed.
81 percent processed.
90 percent processed.
100 percent processed.
Processed 176 pages for database 'model', file 'modeldev' on file 1.
Processed 1 pages for database 'model', file 'modellog' on file 1.
Msg 3283, Level 16, State 1, Line 1
The file "modellog" failed to initialize correctly. Examine the error logs for more details.
Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.
I also see this on my cmd window, where I've started SQL:
2015-06-10 16:01:22.79 spid51 Starting up database 'tempdb'.
2015-06-10 16:01:22.79 spid51 Error: 17204, Severity: 16, State: 1.
2015-06-10 16:01:22.79 spid51 FCB::Open failed: Could not open file E:\Temp
DB\Data\tempdb.mdf for file number 1. OS error: 2(The system cannot find the fi
le specified.).
2015-06-10 16:56:48.39 spid51 Starting up database 'model'.
2015-06-10 16:56:48.44 spid51 The database 'model' is marked RESTORING and
is in a state that does not allow recovery to be run.
2015-06-10 16:56:49.04 spid51 Starting up database 'model'.
2015-06-10 16:56:49.07 spid51 The database 'model' is marked RESTORING and
is in a state that does not allow recovery to be run.
2015-06-10 16:56:49.08 Backup Error: 3283, Severity: 16, State: 1.
2015-06-10 16:56:49.08 Backup The file "modellog" failed to initialize corr
ectly. Examine the error logs for more details.
I've tried fresh model backups, in case there was corruption, but they all do the same thing.
Am I going about this wrong? Any ideas?
Also, full disclosure, the OS is different (Win 2012, instead of 2008 R2), and my paths are different. But I'm trying to simulate the real world, where I may not have time or control to make every single variable match. And I feel like these issues shouldn't be caused by those different variables anyway. I've tried altering tempdb and model's paths to existing locations and then restoring, and there's no difference.
June 11, 2015 at 3:46 am
Do you really need to restore the model database? Does the instance start ok with the model db creating at install?
Follow me on twitter @EvoDBACheck out my blog Natural Selection DBA[/url]
June 11, 2015 at 10:13 am
I think I need model, unless I'm missing something else, because on restart after the master restore, I get errors related to tempDB and model.
I'll get some more specifics later, but I just noticed what I hope is the root of my problem -- on the target server, I have SQL standard, and the source server is enterprise.
I'll be annoyed, but happy, if this is the source of my issue, but I would have expected a more clear message like "You're restoring to the wrong edition, dummy!"
June 11, 2015 at 11:37 am
You need a model database there as the instance creates tempdb from that model, bit so long as you have the .MDF and .ldf for model in the location specified in your master database then I think it should start up OK.
Follow me on twitter @EvoDBACheck out my blog Natural Selection DBA[/url]
June 11, 2015 at 3:05 pm
My problem was indeed the edition difference. Rebuilt target box as enterprise, and everything went mostly smooth.
I didn't have to restore model, just alter the location to where the new path was on the target server. Did the same for tempDB, bounced the instance, then restored MSDB and I was ready to tackle the user DBs.
Thanks!
June 11, 2015 at 3:33 pm
Good to know, glad you got to the bottom of it!
Follow me on twitter @EvoDBACheck out my blog Natural Selection DBA[/url]
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply