Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
PingTheServer
Starting Member
28 Posts |
 Posted - 2008-10-03 : 10:29:16
|
| We have a SQL 2k5 running on Win 2k3x64, which is only for development right now. We are about to rework our DR plan and I had some questions I thought you guys might be better able to answer than I am. Looking for suggestions on what you would like to do for a DRP.Our SQL for dev is going to remain for dev, and we are going to have a new HP proliant with a number of HD's for raid. We are going to use Backup Exec and I was reading about their baremetal restore capabilities. My concern is that if we have a spare server (not a server with huge storage, just a few drives), and I try to do a baremetal restore from the SQL with all the various drives with logs/indexes/data on different ones, am I correct in assuming the locations of those files would be mismatched when restored to the new server with fewer physical drives? The SQL server is going to be a HP Proliant - something new idk which specific model, with an attached 10 drives. We only do a few thousand transactions a day, transactions stopping at 5:00, nothing on the weekends. Is trying to do a baremetal restore with a daily full backup plausable given the number of physical and logical drives that will be in a raid? Would it be better to purchase two identical servers? Is there a Backup Exec for SQL feature that is better than what is built in to 2k5? What would you guys do, ideally, in my situation...as this is my first DRP for SQL. |
|
|
lepeniotis
Yak Posting Veteran
75 Posts |
Posted - 2008-10-03 : 10:49:16
|
| What I do and what I would suggest is to have DRP for the databases by using a Full recovery model (full backup, differencial back up and log backups) if it is needed according to the databases and their usage. If something happen restore the db in the specific point in time. Then these backup files back them up in a tape or somewhere to be sure that you will not lose them whatever happens.Thats what I do thats what I suggest.?I hope that I helped!RegardsMSc Advanced Computing Science MSc Database ProfessionalSheffield Hallam UniversityMCP (70-229, 70-228)Industrial IT Engineer |
 |
|
|
PingTheServer
Starting Member
28 Posts |
Posted - 2008-10-03 : 11:56:26
|
| I guess the jest of what I dont understand is what will happen to the indexes/data/logs that are all pointing to different drives when moving or restoring to a different computer.Say I have indexes on drive I, data on drive D and E, logs on drive L. Disaster happens, I need to get it online somehow and cannot wait for replacement parts. When I restore to a server without that many physical or logical drives, is SQL going to throw up because the drives it needs are not available...or is it smart enough to recognize something happened and send them all to a default location? |
|
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-10-03 : 12:08:46
|
| While restoring you can specify where you want your files to go depending on configuration of new drives you have on new server? It gets same drive letter from previous server, but you gotta change it to present configuration. |
|
|
|
|
|
|
|
|
Disaster Recovery/Backup with baremetal?