SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


How to handle the resource database during DR


How to handle the resource database during DR

Author
Message
Brian Brown-204626
Brian Brown-204626
Say Hey Kid
Say Hey Kid (689 reputation)Say Hey Kid (689 reputation)Say Hey Kid (689 reputation)Say Hey Kid (689 reputation)Say Hey Kid (689 reputation)Say Hey Kid (689 reputation)Say Hey Kid (689 reputation)Say Hey Kid (689 reputation)

Group: General Forum Members
Points: 689 Visits: 297
I have been tasked with updating our DR documentation, which has gotten woefully out of
date. My only question concerns the resource database. In SQL Server 2005, it was among the
system databases and had to remain in the same location as the master database. In SQL Server
2008, it was moved to the bin folder in the SQL Server install directory.

Am I correct in assuming that the resource database contains only objects, but no data? If this
is so, can I safely ignore this database for purposes of DR, as long as my DR server is at the same
release level(service pack, CU, etc.) as my production server? If I must account for the resource
database, how do I go about it. I know I cannot backup the database, but must copy the data
and log files, but do I need to shutdown SQL Server before I do the copy? What order do I do the
restore? Do I restore the master database first, then the resource database, or do I restore the
resource database first, then the master?
GilaMonster
GilaMonster
SSC Guru
SSC Guru (234K reputation)SSC Guru (234K reputation)SSC Guru (234K reputation)SSC Guru (234K reputation)SSC Guru (234K reputation)SSC Guru (234K reputation)SSC Guru (234K reputation)SSC Guru (234K reputation)

Group: General Forum Members
Points: 234315 Visits: 46368
In 2008 it should be treated just as if it were a dll, a library file for SQL Server.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


george sibbald
george sibbald
One Orange Chip
One Orange Chip (25K reputation)One Orange Chip (25K reputation)One Orange Chip (25K reputation)One Orange Chip (25K reputation)One Orange Chip (25K reputation)One Orange Chip (25K reputation)One Orange Chip (25K reputation)One Orange Chip (25K reputation)

Group: General Forum Members
Points: 25728 Visits: 13701
As long as the two servers are the exact same version the resource databases are interchangeable as it contains system objects only and does not change except when upgrades are performed.

to copy the resource database files SQL must be down. I would make a copy of them each time I do an upgrade (and the other system database files), so I have a copy available in case off corruption. If you want this to go off to tape you may have to change the suffix of the copies as a lot of tape copy software ignores database files (.mdf,.ndf and .ldf).

As your DR server is a different server I cannot imagine your DR process would include recovering the resource database. If you are in a situation where you have to do this you would be using the rebuild process which would recover the resource database for you and then you would restore your system db backups.

Restoring system databases to another server is not normally the best way to go, especially for the msdb databases.

---------------------------------------------------------------------
Brian Brown-204626
Brian Brown-204626
Say Hey Kid
Say Hey Kid (689 reputation)Say Hey Kid (689 reputation)Say Hey Kid (689 reputation)Say Hey Kid (689 reputation)Say Hey Kid (689 reputation)Say Hey Kid (689 reputation)Say Hey Kid (689 reputation)Say Hey Kid (689 reputation)

Group: General Forum Members
Points: 689 Visits: 297
The only reason we restore the system databases is that our DR server is cold, i.e. SQL Server is installed and patched, but nothing more. No user databases, no jobs, no logins, etc.
george sibbald
george sibbald
One Orange Chip
One Orange Chip (25K reputation)One Orange Chip (25K reputation)One Orange Chip (25K reputation)One Orange Chip (25K reputation)One Orange Chip (25K reputation)One Orange Chip (25K reputation)One Orange Chip (25K reputation)One Orange Chip (25K reputation)

Group: General Forum Members
Points: 25728 Visits: 13701
If all you have is logins and jobs you would be better off scripting them out and loading them in.

Maintenance plans do not transfer well to another server, in fact they dont transfer at all.

Ideally you would be copying and restoring your user databases to your DR server on a regular basis.

Provocative statement - MSSQL is WAAAY too tied to the server it was installed on and does not migrate well. Bear that in mind when developing your DR strategy.

---------------------------------------------------------------------
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search