|
sql
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
SQL 2000 restore problem
sql 2k (sp4). I want to use this to document/test steps that I'd take in a disaster recovery scenario. Both servers are in the same domain. Obviously different computer names. Here's what I did: 1. old server: all databases are backed up regularly. I have periodically restored some of these without any problems. 2. new server: installed sql 2k and sp4. same collation as old. new sa password. new location for data. 3. new: created same local windows groups and users as on old server. 4. old: stop sql server. restart in single user mode. open QA as sa (to keep developers out) . 5. new: start sql in single user mode. open QA as sa. Restore backup of master from old server. Restore seems successful and sql stops (it's suppose to, right?) Location of master is different on new server than on old server. 6. new: start sql in single user mode. I can't connect as sa with either old or new sa password. "not associated with a trusted connection" error. Step#4 shows I know the sa password from the original/old server; step#5 shows that I know the new password. My questions: I don't understand not being able to login on the new server using 'sa'. In my disaster recovery scenario, is the correct order of restores (on the new server) master, model, msdb, then our agency databases? Thanks Tom -- E-mail correspondence to and from this address may be subject to the North Carolina Public Records Law and may be disclosed to third parties. It seems like the SQL Server is configures to accept only Windows connections. Try re.-configure
(change in registry if needed). Also, KB 224071 has some good info on this topic. -- Show quoteHide quoteTibor Karaszi, SQL Server MVP http://www.karaszi.com/sqlserver/default.asp http://www.solidqualitylearning.com/ "Tom W" <Tom.Williams@DontSpamMencmail.net> wrote in message news:%23iF$aMlCHHA.5068@TK2MSFTNGP02.phx.gbl... > My agency bought a new server to replace an existing server that hosts sql 2k (sp4). I want to > use this to document/test steps that I'd take in a disaster recovery scenario. Both servers are > in the same domain. Obviously different computer names. > > Here's what I did: > > 1. old server: all databases are backed up regularly. I have periodically restored some of these > without any problems. > 2. new server: installed sql 2k and sp4. same collation as old. new sa password. new location > for data. > 3. new: created same local windows groups and users as on old server. > 4. old: stop sql server. restart in single user mode. open QA as sa (to keep developers out) . > 5. new: start sql in single user mode. open QA as sa. Restore backup of master from old server. > Restore seems successful and sql stops (it's suppose to, right?) Location of master is different > on new server than on old server. > > 6. new: start sql in single user mode. I can't connect as sa with either old or new sa password. > "not associated with a trusted connection" error. Step#4 shows I know the sa password from the > original/old server; step#5 shows that I know the new password. > > My questions: > I don't understand not being able to login on the new server using 'sa'. > > In my disaster recovery scenario, is the correct order of restores (on the new server) master, > model, msdb, then our agency databases? > > > Thanks > Tom > > -- > > > > E-mail correspondence to and from this address may be subject to the > North Carolina Public Records Law and may be disclosed to third parties. Thanks Tibor. You are correct.
What about my 2nd question? is the correct order of restores (on the new server) master, model, msdb, then our agency databases? Thanks Tom Tibor Karaszi wrote: Show quoteHide quote > It seems like the SQL Server is configures to accept only Windows > connections. Try re.-configure (change in registry if needed). Also, > KB 224071 has some good info on this topic. > -- E-mail correspondence to and from this address may be subject to the North Carolina Public Records Law and may be disclosed to third parties. Yes, that seem to be an appropriate order. But you need to be careful if you don't have the same
directory structures on both machine. Again, I believe 224071 has some good info on this. -- Show quoteHide quoteTibor Karaszi, SQL Server MVP http://www.karaszi.com/sqlserver/default.asp http://www.solidqualitylearning.com/ "Tom W" <Tom.Williams@DontSpamMencmail.net> wrote in message news:uNFYiknCHHA.3524@TK2MSFTNGP06.phx.gbl... > Thanks Tibor. You are correct. > > What about my 2nd question? > is the correct order of restores (on the new server) master, model, msdb, then our agency > databases? > > Thanks > Tom > > > Tibor Karaszi wrote: > >> It seems like the SQL Server is configures to accept only Windows connections. Try re.-configure >> (change in registry if needed). Also, KB 224071 has some good info on this topic. >> > > -- > > > > E-mail correspondence to and from this address may be subject to the > North Carolina Public Records Law and may be disclosed to third parties.
Other interesting topics
|
|||||||||||||||||||||||