Restoring Master on another machine...

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • murrayb3024@gmail.com

    Restoring Master on another machine...

    We set up a test box and having been trying to move an entire instance
    from our production server to this one. I have moved all my created
    dbs using the RESTORE WITH MOVE. Now I am trying to move the Master,
    Model, and msdb. This is where I am having trouble. On the production
    box the dbs are stored on D:\mssql$instan cename\data. On the test
    server the data is stored in C:\Program Files\Microsoft SQL
    Server\mssql$in stancename\data . Also the server names are different.
    So I finally got the Master from production to restore over the test's
    copy. Now the instance will not start. I was trying to use the
    following code in cmd line to connect to the instace so I could then
    copy model and msdb:

    sqlservr -c -f -T3608 -T4022 -sINSTANCENAME

    When this is trying to connect I read it is failing and saying that the
    MDF and LDF may be corrupt or not there. The problem is it is now
    trying to look in D:\mssql$instan cename\data instead of C:\Program
    Files\Microsoft SQL Server\mssql$in stancename\data . Any ideas on how I
    can change this, or if I have to reinstall the entire instace, not run
    into this again?

  • Erland Sommarskog

    #2
    Re: Restoring Master on another machine...

    (murrayb3024@gm ail.com) writes:[color=blue]
    > We set up a test box and having been trying to move an entire instance
    > from our production server to this one. I have moved all my created
    > dbs using the RESTORE WITH MOVE. Now I am trying to move the Master,
    > Model, and msdb. This is where I am having trouble. On the production
    > box the dbs are stored on D:\mssql$instan cename\data. On the test
    > server the data is stored in C:\Program Files\Microsoft SQL
    > Server\mssql$in stancename\data . Also the server names are different.
    > So I finally got the Master from production to restore over the test's
    > copy. Now the instance will not start. I was trying to use the
    > following code in cmd line to connect to the instace so I could then
    > copy model and msdb:
    >
    > sqlservr -c -f -T3608 -T4022 -sINSTANCENAME
    >
    > When this is trying to connect I read it is failing and saying that the
    > MDF and LDF may be corrupt or not there. The problem is it is now
    > trying to look in D:\mssql$instan cename\data instead of C:\Program
    > Files\Microsoft SQL Server\mssql$in stancename\data . Any ideas on how I
    > can change this, or if I have to reinstall the entire instace, not run
    > into this again?[/color]

    Before you set off, did you look at



    --
    Erland Sommarskog, SQL Server MVP, esquel@sommarsk og.se

    Books Online for SQL Server 2005 at

    Books Online for SQL Server 2000 at

    Comment

    • Ajay Rengunthwar

      #3
      Re: Restoring Master on another machine...

      The article is really useful


      Also attach & detach should save your lot of time.

      Thanks
      Ajay Rengunthwar
      MCDBA

      Comment

      Working...