April 5, 2010 at 12:04 pm
We are planning on moving a SQL 2000 Server to a new physical location. SQL Server was installed on Drive D:. Therefore the system databases and some user database are on drive D:. Drive D: is on SAN storage.
Drive C:\ (System Drive is local disks) (No SQL)
Drive D:\ SAN storage (SQL installed here and some user databases)
Drive E:\ SAN storage
Drive F:\ SAN storage
The server name will remain the same, but the IP will change. We plan on entering a alias in DNS so users who connect using the name will still be able to.
The move as planned is to:
1. Backup everything.
2. Before shut down change SQL services to start manually.
3. Shutdown the server.
4. Start the SAN copy to the new datacenter location.
5. Remove the server from the rack and move to new Datacenter.
6. Rack the moved server in new datacenter.
7. When SAN copy complete, start the server.
8. Make sure SAN attached with Same Drive letters.
9. Change the IP,
10. Start SQL.
Will this work?
Are there any gotcha's we are missing?
Does SQL just need the same drive letters as before or does it keep a binary identifier of drives?
Thanks in advance for any replies.
April 5, 2010 at 12:13 pm
It should work with no problems. Provided the disks are presented to SQL as they look today. The identifier is only a worry in a clustered configuration, and at that, they are only an issue to setting up the cluster.
I don't see any issues with your game plan. We did the same thing several years ago when migrating to a new DC.
/* ----------------------------- */
Tochter aus Elysium, Wir betreten feuertrunken, Himmlische, dein Heiligtum!
April 5, 2010 at 12:33 pm
I agree with Gregory. This approach should work just fine.
I assume that when you say "backup everything" you mean you are taking a physical backup of the whole server - not only the database, is that correct?
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.April 5, 2010 at 12:33 pm
Hi, thank you for the quick reply.
What do you mean by drives "presented the same way as today"?
Do you mean C, D, E and F? And/or with volume name also?
ie. actually doing a list in explorer in my computer shows LUN25 (D:), LUN26 (E:) and LUN52 (F:).
I am not a Systems Administrator who will be performing the SAN COPY or presenting the LUNS. The more I know the better.
So, Does SQL only need to see the drive letters or drive letter and volume name too?
thanks again,
April 5, 2010 at 12:36 pm
Yes, even though we are just physically moving the server "as is" we will have a backup of the server file systems and databases.
April 5, 2010 at 12:37 pm
SQL does not care one lick what the volume is named. You can go in right now and rename it and won't see any difference.
Since the C drive seems to be OS only, and SQL is on the other drives, provided that the drive letters remain the same, you'll be OK.
When you bring the server back online, everything should come up just the same (except for the different IP address), and the IP address should not be an issue (unless there are some poorly written apps that only connect via IP)
/* ----------------------------- */
Tochter aus Elysium, Wir betreten feuertrunken, Himmlische, dein Heiligtum!
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply