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
andy
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 Wckl" <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 Wckl" <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...
>
>
|||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 Wckl" <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...
>
|||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...
>
>
|||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...
>
>
|||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...[vbcol=seagreen]
> We restore the Master, MSDB before rebooting, and then the individual
> databases.
> "Tom Moreau" wrote:
|||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 Wckl" <woeckl@.esys.at> wrote in message
> news:OglOL2R6FHA.3048@.TK2MSFTNGP10.phx.gbl...
>
|||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 Wckl" <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...
>

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 Wckl" <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 Wckl" <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 mast
er
> database?
> best regards
> andy
>
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> schrieb im Newsbeitrag
> news:%23jM$tsR6FHA.4076@.tk2msftngp13.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 Wckl" <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...
>|||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...
>
>|||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...
>
>|||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...[vbcol=seagreen]
> We restore the Master, MSDB before rebooting, and then the individual
> databases.
> "Tom Moreau" wrote:
>|||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 Wckl" <woeckl@.esys.at> wrote in message
> news:OglOL2R6FHA.3048@.TK2MSFTNGP10.phx.gbl...
>|||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 Wckl" <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...
>