Results 1 to 5 of 5
  1. #1
    Join Date
    Jun 2012
    Posts
    2

    Unanswered: Moving SQL instances to a new Server

    We have a SQL instance on a physical clustered environment that we would like to move to a new VM server without disturbing the applications. The instance has its own DNS alias. I was under the impression that I could just install SQL on the new server and create a new instance and then a SQL alias and change the DNS alias to the new server ip. Does this make sense?

    Thanks!

  2. #2
    Join Date
    Jun 2012
    Posts
    4
    The SQL Server 2000 destination server can't be running the 64-bit version of SQL Server 2000. DTS parts for the 64-bit version of SQL Server 2000 aren't obtainable. If you're importing logins from an instance of SQL Server that's on a mainframe testing, your instance of SQL Server can should be running underneath a site Account to complete the task.
    Last edited by ashee1; 06-24-12 at 18:27.

  3. #3
    Join Date
    Feb 2004
    Location
    In front of the computer
    Posts
    15,579
    Provided Answers: 54
    The easiest answer by far is to use P2V or a similar utility to simply "clone" the phiscal server as a virtual machine. This is fast, easy, and in most cases has no side effects... the client machines literally don't know that anything happened!

    -PatP
    In theory, theory and practice are identical. In practice, theory and practice are unrelated.

  4. #4
    Join Date
    Jun 2012
    Posts
    2
    Quote Originally Posted by Pat Phelan View Post
    The easiest answer by far is to use P2V or a similar utility to simply "clone" the phiscal server as a virtual machine. This is fast, easy, and in most cases has no side effects... the client machines literally don't know that anything happened!

    -PatP
    I would agree except in this situation we are dealing with around a TB of data and we are being told by our server team it could take a whole weekend with an outage and that isn't an option for us. Also the source server is windows 2003 with SQL 2005 and we want Windows 2008 VM with SQL 2008.

  5. #5
    Join Date
    Feb 2004
    Location
    In front of the computer
    Posts
    15,579
    Provided Answers: 54
    Ok, then it is time for "Plan B"
    1. Build the VM as desired
    2. Put Source DB into Full recovery
    3. Do a full database backup
    4. Restore the full backup
    5. Do a Big Transaction Log dump
    6. Restore the Big Transaction Log dump
    7. Down the source server to users/applications
    8. Gather statistics/measurements/etc. to prove a good copy
    9. Do a Small Transaction Log dump
    10. Power down the source server
    11. Restore the Small Transaction Log dump
    12. Do any necessary testing/comparison using measures, etc from above
    13. Rename VM Server with source server's name
    14. Change VM IP Address to Source Server's IP
    15. Open beer, the database is moved!
    -PatP
    In theory, theory and practice are identical. In practice, theory and practice are unrelated.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •