Its not doable

I know it's not doable but I thought I should still ask the Gurus on this board:

Can I restore a master database backed up on server A to a new Server B.

Case1: Server A and Server B has the same structure, file system and drive specificiation, I think it's doable in that case.

Case2: Server A and Server B has different file system like c:\ and d:\ on A and C:\ and E:\ on Server B. It's nor DOABLE right?

Case3: Server A is called Server A and Server B is called B, then also we cannot restore the master database, RIGHT?Never done it...

but why not...you'll have to identify the new physical location in the restore..

like

RESTORE DATABASE TaxReconDB_Prod
FROM DISK = 'D:\Tax\BackUp\TaxReconDB.dmp'
WITH MOVE 'TaxReconDB_Data' TO 'D:\Database\NJROS1D151DEV\MSSQL$NJROS1D151DEV\Dat a\TaxReconDB_Prod_Data.MDF'
, MOVE 'TaxReconDB_Log' TO 'D:\Database\NJROS1D151DEV\MSSQL$NJROS1D151DEV\Dat a\TaxReconDB_Prod_Log.LDF'
, REPLACE|||If I had to make a guess, I'd say that you could RESTORE MASTER (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/howtosql/ht_7_backpc_61x5.asp), but that doesn't make it a good idea!

-PatP|||I've never done it...Pat?

I guess in some cases, when it's corrupted you have no choice...

knock on wood

Why do you want to do this...I bet it's some "clever" shortcut...|||It is a common trick for upgrading server hardware. You run up the new box (offline) with the same name and IP as the old box. You then restore master and reattach the other databases, and life is good!

-PatP|||As far as the locations and the drive specification are same, you are safe. But if the system databases where on a different drive on the old server than the new one, then you are in trouble.|||Originally posted by sqlserver2k
As far as the locations and the drive specification are same, you are safe. But if the system databases where on a different drive on the old server than the new one, then you are in trouble. Why is that? We move from C: to E: (and back) all of the time.

-PatP

Issue with restoring master db

Hi all,

I am trying to restore my master database to a new server in sql 2000. I have started sql in single user mode from the command line and connected to enterprise manager and attempted to do the restore. I also tried query analyzer and used the restore database from disk ='file path of backup' used the move option with the correct file path and on both counts received the same error message...

Error: 9001, Severity: 21, State: 1.
Error: 3151, Severity: 21, State: 0.

Any ideas? The connection is then broken (which I would expect anyway as restoring master shuts down sql but, I checked and it has not restored the db)

Thanks!This article may be of some help:

http://www.dbarecovery.com/restoremasterdb.html|||lmao @. your sig ... rdjabarov ... nice one !!!|||That is mostly what I have done (did not need to do the rebuild part) When I try to do the restore it does not complete but generates the error messages I listed in my first posting. I have done this before and it worked but, for some reason it is not allowing me to do the restore but, is breaking the connection.

Any other suggestions?|||I did some more checking - could there be an issue with one server having a windows service pack 3 and the other server having windows service pack 4?

Issue with restore to new dbname on same server

I ran this script to backup to restore a backup onto a database with a new
name - on the same server.
USE master
> RESTORE DATABASE DBnew
> FROM DISK = 'E:\MSSQL7\BACKUP\DBold_db_200409270201.BAK'
> with RECOVERY,
> MOVE 'DBold_Data' TO 'E:\MSSQL7\data\DBnew_Data.MDF',
> MOVE 'DBold_Log' TO 'E:\MSSQL7\data\DBnew_Log.LDF',
> REPLACE
When I look at the properties for the database under em, I see that both the
original database and the copy-of-it-with-a-new-name have the same "File
Name" (DBold_Data and DBold_Log, respectively) under the "Data Files" and
"Transaction Files" tabs. The "Location", which points to the actual
physical file, is correctly and uniquely named.
Is the fact that these have the same File Name going to confuse SQL Server
when it goes to update a database?You should be fine.
"MarkAurit" <MarkAurit@.discussions.microsoft.com> wrote in message
news:59CC2C26-13F8-4664-99F1-CC550827A9D4@.microsoft.com...
>I ran this script to backup to restore a backup onto a database with a new
> name - on the same server.
> USE master
> When I look at the properties for the database under em, I see that both
> the
> original database and the copy-of-it-with-a-new-name have the same "File
> Name" (DBold_Data and DBold_Log, respectively) under the "Data Files" and
> "Transaction Files" tabs. The "Location", which points to the actual
> physical file, is correctly and uniquely named.
> Is the fact that these have the same File Name going to confuse SQL Server
> when it goes to update a database?

Issue with restore to new dbname on same server

I ran this script to backup to restore a backup onto a database with a new
name - on the same server.
USE master
> RESTORE DATABASE DBnew
> FROM DISK = 'E:\MSSQL7\BACKUP\DBold_db_200409270201.BAK'
> with RECOVERY,
> MOVE 'DBold_Data' TO 'E:\MSSQL7\data\DBnew_Data.MDF',
> MOVE 'DBold_Log' TO 'E:\MSSQL7\data\DBnew_Log.LDF',
> REPLACE
When I look at the properties for the database under em, I see that both the
original database and the copy-of-it-with-a-new-name have the same "File
Name" (DBold_Data and DBold_Log, respectively) under the "Data Files" and
"Transaction Files" tabs. The "Location", which points to the actual
physical file, is correctly and uniquely named.
Is the fact that these have the same File Name going to confuse SQL Server
when it goes to update a database?
You should be fine.
"MarkAurit" <MarkAurit@.discussions.microsoft.com> wrote in message
news:59CC2C26-13F8-4664-99F1-CC550827A9D4@.microsoft.com...
>I ran this script to backup to restore a backup onto a database with a new
> name - on the same server.
> USE master
> When I look at the properties for the database under em, I see that both
> the
> original database and the copy-of-it-with-a-new-name have the same "File
> Name" (DBold_Data and DBold_Log, respectively) under the "Data Files" and
> "Transaction Files" tabs. The "Location", which points to the actual
> physical file, is correctly and uniquely named.
> Is the fact that these have the same File Name going to confuse SQL Server
> when it goes to update a database?

Issue with restore to new dbname on same server

I ran this script to backup to restore a backup onto a database with a new
name - on the same server.
USE master
> RESTORE DATABASE DBnew
> FROM DISK = 'E:\MSSQL7\BACKUP\DBold_db_200409270201.BAK'
> with RECOVERY,
> MOVE 'DBold_Data' TO 'E:\MSSQL7\data\DBnew_Data.MDF',
> MOVE 'DBold_Log' TO 'E:\MSSQL7\data\DBnew_Log.LDF',
> REPLACE
When I look at the properties for the database under em, I see that both the
original database and the copy-of-it-with-a-new-name have the same "File
Name" (DBold_Data and DBold_Log, respectively) under the "Data Files" and
"Transaction Files" tabs. The "Location", which points to the actual
physical file, is correctly and uniquely named.
Is the fact that these have the same File Name going to confuse SQL Server
when it goes to update a database?You should be fine.
"MarkAurit" <MarkAurit@.discussions.microsoft.com> wrote in message
news:59CC2C26-13F8-4664-99F1-CC550827A9D4@.microsoft.com...
>I ran this script to backup to restore a backup onto a database with a new
> name - on the same server.
> USE master
>> RESTORE DATABASE DBnew
>> FROM DISK = 'E:\MSSQL7\BACKUP\DBold_db_200409270201.BAK'
>> with RECOVERY,
>> MOVE 'DBold_Data' TO 'E:\MSSQL7\data\DBnew_Data.MDF',
>> MOVE 'DBold_Log' TO 'E:\MSSQL7\data\DBnew_Log.LDF',
>> REPLACE
> When I look at the properties for the database under em, I see that both
> the
> original database and the copy-of-it-with-a-new-name have the same "File
> Name" (DBold_Data and DBold_Log, respectively) under the "Data Files" and
> "Transaction Files" tabs. The "Location", which points to the actual
> physical file, is correctly and uniquely named.
> Is the fact that these have the same File Name going to confuse SQL Server
> when it goes to update a database?

Issue restoring database

I'm running into a problem restoring a database to MSDE.
Actually, osql reports RESTORE DATABASE successfully
worked but when I view the database from enterprise
manager it tells me the database is still "loading..."
Any suggestions?
Sounds like you are using NORECOVERY with the RESTORE command. This will
leave the database expecting additional restores.
Jim
"Tim" <tim.huenke@.ngc.com> wrote in message
news:0f9c01c4dee6$ebe38f60$a401280a@.phx.gbl...
> I'm running into a problem restoring a database to MSDE.
> Actually, osql reports RESTORE DATABASE successfully
> worked but when I view the database from enterprise
> manager it tells me the database is still "loading..."
> Any suggestions?