restoring the master database

I read earlier posts about restoring the master database.
I am testing for failover, and I found that after I had restored the master
database to the failover server, the SQL Server service stopped immediately
after starting.
The databases on the production server are on a drive which doesn't exist on
the failover server. Is it necessary to configure the servers identically?
I think perhaps SQL Server service can't start because it can't locate the
model database to create the tempdb, or because the path the tempdb doesn't
exist.
I can't get it started even with sqlservr.exe -f, in order to Alter Database
and change the location of the databases.
The Event log had errors (17052, 17204) because the path in sysdatabases
points to a non-existent location.
I am running SQL Server 2000 Standard edition.
Thanks
Bill
Here is a nice article on moving db locations:
http://support.microsoft.com/default...;en-us;224071.
Check the master db first.
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com
"bill" <belgie@.datamti.com> wrote in message
news:%237QDmlDwEHA.1292@.TK2MSFTNGP10.phx.gbl...
> I read earlier posts about restoring the master database.
> I am testing for failover, and I found that after I had restored the
master
> database to the failover server, the SQL Server service stopped
immediately
> after starting.
> The databases on the production server are on a drive which doesn't exist
on
> the failover server. Is it necessary to configure the servers
identically?
> I think perhaps SQL Server service can't start because it can't locate the
> model database to create the tempdb, or because the path the tempdb
doesn't
> exist.
> I can't get it started even with sqlservr.exe -f, in order to Alter
Database
> and change the location of the databases.
> The Event log had errors (17052, 17204) because the path in sysdatabases
> points to a non-existent location.
> I am running SQL Server 2000 Standard edition.
> Thanks
> Bill
>
>
|||Master, Model, and MSDB must be in the same path they originally came from.
Keep in mind though that for reasons unknown to me SQL will shut down after
restoring even to the correct path.
"bill" <belgie@.datamti.com> wrote in message
news:#7QDmlDwEHA.1292@.TK2MSFTNGP10.phx.gbl...
> I read earlier posts about restoring the master database.
> I am testing for failover, and I found that after I had restored the
master
> database to the failover server, the SQL Server service stopped
immediately
> after starting.
> The databases on the production server are on a drive which doesn't exist
on
> the failover server. Is it necessary to configure the servers
identically?
> I think perhaps SQL Server service can't start because it can't locate the
> model database to create the tempdb, or because the path the tempdb
doesn't
> exist.
> I can't get it started even with sqlservr.exe -f, in order to Alter
Database
> and change the location of the databases.
> The Event log had errors (17052, 17204) because the path in sysdatabases
> points to a non-existent location.
> I am running SQL Server 2000 Standard edition.
> Thanks
> Bill
>
>
|||Hi
The SQL server log will tell you why it fails to start, but if you are
restoring a master database from a different configuration one of the
problems will be that it can not find the databases.
You hardware should be the same configuration, see "single node failover"
section of
http://www.microsoft.com/technet/pro...clus.mspx#EJAA
John
"bill" wrote:

> I read earlier posts about restoring the master database.
> I am testing for failover, and I found that after I had restored the master
> database to the failover server, the SQL Server service stopped immediately
> after starting.
> The databases on the production server are on a drive which doesn't exist on
> the failover server. Is it necessary to configure the servers identically?
> I think perhaps SQL Server service can't start because it can't locate the
> model database to create the tempdb, or because the path the tempdb doesn't
> exist.
> I can't get it started even with sqlservr.exe -f, in order to Alter Database
> and change the location of the databases.
> The Event log had errors (17052, 17204) because the path in sysdatabases
> points to a non-existent location.
> I am running SQL Server 2000 Standard edition.
> Thanks
> Bill
>
>
sql