Disaster Recovery With SQL 8.0

Hi,
We are trialling a disaster recovery for a new customer who has been assured
his SQL is being backed up and can be recovered with the minimum of fuss. I
immediately found that his Master and Model were not being backed up, not
the end of the world but not what they were expecting either. Anyway, their
SQL is backed up a coupld of times per day via a Maintenance Plan. I have
completely restored his server to a new box and everything, apart from SQL,
is up and running. The situation is, I have the databases in *.bak format,
but because the Master and Model are missing, I cannot start SQL to
re-attach the databases. I have since copied a backup of Master and Model
taken since the original backup, copied them into place and tried to start
the service. No joy. No error. No nothing.
I've hunted high and low to find some documentation for my current scenario,
but not found any. Can somebody please point me in the right direction.
Many thanks
Hi
You can not attach a *.bak file. It's a backup you need to restore it. As
you say you don't need the master and model. However if you have a lot of
individual users with standard accounts it might take a while to get the
master up to date.
Here are some links to a lot of articles about moving/restoring databases to
another server. they should help you understand and resolve your issues.
http://www.support.microsoft.com/?id=314546 Moving DB's between Servers
http://www.support.microsoft.com/?id=224071 Moving SQL Server Databases to a
New Location with Detach/Attach
http://support.microsoft.com/?id=221465 Using WITH MOVE in a Restore
http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
Passwords Between SQL Servers
http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after a
Restore http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
users
http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
Errors After Restoring Dump
http://www.support.microsoft.com/?id=240872 How to Resolve Permission Issues
When a Database Is Moved Between SQL Servers
http://www.sqlservercentral.com/scri...p?scriptid=599
Restoring a .mdf http://www.support.microsoft.com/?id=307775 Disaster
Recovery Articles for SQL Server
Good Luck
John
|||By the way when i said you don't need to master and model database I did of
course mean you don't need to original. You definately need a master and
model database.
|||"John Bandettini" <JohnBandettini@.discussions.microsoft.com> wrote in
message news:AB7C8416-35B2-4233-8D4B-FE39CC2CCC9F@.microsoft.com...
> Hi
> You can not attach a *.bak file. It's a backup you need to restore it. As
> you say you don't need the master and model. However if you have a lot of
> individual users with standard accounts it might take a while to get the
> master up to date.
> Here are some links to a lot of articles about moving/restoring databases
> to
> another server. they should help you understand and resolve your issues.
> http://www.support.microsoft.com/?id=314546 Moving DB's between Servers
> http://www.support.microsoft.com/?id=224071 Moving SQL Server Databases to
> a
> New Location with Detach/Attach
> http://support.microsoft.com/?id=221465 Using WITH MOVE in a Restore
> http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
> Passwords Between SQL Servers
> http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after a
> Restore http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
> users
> http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
> Errors After Restoring Dump
> http://www.support.microsoft.com/?id=240872 How to Resolve Permission
> Issues
> When a Database Is Moved Between SQL Servers
> http://www.sqlservercentral.com/scri...p?scriptid=599
> Restoring a .mdf http://www.support.microsoft.com/?id=307775 Disaster
> Recovery Articles for SQL Server
> Good Luck
> John
Thanks for the reply. A quick look through these, and they all rely on the
SQL server actually starting. My problem is, I can't start it! I've tried
rebuilding the Master but I get a message telling me there are no suitable
instances of SQL available..
|||Hi
I dont have access to your server and i don't know how you restored it, so I
can not comment on those issues. However from my experiences it is very hard
to restore a server including SQL Server files and then get it to work.
You would find it a lot easier to install SQL Server from scratch and then
restore your databases.
What tends to happen when you restore the entire Server is that SQL Server
does not respond well. (As you have found out). Usual reason is that the
backup software cannot backup in-use files. So you have things missing, most
significantly the .mdf and .ldf files.
With copies of the Master and Model and MSDB from another server and a good
bit of hacking into the register you may be able to bring it up, but what
state it would be in I don't know. Not a good one I'm sure.
I would advise you to rebuild the server, Install the operating system and
SQL Server and then follow the articles I first posted. Trying to proceed
from your current position is not going to work.
Regards
John
|||"John Bandettini" <JohnBandettini@.discussions.microsoft.com> wrote in
message news:31C3562B-D4B3-44FA-96AA-C6E8856FFDE3@.microsoft.com...
> Hi
> I dont have access to your server and i don't know how you restored it, so
> I
> can not comment on those issues. However from my experiences it is very
> hard
> to restore a server including SQL Server files and then get it to work.
> You would find it a lot easier to install SQL Server from scratch and then
> restore your databases.
> What tends to happen when you restore the entire Server is that SQL Server
> does not respond well. (As you have found out). Usual reason is that the
> backup software cannot backup in-use files. So you have things missing,
> most
> significantly the .mdf and .ldf files.
> With copies of the Master and Model and MSDB from another server and a
> good
> bit of hacking into the register you may be able to bring it up, but what
> state it would be in I don't know. Not a good one I'm sure.
> I would advise you to rebuild the server, Install the operating system and
> SQL Server and then follow the articles I first posted. Trying to proceed
> from your current position is not going to work.
> Regards
> John
Done it. Managed to get rebuildm.exe working after all kinds of traumas, and
once I had master back in place, it was as easy as I was hoping it would be!
Thanks for you help.
Matt