Restore SQL Server Express Databases After A Disaster Recovery
Sep 15, 2006
Hello,
I would like to restore SQL Server Express and its databases from a tape backup to the same server. This is a disaster recovery senario.
I backed up the Master, Model, MSDB and my own test database using SQLCMD scripts. I have no problem restoring these using task manager on the server before the disaster recovery.
However, in my real disaster recovery testing, When the server is restored by tape drive (HP one button disaster recovery), I try to run my SQLCMD restore scripts in task manager and I cannot connect to the sql server. Also I cannot connect with Management studio. I have recieved the following error in event viewer.
Event Type: Warning
Event Source: SQLBrowser
Event Category: None
Event ID: 3
Date: 9/15/2006
Time: 8:16:36 AM
User: N/A
Computer: COPLEYNEWS
Description:
The configuration of the AdminConnectionTCP protocol in the SQL instance SQLEXPRESS is not valid.
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7024
Date: 9/15/2006
Time: 8:16:36 AM
User: N/A
Computer: COPLEYNEWS
Description:
The SQL Server (SQLEXPRESS) service terminated with service-specific error 3411.
C:Program FilesMicrosoft SQL Server90ToolsBinn>sqlcmd -S.SQLExpr
COPLEYNEWSDATABASEscriptsMASTERFULLRESTORE.sql"
HResult 0x2, Level 16, State 1
Named Pipes Provider: Could not open a connection to SQL Server [2].
Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred whi
shing a connection to the server. When connecting to SQL Server 2005,
re may be caused by the fact that under the default settings SQL Serve
allow remote connections..
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
My question is, what is the correct procedure to follow when I want to do a disaster recovery and restore SQL Server Express from tape backup using the Simple Backup method and scripts.
Is it always required to reinstall sql server express from the original program file or is it possible to reinstall from back up tape.
I know my backup and restore scripts work because I tested them on the server before I do the disaster recovery and rebuild that server from tape.
This is some kind of issue with SQL Server Express being restored by tape backup.
We have a requirement to build SQL environment which will give us local high availability and disaster recovery to second site. We have two sites- Site A & Site B. We are planning to have two nodes at Site A and 2 nodes at Site B. All four nodes will be part of same Windows failover cluster. We will build two SQL Cluster, InstanceA will be clustered between the nodes at Site A Server and InstanceB will be clustered between the nodes at Site B, we will enable Always On Between the InstanceA and InstanceB and will be primary owner where data will be written on InstanceA and will be replicated to InstaceB. URL....Now we want we will have instanceC on the Site B and data will be writen from the application available on Site B, will be replicated to the instance on the Site A as replica.
Recently I watched Microsoft Support WebCast: Microsoft SQL Server 7.0 Common Problems and Resolutions dated August 29, 2000. I am trying to find information for a total disaster recovery for my server. In the webcast the presenter made a reference to a Microsoft article Q240872, "How to Resolve Permission Issues When a Database is Moved Between SQL Servers?". I can't find this article. Since we are working with the scenerio of total diaster, we are starting with a new server. I know that when we tried to recover a database to a new server, the server recognized that the database did not originate on that server. Does anyone have any ideas? Or does anyone know how to contact Microsoft so I can find out how to get a copy of this article? Thanks!
I am part of a team developing a Disaster Recovery plan for our company, most of the data is in SQL Server 2000, and Visual Foxpro, what are the best options of backing up this data to one remote site, and being able to failover to those servers in case of a disaster.
I need to know if anybody has any suggestions on websites to visits, documents or templates that will give examples on how to set up a Disaster Recovery Plan for SQL Server 7.0 Databases. I am mostly interested in the Documentation portion to acquire knowledge on the various methodologies used out there. I am a Jr DBA and would appreciate any feedback. Thanks.
We have 10 SSIS packages which are deployed on 2 servers. (at different geographical locations)
On both the servers we will install all the 10 packages, but on server1 we will enable 1 - 5 and server2 we will enable 6 to 10.
the idea is that if server1 goes down we enable all the 10 on server2 (and vise-versa).
Is this the best way to implement disaster recovery of SSIS packages? We want that in all cases of failure the SSIS packages are ready to process the ETL: tasks.
Is it possible to setup a Disaster Recovery server for Reporting services (Databases: ReportServer and ReportServerTempDB)? If so, will loading these 2 databases (Log shipping) allow to me access the same reports as in Production server. Is there anything which I have to do on DR Server when the Production site is down?
I currently work for a company that has had a "family business" mentality for many years. The only trouble is, it has grown into a fairly large company over the years and that mentality just doesn't cut it anymore (We have around 200 employees in 2 offices, and 25-50 remote users).
I have recently taken over the role of System Administrator, and I'm having a lot of trouble trying to get everything under wraps. There are a LOT of un-documented things happening with our database/web server, and in order to keep things safe & secure, I need to try & flesh out what those mystery settings would be. I feel that NOW is the time to get some solid documentation down, to protect my ass before some critical failure happens.
I'm wading into unknown waters here, and I'm hoping that somebody who's "been there" might have some tips to make my life a little easier.
I have an IBM Bladecenter, and a spare blade with which I can use to re-produce as close to a mirror copy of our system as possible. I have installed windows 2003 /w SQL2000 and restored a full backup of our databases and imported all database user accounts, and logins. What about Maintenance Jobs? Error Logs? Patches/Hotfixes? Service accounts? Membership roles? System databases? ODBC Sources? Services? Startup Scripts? I'm sure the list could go on & on... What are some of the crucial details I should look into?
Has anybody been in this boat before having little knowledge of what was built before you arrived, and have any insight on how to get through this without too much headache?
I'm trying to find any useful whitepapers about how to effectively build and operate a disaster recovery site at a remote location for SQL Server 2000. Does anyone know where to find such information?
I also know that one good option for my customer is using the Mirroring feature of SQL Server 2005. What are the other options? Is Replication an effective one for a mission-critical database (online banking)?
If you are doing a disaster recovery of an entire SQL 2005 cluster, can you just install SQL server and restore the system database to get the configuration?
I have a problem. I am trying to set up a disaster recovery plan and have ran into some problems. Just so you are aware, we have tried setting up replication but it failed since the database does not have primary keys(don't ask--I have no control) and we have tried to set up log shipping but we do not have the Enterprise version of SQL server so that won't work. The database is over 200GB so shipping by tape or transferring full backups across the wire is impractical. So basically my question is - "What other options can we explore for setting up disaster recovery that do not involve 'substantial' expenditures?"
There is a direct connection set up between the off site data store.
Hi, A test server I was developing on has died and all of my good work was on it. However I have a copy of the Data folder containing the folloing files:
Test_Data.MDF
Test_Log.LDF
Is it possible to restore my database from these files? If so how would I go about it?
I'm looking for something beyond trying to recover databases and/or SQLServer. My group has been tasked with documenting the recovery for 30+ servers that make up our applications infrastructure including SQL, Web, etc. I posted this here as opposed to another forum because I couldn't even find disaster recovery related topics in the other forums.
Our Systems group (Lan, Wan, etc.) isn't really much help at all. Their focus is more on the mainframe and Novell network recovery. Their perspective is that they will get any replacement server back on line in the event of failure but we are on our own from there.
There are three disaster scenarios for which we must plan: 1) A 737 does a nose dive into the Data Center. 2) A hurricane floods the Data Center. 3) A server gets smoked for whatever reason and is no longer useable.
Assume... - that there were enough survivors to rebuild the network infrastructure at a remote site.
- we have to recover the operating system, additional software, IIS, SQL, applications, etc.
Questions: What's the best way to capture the server's configuration on an automated basis?
What's the best way to recover the configuration mentioned above?
How do you maintain a current snapshot of any particular server and how do you ensure there's a documented history of the changes?
Does anybody use a centralized backup system? OmniBack, BackupExec?
What's the best/fastest way to get the replacement equipment?
Where else can I look to find this information?
Have I asked all the questions that I should or can you think of one I've missed?
Yikes! I lost my autoloader bakcup device along with my SQL2K Server. I reinstalled Win2k and now can see my RAID partitions where I had SQL server installed, along with all of the files. Since my tape backup is dead, I cannot simply restore from media. I'd like to reinstall SQL Server and then somehow grab the files on the partition and restore all of the data back to where things were. Is this even possible? If so, could someone help me out? I am worried by reading this list that my primary application (Sharepoint) will not be able to be restored because of security issues. Any ideas on that?
I am planning to create a disaster recovery site for my production database server. But I am not able to identify which option to choose. Not sure if I should go with database mirroring or transactional replication.
What are the pros and cons of each option?
Production and disaster recovery site location will be geographically very far.
please help
Regards, S
Don't sit back because of failure. It will come back to check if you still available. -- Binu
I'm looking for a proven method and documenation on recovering a publisher that is also the distributor. I have had problems with subscribers failing and database corruption on subscribtion databases. I do not have any documentation or experience in recovering a publisher that also is it's own distributor. Please point me in the right direction for this and any in house documentation that may not be published to the public would be great.
I used to have WSS 3.0 Beta version, to update that to B2TR i got a problem and for which i require to reinstall the WSS again. Now I have the old WSS_Content.mdf and WSS_Content.ldf. I want this old site content tranfer to the current one.
How can I restore the data of this Site Content Database to the new one which I have newly created.
Backup : Full and Transaction log. Hardware : Clustering, RAID
I am not sure about what all need to be Scripted for having a good disaster recovery plan?? Scripting:: tables, views, defaults, rules, users, roles, permissions Backup : Triggers, Stored Procedures
Hi, Im going to set up a disaster recovery plan for SQL-servers at my company. Does anyone know where to find a template for this ? Something to help me that describes what you must write down and so on ?
Please email me besides answering at discussion board.
We have the following situation. Box A is publisher & Box B is a DR box that is a subscriber to Box A keeping it in line with Box A. If Box A goes down Box B then becomes the 'live' box. I assume I have to do nothing to Box B to allow this to happen but if I'm wrong please let me know. My question is :- Once Box A is back online how do I get the data from Box B onto Box A so that Box A can be made the 'live' box again?
"Site A" SQL 7.0 Cluster with Drives on Shared Storage. "Site B" SQL Server Cluster with Drives on Shared Storage Both Configured as Active/Active (8+ databases <100GB total)
How can I get the DB's (all) from Site A and allow a DIFFERNET cluster to control them.
Basically, I want to move all DB's from "Site A" and bring them into "Site B" with all relevant data ..ie master DB etc . I have a time window of 90 Mins and I cannot lose one single piece of data.........( I need to lie down now) Help would be apprecitated)
Can any one please share the sample disaster recovery plan. I dont know what I have to include in it and how to prepare it. Your help will be highly appreciated. Thanks in advance...
Would appreciate if anyone can advice me about disaster recovery plan for SSRS.
I am going to build one report server with Windows 2003 Enterprise x64 + SQL 2005 Enterprise x64 with Reporting Service, all in one box. The remote report data source is on another SQL 2000 server.
If the report server has failed, what option do I have to continue reporting services? I am not worry about the remote report data source as it is backup regularly.
I am a newbie to SQL admin. I have been given a responsibility to document a) Backup, recovery and disaster plan
Can some one give me poninters where I would start???. Please let me know if you can suggest any sites for new DBA's and also where I would find out about what to document, etc??. Thanx for your time
Hi, I want to setup disaster recovery site for small databases from disffrent data centre.Which method would be good and from where I will get some good stuffs to read except online documents?
we are trying to simulate a disater recovery of our SQL2000 and SQL2005 development servers. Which is the order in which we should restore the DBs. I am talking specifically of MSDB, master and user DBs; should we restore user DBs before master and MSDB?
I have a client with no backup of MASTERdb or Help_rev_devices, all I have is a couple of .dmp's of the production data. In order to run DISK REINIT I need to know the size of the database, is there any way of finding out the size of the database device, if all you have to go with is a backup dump file?
