June 29, 2011 at 3:27 pm
Hello.
I'm quite new to sql server and have limited knowledge but this looks like a good place to up my knowledge.
I started supporting an existing Fujitsu Econel 100 server with SBS 2003 installed last year. This had been configured for the company to store all their office documents on the companyweb. This had been working fine until the electrical storms came to England yesterday, something happened to the server and has blown the motherboard. Thus we can no longer boot into the os. We had it setup with a raid 1 configuration so it is possible to access the drives and I have the sbs backup from the night before.
How would I go about getting the sql database and restoring it to a different server so i can get their needed documents out and pop them onto a usb drive to get my customer up and working until I can get a new server in there?
Thanks in advance - Adam
June 29, 2011 at 3:33 pm
Where are your backups of those dbs? That would be by far the easiest route to take.
June 29, 2011 at 3:41 pm
I can get a backup of the dbs from the program files/sql server/data folder or do you mean the ntbackup?
I have that on a network storage device which can be accessed, it has the .bkf file.
Thanks for your quick response.
June 29, 2011 at 3:47 pm
No I mean did you take daily full backups of the dbs using either sql agent or backup exec or anything else similar?
There are applications that can take full server backups which include the db files but those apps are few and far in between.
June 29, 2011 at 3:52 pm
Adam Hills (6/29/2011)
I can get a backup of the dbs from the program files/sql server/data folder or do you mean the ntbackup?I have that on a network storage device which can be accessed, it has the .bkf file.
Thanks for your quick response.
This sounds like you only have the core mdf/ldf files to work from, and not the actual database backups. I'll be honest I don't know what SBS does, but it's unfamiliar to me. Look for some files with like <databasename>.bak, usually somewhere down a filepath with '/backup/' included. Those are what you're looking for if it was setup as default. That'll let you restore to another machine the easiest.
If you only have the mdf/ldfs to work with, you're in a recovery scenario and I'll see if I can find you some good walkthrough links.
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
June 29, 2011 at 3:58 pm
Unfortunately, we haven't got any backup agents/programs installed, so Craig is correct. I'll take a log at the drive tomorrow and let you know if I can find the /backup folder.
Thanks
June 29, 2011 at 4:06 pm
Adam Hills (6/29/2011)
Unfortunately, we haven't got any backup agents/programs installed, so Craig is correct. I'll take a log at the drive tomorrow and let you know if I can find the /backup folder.Thanks
You can setup the internal agent on SQL Server to do that maintenance for you and I'm hoping for your sanity that this was done so you can recover easier. If not, prepare for an interesting ride.
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
June 30, 2011 at 1:14 am
I've scanned the hdd for any files of .bak and can't find any that relate to the servername etc.
Looks like i'm in for an interesting ride.....
July 1, 2011 at 3:26 am
If you only have the mdf/ldfs to work with, you're in a recovery scenario and I'll see if I can find you some good walkthrough links.
This looks like it's all I have to work with, I don't suppose you have any walkthroughs as mentioned?
Thanks - Adam.
July 1, 2011 at 7:15 am
Some basics to get you started:
1. Install MSSQL Server on a new physical server, or you may already have an existing server/instance that you can use.
2. Copy the MDF and LDF files from the crashed server to the new server. Place these files in the directory/directories where you want the database files.
3. ATTACH the database and create the necessary logins/users on the new instance
(see Books online for detach/attach)
4. Perform a FULL backup and save this file on another server/device for disaster recovery.
July 1, 2011 at 3:45 pm
Adam Hills (7/1/2011)
If you only have the mdf/ldfs to work with, you're in a recovery scenario and I'll see if I can find you some good walkthrough links.
This looks like it's all I have to work with, I don't suppose you have any walkthroughs as mentioned?
Thanks - Adam.
Sorry Adam, been a long few days and I couldn't find the post I was looking to find for a bit.
The first trick is simply to bring the files over to the new server, and try doing a database attach. You can try this from the GUI. EDIT: As Steve mentioned above... 🙂
If that fails, you're looking at recovery. When you're dealing with recovery, always go to the master:
That blog will go over at the beginning all the reasons it doesn't want to work, and then near the end you'll see a 'fixing the database' section which is what you'll need to do if a simple attach won't function.
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
August 24, 2023 at 12:31 pm
This was removed by the editor as SPAM
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply