My Scripts and Tips » SQL Server http://www.tipsandscripts.net Various things I've found useful in my travels Mon, 09 Aug 2010 09:23:50 +0000 en hourly 1 http://wordpress.org/?v=3.0.1 Moving MS SQL Server 2000 to new hardware http://www.tipsandscripts.net/archives/46 http://www.tipsandscripts.net/archives/46#comments Tue, 28 Apr 2009 10:24:21 +0000 admin http://www.tipsandscripts.net/?p=46 We had the fibre channel cards on our SQL Server fail on us. We had been planning to replace this server, and the storage array it was attached to, so we decided to bring that forward rather than repairing the server. Note we also had a copy of the server running in an isolated virtual machine for testing. All of our databases, including master.mdf were on a LUN on the storage array (previously mounted as D:).

Here are the steps we took in migrating our server:

  1. Installed Windows and drivers on the new server.
  2. Modified the zones and mounted the LUN containing the SQL databases on the existing storage array to the new server (E:).
  3. Created the required LUN on the new storage array and mounted on the new server (D:).
  4. Used robocopy E:\ D:\ /MIR /R:0 /W:1 to copy the databases from the old LUN to the new LUN.
  5. Unmounted the old LUN and undid the zone changes.
  6. Moved everything on D: to a temporary directory on D: (so they wouldn’t get overwritten during the install of SQL Server 2000). Note, move the files to the same filesystem so everything happens instantly (i.e. not a copy).
  7. On the old server, exported HKLM\Software\Microsoft\MSSQL from the registry.
  8. Copied the SID from the old server to the new server using newsid.exe (I had a friend run into a problem when restoring databases to a new server during a DR test. Because the SID of the new server was different to the old server security in the database didn’t work correctly. I assume this was because they were using local Windows accounts. ) I don’t know if we needed to do this step, but we did it just in case.
  9. Removed the old server from the domain and renamed it. Changed its IP address.
  10. Renamed the new server to the original name of the old server and added it to the domain. Set its IP address to the one previously used on the old server.
  11. Installed SQL Server 2000. During the installation we specified the same paths as had been used on the old server (D:\Databases).
  12. Installed SQL Server 2000 service packs.
  13. Shut down the SQL services.
  14. On the new server, exported HKLM\Software\Microsoft\MSSQL from the registry (just in case things went wrong).
  15. On the new server, imported HKLM\Software\Microsoft\MSSQL that had been exported from the old server.
  16. Renamed the directory containing the new master.mdf (D:\Databases to D:\Databases.freshinstall).
  17. Moved the directories in the temporary directory back to their original location in D:.
  18. Restarted the SQL services.

Everything still seems to be working so I guess it worked. Luckily we weren’t using local accounts (only domain accounts) so we didn’t have to try to recreate the original accounts (which might have caused an issue with different account SIDs).

]]> http://www.tipsandscripts.net/archives/46/feed 0