database problem: recovery

Showing posts with label recovery. Show all posts

Monday, March 26, 2012

Thank you, the database was restored. Now I have another problem. I restored the master database to a disaster recovery server and the database names are different. How do I Point the master DB to the new databases?
"Steve" <anonymous@.discussions.microsoft.com> wrote in message
news:9A89A18C-6F95-4066-B08E-3D5657CDF85B@.microsoft.com...
> Thank you, the database was restored. Now I have another problem. I
restored the master database to a disaster recovery server and the database
names are different. How do I Point the master DB to the new databases?
EXEC sp_attach_db or sp_attach_single_file_db
e.g.
EXEC sp_attach_db @.dbname = N'pubs',
@.filename1 = N'c:\Program Files\Microsoft SQL
Server\MSSQL\Data\pubs.mdf',
@.filename2 = N'c:\Program Files\Microsoft SQL
Server\MSSQL\Data\pubs_log.ldf'
EXEC sp_attach_single_file_db @.dbname = 'pubs',
@.physname = 'c:\Program Files\Microsoft SQL Server\MSSQL\Data\pubs.mdf'
--Outgoing mail is certified Virus Free.Checked by AVG anti-virus system
(http://www.grisoft.com).Version: 6.0.647 / Virus Database: 414 - Release
Date: 29/03/2004

Restoring the master database

Hello,
I am going throught my disaster recovery. I am at the point where I have a
nightly databases backup and I am backing up the transaction logs frequently
during the day.
I am having the problem that i am trying to restore the backedup master
database, but every time I restore it, I cannot get SQL to run again, so I
have to re-build the master database. I have tried doing it with Enterprise
manager and with Querry analizer, in both cases I get the message 'master
database succesfully recover and then it is shutting donw the service right
away, at this point I cannot re-start the service, am I missing something?
Please help
Joe HernandezMy guess is that the master database you have restored specifies that tempdb and/or model should be
located on some other place compared to where they are on your restored system.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Joe Hernandez" <JoeHernandez@.discussions.microsoft.com> wrote in message
news:046BF402-C476-4489-9773-15DB290E4FC9@.microsoft.com...
> Hello,
> I am going throught my disaster recovery. I am at the point where I have a
> nightly databases backup and I am backing up the transaction logs frequently
> during the day.
> I am having the problem that i am trying to restore the backedup master
> database, but every time I restore it, I cannot get SQL to run again, so I
> have to re-build the master database. I have tried doing it with Enterprise
> manager and with Querry analizer, in both cases I get the message 'master
> database succesfully recover and then it is shutting donw the service right
> away, at this point I cannot re-start the service, am I missing something?
> Please help
> Joe Hernandez|||Please look at the error log , what error you found in it?
Regards
Amish|||Hello,
I am very new at SQL, can you tell me how to look up the error log?
"amish" wrote:
> Please look at the error log , what error you found in it?
> Regards
> Amish
>|||I dont know how would I tell that.
So do I need to restore the tempdb and the model before I restore the
masterdb?
thanks,
Joe H
"Tibor Karaszi" wrote:
> My guess is that the master database you have restored specifies that tempdb and/or model should be
> located on some other place compared to where they are on your restored system.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Joe Hernandez" <JoeHernandez@.discussions.microsoft.com> wrote in message
> news:046BF402-C476-4489-9773-15DB290E4FC9@.microsoft.com...
> > Hello,
> >
> > I am going throught my disaster recovery. I am at the point where I have a
> > nightly databases backup and I am backing up the transaction logs frequently
> > during the day.
> >
> > I am having the problem that i am trying to restore the backedup master
> > database, but every time I restore it, I cannot get SQL to run again, so I
> > have to re-build the master database. I have tried doing it with Enterprise
> > manager and with Querry analizer, in both cases I get the message 'master
> > database succesfully recover and then it is shutting donw the service right
> > away, at this point I cannot re-start the service, am I missing something?
> >
> > Please help
> >
> > Joe Hernandez
>|||Check sysdatabases on the old installation for the original path for those databases. Or the
errorlog file. You can then create a directory as the original and have copy the files of those
databases so that they exist in the original location. Then use KB 224071 to move those databases to
the desired location. Some articles that might be helpful:
Have a look at this list compiled by Andrew Kelly:
Moving DB's between Servers
http://www.support.microsoft.com/?id=314546
Moving SQL Server Databases to a New Location with Detach/Attach
http://www.support.microsoft.com/?id=224071
Using WITH MOVE in a Restore
http://support.microsoft.com/?id=221465
How To Transfer Logins and Passwords Between SQL Servers
http://www.support.microsoft.com/?id=246133
Mapping Logins & SIDs after a Restore
http://www.support.microsoft.com/?id=298897
Utility to map logins to users
http://www.dbmaint.com/SyncSql Logins.asp
User Logon and/or Permission Errors After Restoring Dump
http://www.support.microsoft.com/?id=168001
How to Resolve Permission Issues When a Database Is Moved Between SQL
Servers
http://www.support.microsoft.com/?id=240872
Restoring a .mdf
http://www.sqlservercentral.com/scripts/scriptdetails.asp?scriptid=599
Disaster Recovery Articles for SQL Server
http://www.support.microsoft.com/?id=307775
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Joe Hernandez" <JoeHernandez@.discussions.microsoft.com> wrote in message
news:6F9B255A-7822-4B8D-976C-1C04E44E2374@.microsoft.com...
>I dont know how would I tell that.
> So do I need to restore the tempdb and the model before I restore the
> masterdb?
> thanks,
> Joe H
> "Tibor Karaszi" wrote:
>> My guess is that the master database you have restored specifies that tempdb and/or model should
>> be
>> located on some other place compared to where they are on your restored system.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "Joe Hernandez" <JoeHernandez@.discussions.microsoft.com> wrote in message
>> news:046BF402-C476-4489-9773-15DB290E4FC9@.microsoft.com...
>> > Hello,
>> >
>> > I am going throught my disaster recovery. I am at the point where I have a
>> > nightly databases backup and I am backing up the transaction logs frequently
>> > during the day.
>> >
>> > I am having the problem that i am trying to restore the backedup master
>> > database, but every time I restore it, I cannot get SQL to run again, so I
>> > have to re-build the master database. I have tried doing it with Enterprise
>> > manager and with Querry analizer, in both cases I get the message 'master
>> > database succesfully recover and then it is shutting donw the service right
>> > away, at this point I cannot re-start the service, am I missing something?
>> >
>> > Please help
>> >
>> > Joe Hernandez
>>|||Tibor,
Thanks for all your help.
Do you know if it makes a difference if I am using 2 different instaces
names? should I have the same instance name on my production server as well
as my test server?
Thanks,
Joe Hernandez
"Tibor Karaszi" wrote:
> Check sysdatabases on the old installation for the original path for those databases. Or the
> errorlog file. You can then create a directory as the original and have copy the files of those
> databases so that they exist in the original location. Then use KB 224071 to move those databases to
> the desired location. Some articles that might be helpful:
> Have a look at this list compiled by Andrew Kelly:
> Moving DB's between Servers
> http://www.support.microsoft.com/?id=314546
> Moving SQL Server Databases to a New Location with Detach/Attach
> http://www.support.microsoft.com/?id=224071
> Using WITH MOVE in a Restore
> http://support.microsoft.com/?id=221465
> How To Transfer Logins and Passwords Between SQL Servers
> http://www.support.microsoft.com/?id=246133
> Mapping Logins & SIDs after a Restore
> http://www.support.microsoft.com/?id=298897
> Utility to map logins to users
> http://www.dbmaint.com/SyncSql Logins.asp
> User Logon and/or Permission Errors After Restoring Dump
> http://www.support.microsoft.com/?id=168001
> How to Resolve Permission Issues When a Database Is Moved Between SQL
> Servers
> http://www.support.microsoft.com/?id=240872
> Restoring a .mdf
> http://www.sqlservercentral.com/scripts/scriptdetails.asp?scriptid=599
> Disaster Recovery Articles for SQL Server
> http://www.support.microsoft.com/?id=307775
>
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Joe Hernandez" <JoeHernandez@.discussions.microsoft.com> wrote in message
> news:6F9B255A-7822-4B8D-976C-1C04E44E2374@.microsoft.com...
> >I dont know how would I tell that.
> >
> > So do I need to restore the tempdb and the model before I restore the
> > masterdb?
> >
> > thanks,
> >
> > Joe H
> >
> > "Tibor Karaszi" wrote:
> >
> >> My guess is that the master database you have restored specifies that tempdb and/or model should
> >> be
> >> located on some other place compared to where they are on your restored system.
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://www.solidqualitylearning.com/
> >> Blog: http://solidqualitylearning.com/blogs/tibor/
> >>
> >>
> >> "Joe Hernandez" <JoeHernandez@.discussions.microsoft.com> wrote in message
> >> news:046BF402-C476-4489-9773-15DB290E4FC9@.microsoft.com...
> >> > Hello,
> >> >
> >> > I am going throught my disaster recovery. I am at the point where I have a
> >> > nightly databases backup and I am backing up the transaction logs frequently
> >> > during the day.
> >> >
> >> > I am having the problem that i am trying to restore the backedup master
> >> > database, but every time I restore it, I cannot get SQL to run again, so I
> >> > have to re-build the master database. I have tried doing it with Enterprise
> >> > manager and with Querry analizer, in both cases I get the message 'master
> >> > database succesfully recover and then it is shutting donw the service right
> >> > away, at this point I cannot re-start the service, am I missing something?
> >> >
> >> > Please help
> >> >
> >> > Joe Hernandez
> >>
> >>
>|||For 2000, the instance name is part for the directory structure for SQL Server. So, it will probably
be easier of you have the same instance name, more likely that you will have the same directory
structure.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Joe Hernandez" <JoeHernandez@.discussions.microsoft.com> wrote in message
news:0C55B74D-03E2-4A73-BAD4-FA8E72BA27EE@.microsoft.com...
> Tibor,
> Thanks for all your help.
> Do you know if it makes a difference if I am using 2 different instaces
> names? should I have the same instance name on my production server as well
> as my test server?
> Thanks,
> Joe Hernandez
> "Tibor Karaszi" wrote:
>> Check sysdatabases on the old installation for the original path for those databases. Or the
>> errorlog file. You can then create a directory as the original and have copy the files of those
>> databases so that they exist in the original location. Then use KB 224071 to move those databases
>> to
>> the desired location. Some articles that might be helpful:
>> Have a look at this list compiled by Andrew Kelly:
>> Moving DB's between Servers
>> http://www.support.microsoft.com/?id=314546
>> Moving SQL Server Databases to a New Location with Detach/Attach
>> http://www.support.microsoft.com/?id=224071
>> Using WITH MOVE in a Restore
>> http://support.microsoft.com/?id=221465
>> How To Transfer Logins and Passwords Between SQL Servers
>> http://www.support.microsoft.com/?id=246133
>> Mapping Logins & SIDs after a Restore
>> http://www.support.microsoft.com/?id=298897
>> Utility to map logins to users
>> http://www.dbmaint.com/SyncSql Logins.asp
>> User Logon and/or Permission Errors After Restoring Dump
>> http://www.support.microsoft.com/?id=168001
>> How to Resolve Permission Issues When a Database Is Moved Between SQL
>> Servers
>> http://www.support.microsoft.com/?id=240872
>> Restoring a .mdf
>> http://www.sqlservercentral.com/scripts/scriptdetails.asp?scriptid=599
>> Disaster Recovery Articles for SQL Server
>> http://www.support.microsoft.com/?id=307775
>>
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "Joe Hernandez" <JoeHernandez@.discussions.microsoft.com> wrote in message
>> news:6F9B255A-7822-4B8D-976C-1C04E44E2374@.microsoft.com...
>> >I dont know how would I tell that.
>> >
>> > So do I need to restore the tempdb and the model before I restore the
>> > masterdb?
>> >
>> > thanks,
>> >
>> > Joe H
>> >
>> > "Tibor Karaszi" wrote:
>> >
>> >> My guess is that the master database you have restored specifies that tempdb and/or model
>> >> should
>> >> be
>> >> located on some other place compared to where they are on your restored system.
>> >>
>> >> --
>> >> Tibor Karaszi, SQL Server MVP
>> >> http://www.karaszi.com/sqlserver/default.asp
>> >> http://www.solidqualitylearning.com/
>> >> Blog: http://solidqualitylearning.com/blogs/tibor/
>> >>
>> >>
>> >> "Joe Hernandez" <JoeHernandez@.discussions.microsoft.com> wrote in message
>> >> news:046BF402-C476-4489-9773-15DB290E4FC9@.microsoft.com...
>> >> > Hello,
>> >> >
>> >> > I am going throught my disaster recovery. I am at the point where I have a
>> >> > nightly databases backup and I am backing up the transaction logs frequently
>> >> > during the day.
>> >> >
>> >> > I am having the problem that i am trying to restore the backedup master
>> >> > database, but every time I restore it, I cannot get SQL to run again, so I
>> >> > have to re-build the master database. I have tried doing it with Enterprise
>> >> > manager and with Querry analizer, in both cases I get the message 'master
>> >> > database succesfully recover and then it is shutting donw the service right
>> >> > away, at this point I cannot re-start the service, am I missing something?
>> >> >
>> >> > Please help
>> >> >
>> >> > Joe Hernandez
>> >>
>> >>
>>|||you will find it in log folder in the directory where you installed
microsoft sql server.
Open the file Errorlog in notepad. It will show you the error why sql
server not starts.
Post it here to identify the reason why Services not starting.
Regards
Amish|||Tibor,
After I changed the instance name in SQL200, I had no problems restoring the
master database and right after was able to re-start server, took it off from
single user mode, have restore all my other databases and I am running full
boat on the test server.
I want to thank you all that helped me and hope that others can benefit from
this issue.
Joe Hernandez
"Tibor Karaszi" wrote:
> For 2000, the instance name is part for the directory structure for SQL Server. So, it will probably
> be easier of you have the same instance name, more likely that you will have the same directory
> structure.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Joe Hernandez" <JoeHernandez@.discussions.microsoft.com> wrote in message
> news:0C55B74D-03E2-4A73-BAD4-FA8E72BA27EE@.microsoft.com...
> > Tibor,
> >
> > Thanks for all your help.
> >
> > Do you know if it makes a difference if I am using 2 different instaces
> > names? should I have the same instance name on my production server as well
> > as my test server?
> >
> > Thanks,
> >
> > Joe Hernandez
> >
> > "Tibor Karaszi" wrote:
> >
> >> Check sysdatabases on the old installation for the original path for those databases. Or the
> >> errorlog file. You can then create a directory as the original and have copy the files of those
> >> databases so that they exist in the original location. Then use KB 224071 to move those databases
> >> to
> >> the desired location. Some articles that might be helpful:
> >>
> >> Have a look at this list compiled by Andrew Kelly:
> >>
> >> Moving DB's between Servers
> >> http://www.support.microsoft.com/?id=314546
> >>
> >> Moving SQL Server Databases to a New Location with Detach/Attach
> >> http://www.support.microsoft.com/?id=224071
> >>
> >> Using WITH MOVE in a Restore
> >> http://support.microsoft.com/?id=221465
> >>
> >> How To Transfer Logins and Passwords Between SQL Servers
> >> http://www.support.microsoft.com/?id=246133
> >>
> >> Mapping Logins & SIDs after a Restore
> >> http://www.support.microsoft.com/?id=298897
> >>
> >> Utility to map logins to users
> >> http://www.dbmaint.com/SyncSql Logins.asp
> >>
> >> User Logon and/or Permission Errors After Restoring Dump
> >> http://www.support.microsoft.com/?id=168001
> >>
> >> How to Resolve Permission Issues When a Database Is Moved Between SQL
> >> Servers
> >> http://www.support.microsoft.com/?id=240872
> >>
> >> Restoring a .mdf
> >> http://www.sqlservercentral.com/scripts/scriptdetails.asp?scriptid=599
> >>
> >> Disaster Recovery Articles for SQL Server
> >> http://www.support.microsoft.com/?id=307775
> >>
> >>
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://www.solidqualitylearning.com/
> >> Blog: http://solidqualitylearning.com/blogs/tibor/
> >>
> >>
> >> "Joe Hernandez" <JoeHernandez@.discussions.microsoft.com> wrote in message
> >> news:6F9B255A-7822-4B8D-976C-1C04E44E2374@.microsoft.com...
> >> >I dont know how would I tell that.
> >> >
> >> > So do I need to restore the tempdb and the model before I restore the
> >> > masterdb?
> >> >
> >> > thanks,
> >> >
> >> > Joe H
> >> >
> >> > "Tibor Karaszi" wrote:
> >> >
> >> >> My guess is that the master database you have restored specifies that tempdb and/or model
> >> >> should
> >> >> be
> >> >> located on some other place compared to where they are on your restored system.
> >> >>
> >> >> --
> >> >> Tibor Karaszi, SQL Server MVP
> >> >> http://www.karaszi.com/sqlserver/default.asp
> >> >> http://www.solidqualitylearning.com/
> >> >> Blog: http://solidqualitylearning.com/blogs/tibor/
> >> >>
> >> >>
> >> >> "Joe Hernandez" <JoeHernandez@.discussions.microsoft.com> wrote in message
> >> >> news:046BF402-C476-4489-9773-15DB290E4FC9@.microsoft.com...
> >> >> > Hello,
> >> >> >
> >> >> > I am going throught my disaster recovery. I am at the point where I have a
> >> >> > nightly databases backup and I am backing up the transaction logs frequently
> >> >> > during the day.
> >> >> >
> >> >> > I am having the problem that i am trying to restore the backedup master
> >> >> > database, but every time I restore it, I cannot get SQL to run again, so I
> >> >> > have to re-build the master database. I have tried doing it with Enterprise
> >> >> > manager and with Querry analizer, in both cases I get the message 'master
> >> >> > database succesfully recover and then it is shutting donw the service right
> >> >> > away, at this point I cannot re-start the service, am I missing something?
> >> >> >
> >> >> > Please help
> >> >> >
> >> >> > Joe Hernandez
> >> >>
> >> >>
> >>
> >>
>

Restoring the master

I getting a versioning error when trying to restore the master at our
disaster recovery site? The error I'm getting is below, any information
would be appreciated!
2004-01-29 14:43:43.61 spid51 Using 'xpstar.dll' version
'2000.80.760' to execute extended stored procedure 'sp_MSgetversion'.
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!This is an informational message, net an error.
Note that once the master database restore has completed, SQL Server will
shut itself down.
Hope this helps.
Dan Guzman
SQL Server MVP
"Dave Brooks" <dbrooks@.neca.org> wrote in message
news:%2359brYq5DHA.1948@.TK2MSFTNGP12.phx.gbl...

quote:

> I getting a versioning error when trying to restore the master at our
> disaster recovery site? The error I'm getting is below, any information
> would be appreciated!
> 2004-01-29 14:43:43.61 spid51 Using 'xpstar.dll' version
> '2000.80.760' to execute extended stored procedure 'sp_MSgetversion'.
> *** Sent via Developersdex http://www.examnotes.net ***
> Don't just participate in USENET...get rewarded for it!

restoring the database

Hi,

Two of my hard drives went down yesterday. and with it went the Sql server database.The data recovery guys recovered the back up database (.bak) file.I have since reinstalled SQL Server 2000 and now when i try and restore the .bak file it says the Microsoft tape back up file set is not valid when i try and open the .bak file.

Whats the right way to add my databse to the SQl Server2000 using my .bak file and if anyone has come across the error they could help.

Thanks

LDid you apply all SPs that your old server used to have?|||what do u mean by sps|||what do u mean by sps

Stored Procedure|||It's "Service Packs", not stored procedures...how do you apply a stored procedure anyway?|||Restore the databases...which she can't do. DOH!!! :)

You should always verify your backups, especially if writing directly to tape. Any luck though after applying the service packs? Don't you guys have a DBA who can help with this?|||It's "Service Packs", not stored procedures...how do you apply a stored procedure anyway?

Yes. It should be Service Packs|||Hi Lohit,

hows was your process of restoring the backup?

Friday, March 23, 2012

Restoring sql express and databases from tape backup.

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 scheduler 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 scheduler 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: Error
Event Source: MSSQL$SQLEXPRESS
Event Category: (2)
Event ID: 3411
Date: 9/15/2006
Time: 8:16:36 AM
User: N/A
Computer: COPLEYNEWS
Description:
Configuration block version 0 is not a valid version number. SQL Server is exiting. Restore the master database or reinstall.
Data:
0000: 53 0d 00 00 15 00 00 00 S.......
0008: 16 00 00 00 43 00 4f 00 ....C.O.
0010: 50 00 4c 00 45 00 59 00 P.L.E.Y.
0018: 4e 00 45 00 57 00 53 00 N.E.W.S.
0020: 5c 00 53 00 51 00 4c 00 \.S.Q.L.
0028: 45 00 58 00 50 00 52 00 E.X.P.R.
0030: 45 00 53 00 53 00 00 00 E.S.S...
0038: 00 00 00 00 ....

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 AdminConnection\TCP 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 Files\Microsoft SQL Server\90\Tools\Binn>sqlcmd -S.\SQLExpr
COPLEYNEWSDATABASEscripts\MASTERFULLRESTORE.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.

Any suggestions, thanks.

hi,

usually you will not be able to restore system databases to a server that is not the one you took the dumps of...

you can restore on it users databases with little efforts (usually related to database users/logins mapping), but system databases should not be restored from dumps of different servers..

if this is not the case, perhaps the files related HP restore did not a good job.. I did not find lot of info about problems like that..

you can perhaps try, in order to verify the problem is not "Network" related, modifying the connection string to "(Local)\InstanceName", in order to activate a shared memory connection and not a connection under a different network protocol..

you can even check all the required newtowork protocols are enabled via the SQL Server Configuration Manager and SQL Server Surface Area Configuration...

but both these are related to

>The configuration of the AdminConnection\TCP protocol in the SQL instance SQLEXPRESS is not valid.
and
>Named Pipes Provider: Could not open a connection to SQL Server [2].

and not with the very first problem,

>Configuration block version 0 is not a valid version number...

this seems to me more .Net assembly related versus SQL related..

waiting for Mike to jump in

regards

|||

Thank you for your reply.

I guess I am wondering what other people do for disaster recovery. Is there something wrong with my disaster recovery plan?

I do a daily backup the Master, MSDB, Model, MyDatabase using simple backup and running a SQLCMD that backs up the database files Master.bak, MSDB.bak, Model.bak, and MyDatabase.bak to a different directory. This way I can have my full tape backup of my server run afterwards and back up everything (Operating System, SQLExpress, Master.bak, MSDB.bak, Model.bak, MyDatabase.bak etc.) . Then when disaster hits, I can restore my same server from last nights tape backup and then run my SQLCMD restore scripts to restore the Master.bak, MSDB.bak, Model.bak, MyDatabase.bak.

I have done many disaster recoveries from tape backup with no problems with the Operating System or any applications, except when it comes to SQL Express.

For some reason, after I follow the steps above, if I then go to open the SQL Express management studio express, I cannot connect to the server and its databases. This does'nt seem to be a settings issue unless settings are being changed behind the scenes. It does'nt make any sense to me that I would not be able restore SQL Express and its databases by tape backup. I can do it with the operating system and everything else.

Do i need to re attach the databases or something additional like that?

|||

hi,

I usually have seen total disaster recovery performed via traditional CDs..

I mean, you have all your installation media from which install the OS, all software and the like... (actually new machines as well ).. then you go on with SQL Server databases.. but "user's databases" and not system dbs as it's usually a mess to mix inter-instances system dbs..

taking a "live backup" of the folders SQL Server is running from and it's related subdirs, including data folder, is usually not safe for dbs, as this, if available to the backup sw at all, includes unclean data from the physical files.. tapes and backup sw vendors should use the appropriate apis to interface to and interact with SQL Server live databases or the result will just be a mess...

if something goes wrong, say, master.mdf gets corrupted, you just restore a corrupted master database.. and usually that means SQL Server will not be able to start at all, so you are no longer able to restore your last valid (SQL) backups.. but you are required to "rebuild" the master db.. from the installation media.. http://msdn2.microsoft.com/en-us/library/ms143269.aspx ...

(this is very hand in SQLExpress scenario as well, as, in MSDE 2000 time frame, you are out of luck as the feature was not available in the setup options, and no rebuildm.exe was shipped along with MSDE package..)

when you are done, you can then restore your user's databases as well..

but I'm still waiting for Mike to jump in for further info about you initial exception ...

reagards

|||

(cross-posting from my reply to this question in the SQL Disaster Recovery forum http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=744&SiteID=1 )

The issue is that the backup app is not properly restoring master. Most likely it failed to back up the file because it was locked by SQL at the time. Backup apps using the VSS infrastructure do not have this issue.

So, you have a few options:

1) shut down SQL Express during the backup so that the database files are properly saved

2) after bare-metal restore, uninstall SQL Express (this will not remove any databases you've created), reinstall it, and then restore your master database from backup (along with all other databases). This should restore all customizations that you have made.

3) Books Online documents a procedure for rebuild the system databases (master, model, msdb) using setup.exe:

If you extract the setup files to a directory by downloading and saving sqlexpr.exe (if you haven't already) using the command sqlexpr.exe /x, you'll have all the setup files.

Then, use the command:

start /wait <CD or DVD Drive>\setup.exe /qn INSTANCENAME=SQLExpress REINSTALL=SQL_Engine REBUILDDATABASE=1 SAPWD=<NewStrongPassword> REINSTALLMODE=vomus

The setup will recreate all of the system databases without disturbing anything else. You can then restore master and the other databases from your backups and be up and running.

sql

Tuesday, March 20, 2012

Restoring Merge Publication

I'm looking for a little help in preparing a disaster recovery staragey for
merge replication. We are desigining a replication topology that includes
publishers, named Republishers and several hundred anonymous merge
subscribers.
The "top tier" publisher will only talk to named subscribers, so its
recovery via a restore and then synchronizing with the named subscribers
should be fine. The problem I see is with the "tier 2" (republisher with
anonymous subscriptions to it) may not be recoverable according to the
excerpt below from the books online.
The situation would be Anonymous sub updates a record, it is replicated to
the "tier 2" box. The "Tier 2" box dies and is restored from several days
earlier. This "tier 2" republisher is synchonized with the "top tier"
publisher bringing it fairly current. The Anonymous subscriber now
synchronizes again with the restore tier 2 box.
Does it resend it's update? What specifically is missing on anoymous
subscribers that will cause an issue?
Any insight is appreciated!!!
"Caution If you synchronize with a subscription database, you must
synchronize with one that has a global subscription (that is, a subscription
having an assigned priority value) to guarantee correct convergence behavior.
Do not synchronize the publication database with a subscription database that
has an anonymous subscription. Because anonymous subscriptions do not have
enough meta data to apply changes to the publication database, such
synchronization could lead to the non-convergence of data."
Dear Brain,
If i understand ur questation then i suggest that doing replication is not
the best best thing and it take lot of time for replication and as u
mentioned u r going for 2 tier and if replication fails then it is a problem
for u.
So i tell u i had faced the same problem and i created a job and a cursor in
which i update all my tables every 2 hour mintues in the cursor i mentioned
that when the updation is complete in one database then it shift to other
changing the ip address of the server.
U can also update all the datebase server at a time. I had 1500 tables and 8
remotes location and it take only one hour to update.
if i had did wrong then feel free to tell me to update my knowledge.
from sufian
"Brian Reuter" wrote:

> I'm looking for a little help in preparing a disaster recovery staragey for
> merge replication. We are desigining a replication topology that includes
> publishers, named Republishers and several hundred anonymous merge
> subscribers.
> The "top tier" publisher will only talk to named subscribers, so its
> recovery via a restore and then synchronizing with the named subscribers
> should be fine. The problem I see is with the "tier 2" (republisher with
> anonymous subscriptions to it) may not be recoverable according to the
> excerpt below from the books online.
> The situation would be Anonymous sub updates a record, it is replicated to
> the "tier 2" box. The "Tier 2" box dies and is restored from several days
> earlier. This "tier 2" republisher is synchonized with the "top tier"
> publisher bringing it fairly current. The Anonymous subscriber now
> synchronizes again with the restore tier 2 box.
> Does it resend it's update? What specifically is missing on anoymous
> subscribers that will cause an issue?
> Any insight is appreciated!!!
>
> "Caution If you synchronize with a subscription database, you must
> synchronize with one that has a global subscription (that is, a subscription
> having an assigned priority value) to guarantee correct convergence behavior.
> Do not synchronize the publication database with a subscription database that
> has an anonymous subscription. Because anonymous subscriptions do not have
> enough meta data to apply changes to the publication database, such
> synchronization could lead to the non-convergence of data."
>

Monday, March 12, 2012

restoring master database

Restoring master database

Hi All
Im testing our disaster recovery plan by rebuilding our production server
onto a new server box with different hardware and partitions.
Ive started the SQL server in single user mode and restored the master
database to a success message but when it tries to restart it fails to start.
On checking the error log there are some VDN errors, I assume that this is
because the server Im restoring it to has different drive setup to the live
server.
Is there anyway around this problem?
Message posted via http://www.droptable.com
Hi
Does this occur on subsequent restarts?
John
"Tony S via droptable.com" <forum@.droptable.com> wrote in message
news:5410926593904@.droptable.com...
> Hi All
> I'm testing our disaster recovery plan by rebuilding our production server
> onto a new server box with different hardware and partitions.
> I've started the SQL server in single user mode and restored the master
> database to a success message but when it tries to restart it fails to
> start.
>
> On checking the error log there are some VDN errors, I assume that this is
> because the server I'm restoring it to has different drive setup to the
> live
> server.
> Is there anyway around this problem?
>
> --
> Message posted via http://www.droptable.com
|||Hi
I get the VDN error reported after everytime I try and restart the SQL Server,
regardless of how I try to restart it.
Tony
|||Hi Tony
Even with the -f flag?
Have you followed
http://support.microsoft.com/default...22120121120120
John
"Tony S via droptable.com" <forum@.droptable.com> wrote in message
news:54196F15F1D57@.droptable.com...
> Hi
> I get the VDN error reported after everytime I try and restart the SQL
> Server,
> regardless of how I try to restart it.
> Tony
|||Hi John
Yes it fails to start even with the -f flag
I've tried changing the startup parameters but because the SQL server isn't
starting I can not get into the properties through Enterprise Manager.
Im not sure how Attach/Detach can help me as Im trying to restore from
backup?
The common error Im getting is when the SQL server is trying to start it is
looking for the other system databases from a drive that doesnt exist
producing VDN errors
Tony
John Bell wrote:[vbcol=seagreen]
>Hi Tony
>Even with the -f flag?
>Have you followed
>http://support.microsoft.com/default...22120121120120
>John
>[quoted text clipped - 3 lines]
Message posted via http://www.droptable.com
|||Hi
Test this out by calling sqlservr from a command prompt, see "sqlservr
Application" in Books online for parameters. Also check out the trace flag
3608 which will skip recovery on all databases except master, you can then
detach each database and re-attach with the new files as descibed for msdb
and model in
http://support.microsoft.com/default...22120121120120
To move tempdb use the alter database command as described.
John
"Tony S via droptable.com" <forum@.droptable.com> wrote in message
news:544195E6FFA0B@.droptable.com...
> Hi John
> Yes it fails to start even with the -f flag
> I've tried changing the startup parameters but because the SQL server
> isn't
> starting I can not get into the properties through Enterprise Manager.
> I'm not sure how Attach/Detach can help me as I'm trying to restore from
> backup?
> The common error I'm getting is when the SQL server is trying to start it
> is
> looking for the other system databases from a drive that doesn't exist
> producing VDN errors
> Tony
> John Bell wrote:
>
> --
> Message posted via http://www.droptable.com

restoring master database

Hi group!
I am trying to do the following for a recovery strategy: If server1 fails
all databases should be restored on server2. I did a restore of the master
database as described in some articles (starting in single user mode,
restoring...) after restoring my sql server does not start. An example error
message is:
FCB::Open failed: Could not open device d:\sql\MSSQL\data\pubs.mdf for
virtual device number (VDN) 1.
On server1 my data directory is d:\sql\mssql\data - on server2 my data
directory is d:\sql\mssql\mssql\data (configuration error during setup). He
wants to load all databases but of course does not have all the databases -
I have to recover them now - but how - I can't start the service..
Anyone an idea?
best regards
andyIf you are going to restore master from one server onto another, then you
need to have all DB's in the exact same location as they were on the
original server.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
.
"Andreas Wöckl" <woeckl@.esys.at> wrote in message
news:en%230WpR6FHA.1000@.tk2msftngp13.phx.gbl...
Hi group!
I am trying to do the following for a recovery strategy: If server1 fails
all databases should be restored on server2. I did a restore of the master
database as described in some articles (starting in single user mode,
restoring...) after restoring my sql server does not start. An example error
message is:
FCB::Open failed: Could not open device d:\sql\MSSQL\data\pubs.mdf for
virtual device number (VDN) 1.
On server1 my data directory is d:\sql\mssql\data - on server2 my data
directory is d:\sql\mssql\mssql\data (configuration error during setup). He
wants to load all databases but of course does not have all the databases -
I have to recover them now - but how - I can't start the service..
Anyone an idea?
best regards
andy|||hi tom!
hmm - but what are the steps that I have to take - Am I right that I first
have to restore all the databases and the last step is to restore the master
database?
best regards
andy
"Tom Moreau" <tom@.dont.spam.me.cips.ca> schrieb im Newsbeitrag
news:%23jM$tsR6FHA.4076@.tk2msftngp13.phx.gbl...
> If you are going to restore master from one server onto another, then you
> need to have all DB's in the exact same location as they were on the
> original server.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> .
> "Andreas Wöckl" <woeckl@.esys.at> wrote in message
> news:en%230WpR6FHA.1000@.tk2msftngp13.phx.gbl...
> Hi group!
> I am trying to do the following for a recovery strategy: If server1 fails
> all databases should be restored on server2. I did a restore of the master
> database as described in some articles (starting in single user mode,
> restoring...) after restoring my sql server does not start. An example
> error
> message is:
> FCB::Open failed: Could not open device d:\sql\MSSQL\data\pubs.mdf for
> virtual device number (VDN) 1.
> On server1 my data directory is d:\sql\mssql\data - on server2 my data
> directory is d:\sql\mssql\mssql\data (configuration error during setup).
> He
> wants to load all databases but of course does not have all the
> databases -
> I have to recover them now - but how - I can't start the service..
> Anyone an idea?
> best regards
> andy
>|||A technique we have used successfully in tests is:
1- Install SQL Server on new server
2- Restore individual databases to new server using one of three techniques:
a- Restore with third party software with new location
b- restore with manual restore command with move option
c- re-attach copies of detached databases
3- Get a list of the users from each application database
4- Either run sp_helplogins (and related scripts/procedures) or use the list
from 3 to rebuild access.
--
Joseph R.P. Maloney, CSP,CCP,CDP
"Andreas WÃ¶ckl" wrote:
> hi tom!
> hmm - but what are the steps that I have to take - Am I right that I first
> have to restore all the databases and the last step is to restore the master
> database?
> best regards
> andy
>
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> schrieb im Newsbeitrag
> news:%23jM$tsR6FHA.4076@.tk2msftngp13.phx.gbl...
> > If you are going to restore master from one server onto another, then you
> > need to have all DB's in the exact same location as they were on the
> > original server.
> >
> > --
> > Tom
> >
> > ----
> > Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> > SQL Server MVP
> > Columnist, SQL Server Professional
> > Toronto, ON Canada
> > www.pinpub.com
> > .
> > "Andreas WÃ¶ckl" <woeckl@.esys.at> wrote in message
> > news:en%230WpR6FHA.1000@.tk2msftngp13.phx.gbl...
> > Hi group!
> >
> > I am trying to do the following for a recovery strategy: If server1 fails
> > all databases should be restored on server2. I did a restore of the master
> > database as described in some articles (starting in single user mode,
> > restoring...) after restoring my sql server does not start. An example
> > error
> > message is:
> >
> > FCB::Open failed: Could not open device d:\sql\MSSQL\data\pubs.mdf for
> > virtual device number (VDN) 1.
> >
> > On server1 my data directory is d:\sql\mssql\data - on server2 my data
> > directory is d:\sql\mssql\mssql\data (configuration error during setup).
> > He
> > wants to load all databases but of course does not have all the
> > databases -
> > I have to recover them now - but how - I can't start the service..
> >
> > Anyone an idea?
> >
> > best regards
> >
> > andy
> >
> >
>
>|||What I do is restore the app DB's, then msdb then master. As I said
before - make sure they are in the exact same folders with the exact same
filenames as on your source server.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
"Andreas Wöckl" <woeckl@.esys.at> wrote in message
news:OglOL2R6FHA.3048@.TK2MSFTNGP10.phx.gbl...
> hi tom!
> hmm - but what are the steps that I have to take - Am I right that I first
> have to restore all the databases and the last step is to restore the
> master database?
> best regards
> andy
>
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> schrieb im Newsbeitrag
> news:%23jM$tsR6FHA.4076@.tk2msftngp13.phx.gbl...
>> If you are going to restore master from one server onto another, then you
>> need to have all DB's in the exact same location as they were on the
>> original server.
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinpub.com
>> .
>> "Andreas Wöckl" <woeckl@.esys.at> wrote in message
>> news:en%230WpR6FHA.1000@.tk2msftngp13.phx.gbl...
>> Hi group!
>> I am trying to do the following for a recovery strategy: If server1 fails
>> all databases should be restored on server2. I did a restore of the
>> master
>> database as described in some articles (starting in single user mode,
>> restoring...) after restoring my sql server does not start. An example
>> error
>> message is:
>> FCB::Open failed: Could not open device d:\sql\MSSQL\data\pubs.mdf for
>> virtual device number (VDN) 1.
>> On server1 my data directory is d:\sql\mssql\data - on server2 my data
>> directory is d:\sql\mssql\mssql\data (configuration error during setup).
>> He
>> wants to load all databases but of course does not have all the
>> databases -
>> I have to recover them now - but how - I can't start the service..
>> Anyone an idea?
>> best regards
>> andy
>>
>|||We restore the Master, MSDB before rebooting, and then the individual
databases.
"Tom Moreau" wrote:
> What I do is restore the app DB's, then msdb then master. As I said
> before - make sure they are in the exact same folders with the exact same
> filenames as on your source server.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> "Andreas WÃ¶ckl" <woeckl@.esys.at> wrote in message
> news:OglOL2R6FHA.3048@.TK2MSFTNGP10.phx.gbl...
> > hi tom!
> >
> > hmm - but what are the steps that I have to take - Am I right that I first
> > have to restore all the databases and the last step is to restore the
> > master database?
> >
> > best regards
> >
> > andy
> >
> >
> > "Tom Moreau" <tom@.dont.spam.me.cips.ca> schrieb im Newsbeitrag
> > news:%23jM$tsR6FHA.4076@.tk2msftngp13.phx.gbl...
> >> If you are going to restore master from one server onto another, then you
> >> need to have all DB's in the exact same location as they were on the
> >> original server.
> >>
> >> --
> >> Tom
> >>
> >> ----
> >> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> >> SQL Server MVP
> >> Columnist, SQL Server Professional
> >> Toronto, ON Canada
> >> www.pinpub.com
> >> .
> >> "Andreas WÃ¶ckl" <woeckl@.esys.at> wrote in message
> >> news:en%230WpR6FHA.1000@.tk2msftngp13.phx.gbl...
> >> Hi group!
> >>
> >> I am trying to do the following for a recovery strategy: If server1 fails
> >> all databases should be restored on server2. I did a restore of the
> >> master
> >> database as described in some articles (starting in single user mode,
> >> restoring...) after restoring my sql server does not start. An example
> >> error
> >> message is:
> >>
> >> FCB::Open failed: Could not open device d:\sql\MSSQL\data\pubs.mdf for
> >> virtual device number (VDN) 1.
> >>
> >> On server1 my data directory is d:\sql\mssql\data - on server2 my data
> >> directory is d:\sql\mssql\mssql\data (configuration error during setup).
> >> He
> >> wants to load all databases but of course does not have all the
> >> databases -
> >> I have to recover them now - but how - I can't start the service..
> >>
> >> Anyone an idea?
> >>
> >> best regards
> >>
> >> andy
> >>
> >>
> >
> >
>
>|||Here's the info I mentioned from BOL:
To recover from a disaster, perform the following steps after acquiring
suitable replacement hardware:
Install Windows NT 4.0 or Windows 2000, and apply the appropriate service
pack. Verify that appropriate domain functionality exists.
Install SQL Server, and apply the appropriate service pack. Restore the
master and msdb database backups. Restart the server after restoring the
master database.
Reconfigure the server for the appropriate network libraries and security
mode.
Confirm that SQL Server is running properly by checking SQL Server Service
Manager and the Windows application log. If the Windows NT 4.0 or Windows
2000 name was changed, use sp_dropserver and sp_addserver to match it with
the SQL Server computer name.
Restore and recover each database according to its recovery plan.
Verify the availability of the system. Run a base functionality script to
ensure correct operation.
Allow users to resume normal usage.
"Tom Moreau" wrote:
> What I do is restore the app DB's, then msdb then master. As I said
> before - make sure they are in the exact same folders with the exact same
> filenames as on your source server.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> "Andreas WÃ¶ckl" <woeckl@.esys.at> wrote in message
> news:OglOL2R6FHA.3048@.TK2MSFTNGP10.phx.gbl...
> > hi tom!
> >
> > hmm - but what are the steps that I have to take - Am I right that I first
> > have to restore all the databases and the last step is to restore the
> > master database?
> >
> > best regards
> >
> > andy
> >
> >
> > "Tom Moreau" <tom@.dont.spam.me.cips.ca> schrieb im Newsbeitrag
> > news:%23jM$tsR6FHA.4076@.tk2msftngp13.phx.gbl...
> >> If you are going to restore master from one server onto another, then you
> >> need to have all DB's in the exact same location as they were on the
> >> original server.
> >>
> >> --
> >> Tom
> >>
> >> ----
> >> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> >> SQL Server MVP
> >> Columnist, SQL Server Professional
> >> Toronto, ON Canada
> >> www.pinpub.com
> >> .
> >> "Andreas WÃ¶ckl" <woeckl@.esys.at> wrote in message
> >> news:en%230WpR6FHA.1000@.tk2msftngp13.phx.gbl...
> >> Hi group!
> >>
> >> I am trying to do the following for a recovery strategy: If server1 fails
> >> all databases should be restored on server2. I did a restore of the
> >> master
> >> database as described in some articles (starting in single user mode,
> >> restoring...) after restoring my sql server does not start. An example
> >> error
> >> message is:
> >>
> >> FCB::Open failed: Could not open device d:\sql\MSSQL\data\pubs.mdf for
> >> virtual device number (VDN) 1.
> >>
> >> On server1 my data directory is d:\sql\mssql\data - on server2 my data
> >> directory is d:\sql\mssql\mssql\data (configuration error during setup).
> >> He
> >> wants to load all databases but of course does not have all the
> >> databases -
> >> I have to recover them now - but how - I can't start the service..
> >>
> >> Anyone an idea?
> >>
> >> best regards
> >>
> >> andy
> >>
> >>
> >
> >
>
>|||The problem with that is that you get error messages, since the app DB's
don't (yet) exist.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
"burt_king" <burt_king@.yahoo.com> wrote in message
news:1101C4D3-115D-43C8-A7FF-01DC1D728098@.microsoft.com...
> We restore the Master, MSDB before rebooting, and then the individual
> databases.
> "Tom Moreau" wrote:
>> What I do is restore the app DB's, then msdb then master. As I said
>> before - make sure they are in the exact same folders with the exact same
>> filenames as on your source server.
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinpub.com
>> "Andreas Wöckl" <woeckl@.esys.at> wrote in message
>> news:OglOL2R6FHA.3048@.TK2MSFTNGP10.phx.gbl...
>> > hi tom!
>> >
>> > hmm - but what are the steps that I have to take - Am I right that I
>> > first
>> > have to restore all the databases and the last step is to restore the
>> > master database?
>> >
>> > best regards
>> >
>> > andy
>> >
>> >
>> > "Tom Moreau" <tom@.dont.spam.me.cips.ca> schrieb im Newsbeitrag
>> > news:%23jM$tsR6FHA.4076@.tk2msftngp13.phx.gbl...
>> >> If you are going to restore master from one server onto another, then
>> >> you
>> >> need to have all DB's in the exact same location as they were on the
>> >> original server.
>> >>
>> >> --
>> >> Tom
>> >>
>> >> ----
>> >> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> >> SQL Server MVP
>> >> Columnist, SQL Server Professional
>> >> Toronto, ON Canada
>> >> www.pinpub.com
>> >> .
>> >> "Andreas Wöckl" <woeckl@.esys.at> wrote in message
>> >> news:en%230WpR6FHA.1000@.tk2msftngp13.phx.gbl...
>> >> Hi group!
>> >>
>> >> I am trying to do the following for a recovery strategy: If server1
>> >> fails
>> >> all databases should be restored on server2. I did a restore of the
>> >> master
>> >> database as described in some articles (starting in single user mode,
>> >> restoring...) after restoring my sql server does not start. An example
>> >> error
>> >> message is:
>> >>
>> >> FCB::Open failed: Could not open device d:\sql\MSSQL\data\pubs.mdf for
>> >> virtual device number (VDN) 1.
>> >>
>> >> On server1 my data directory is d:\sql\mssql\data - on server2 my data
>> >> directory is d:\sql\mssql\mssql\data (configuration error during
>> >> setup).
>> >> He
>> >> wants to load all databases but of course does not have all the
>> >> databases -
>> >> I have to recover them now - but how - I can't start the service..
>> >>
>> >> Anyone an idea?
>> >>
>> >> best regards
>> >>
>> >> andy
>> >>
>> >>
>> >
>> >
>>|||hi tom!
thanks for your help - the recovery with the same paths was o.k - I restored
the user databases and then the master database. I still have some troubles
with the msdb because sql server prompts that the msdb has been created with
a different version - both sql servers have service pack 4..?
best regards
andy
"Tom Moreau" <tom@.dont.spam.me.cips.ca> schrieb im Newsbeitrag
news:%2345V%232T6FHA.2896@.TK2MSFTNGP10.phx.gbl...
> What I do is restore the app DB's, then msdb then master. As I said
> before - make sure they are in the exact same folders with the exact same
> filenames as on your source server.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> "Andreas Wöckl" <woeckl@.esys.at> wrote in message
> news:OglOL2R6FHA.3048@.TK2MSFTNGP10.phx.gbl...
>> hi tom!
>> hmm - but what are the steps that I have to take - Am I right that I
>> first have to restore all the databases and the last step is to restore
>> the master database?
>> best regards
>> andy
>>
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> schrieb im Newsbeitrag
>> news:%23jM$tsR6FHA.4076@.tk2msftngp13.phx.gbl...
>> If you are going to restore master from one server onto another, then
>> you
>> need to have all DB's in the exact same location as they were on the
>> original server.
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinpub.com
>> .
>> "Andreas Wöckl" <woeckl@.esys.at> wrote in message
>> news:en%230WpR6FHA.1000@.tk2msftngp13.phx.gbl...
>> Hi group!
>> I am trying to do the following for a recovery strategy: If server1
>> fails
>> all databases should be restored on server2. I did a restore of the
>> master
>> database as described in some articles (starting in single user mode,
>> restoring...) after restoring my sql server does not start. An example
>> error
>> message is:
>> FCB::Open failed: Could not open device d:\sql\MSSQL\data\pubs.mdf for
>> virtual device number (VDN) 1.
>> On server1 my data directory is d:\sql\mssql\data - on server2 my data
>> directory is d:\sql\mssql\mssql\data (configuration error during setup).
>> He
>> wants to load all databases but of course does not have all the
>> databases -
>> I have to recover them now - but how - I can't start the service..
>> Anyone an idea?
>> best regards
>> andy
>>
>>
>|||Hmm. Do both have the same hotfixes?
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
"Andreas Wöckl" <woeckl@.esys.at> wrote in message
news:eZ9onDb6FHA.2608@.tk2msftngp13.phx.gbl...
> hi tom!
> thanks for your help - the recovery with the same paths was o.k - I
> restored the user databases and then the master database. I still have
> some troubles with the msdb because sql server prompts that the msdb has
> been created with a different version - both sql servers have service pack
> 4..?
> best regards
> andy
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> schrieb im Newsbeitrag
> news:%2345V%232T6FHA.2896@.TK2MSFTNGP10.phx.gbl...
>> What I do is restore the app DB's, then msdb then master. As I said
>> before - make sure they are in the exact same folders with the exact same
>> filenames as on your source server.
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinpub.com
>> "Andreas Wöckl" <woeckl@.esys.at> wrote in message
>> news:OglOL2R6FHA.3048@.TK2MSFTNGP10.phx.gbl...
>> hi tom!
>> hmm - but what are the steps that I have to take - Am I right that I
>> first have to restore all the databases and the last step is to restore
>> the master database?
>> best regards
>> andy
>>
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> schrieb im Newsbeitrag
>> news:%23jM$tsR6FHA.4076@.tk2msftngp13.phx.gbl...
>> If you are going to restore master from one server onto another, then
>> you
>> need to have all DB's in the exact same location as they were on the
>> original server.
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinpub.com
>> .
>> "Andreas Wöckl" <woeckl@.esys.at> wrote in message
>> news:en%230WpR6FHA.1000@.tk2msftngp13.phx.gbl...
>> Hi group!
>> I am trying to do the following for a recovery strategy: If server1
>> fails
>> all databases should be restored on server2. I did a restore of the
>> master
>> database as described in some articles (starting in single user mode,
>> restoring...) after restoring my sql server does not start. An example
>> error
>> message is:
>> FCB::Open failed: Could not open device d:\sql\MSSQL\data\pubs.mdf for
>> virtual device number (VDN) 1.
>> On server1 my data directory is d:\sql\mssql\data - on server2 my data
>> directory is d:\sql\mssql\mssql\data (configuration error during
>> setup). He
>> wants to load all databases but of course does not have all the
>> databases -
>> I have to recover them now - but how - I can't start the service..
>> Anyone an idea?
>> best regards
>> andy
>>
>>
>>
>

Monday, March 26, 2012

Restoring the master database

Restoring the master database

Restoring the Master Database

Restoring the master database

Restoring the master

restoring the database

Friday, March 23, 2012

Restoring sql express and databases from tape backup.

Tuesday, March 20, 2012

Restoring Merge Publication

Monday, March 12, 2012

restoring master database

Restoring master database

restoring master database

database problem

Blog Archive

About Me