SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Moving LUN's from existing server to new cluster


Moving LUN's from existing server to new cluster

Author
Message
deep_kkumar
deep_kkumar
SSChasing Mays
SSChasing Mays (625 reputation)SSChasing Mays (625 reputation)SSChasing Mays (625 reputation)SSChasing Mays (625 reputation)SSChasing Mays (625 reputation)SSChasing Mays (625 reputation)SSChasing Mays (625 reputation)SSChasing Mays (625 reputation)

Group: General Forum Members
Points: 625 Visits: 756
Hi,

We are planning to move from standalone server to cluster environment. As our databases are of huge size, we are planning to move the LUN's from existing server to new cluster group for min. downtime. What precautions we need to follow in order to successfully finish this process ?

Thanks,
SpringTownDBA
SpringTownDBA
UDP Broadcaster
UDP Broadcaster (1.4K reputation)UDP Broadcaster (1.4K reputation)UDP Broadcaster (1.4K reputation)UDP Broadcaster (1.4K reputation)UDP Broadcaster (1.4K reputation)UDP Broadcaster (1.4K reputation)UDP Broadcaster (1.4K reputation)UDP Broadcaster (1.4K reputation)

Group: General Forum Members
Points: 1438 Visits: 1499
detach the database files before moving the luns.
JeremyE
JeremyE
SSCertifiable
SSCertifiable (5.8K reputation)SSCertifiable (5.8K reputation)SSCertifiable (5.8K reputation)SSCertifiable (5.8K reputation)SSCertifiable (5.8K reputation)SSCertifiable (5.8K reputation)SSCertifiable (5.8K reputation)SSCertifiable (5.8K reputation)

Group: General Forum Members
Points: 5795 Visits: 4088
I would take a backup of all the databases prior to the move in case something was to happen to the luns during the move.

I would also run select name, physical_name from sys.master_files and save it before detaching the databases because the drives/mount points might not come up the same on a different server and you will likely have to re-letter the drives.

Here is the process I follow:

1. Script out detach and attach statements
2. Run select name, physical_name from sys.master_files and save it for later
3. Run the detach script
4. Stop SQL server
5. Have the SAN admin offline the luns on the old machine
6. Have the SAN admin rezone the luns to the new machine
7. Have the SAN admin online the luns on the new machine
8. Re-letter the luns on the new machine
9. Run the attach script on the new machine
deep_kkumar
deep_kkumar
SSChasing Mays
SSChasing Mays (625 reputation)SSChasing Mays (625 reputation)SSChasing Mays (625 reputation)SSChasing Mays (625 reputation)SSChasing Mays (625 reputation)SSChasing Mays (625 reputation)SSChasing Mays (625 reputation)SSChasing Mays (625 reputation)

Group: General Forum Members
Points: 625 Visits: 756
Thanks a lot!!!!
Ferguson
Ferguson
Ten Centuries
Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)

Group: General Forum Members
Points: 1065 Visits: 109
And depending on the SAN and the SAN administrator, I would create some test LUN's and practice the move first. I've seen windows/SAN administrators get confused, and move a LUN and end up formatting it or otherwise fail to have it arrive with data intact.

It is VERY easy to move on most SAN's, do not misunderstand. But if they haven't done this before, have the windows/SAN guys practice first. Indeed, put a database there and you can practice also.

PS. Don't forget to move the log files also. Even if empty, it is simplier to attach them in place rather than trying to recreate them.



Perry Whittle
Perry Whittle
SSC Guru
SSC Guru (52K reputation)SSC Guru (52K reputation)SSC Guru (52K reputation)SSC Guru (52K reputation)SSC Guru (52K reputation)SSC Guru (52K reputation)SSC Guru (52K reputation)SSC Guru (52K reputation)

Group: General Forum Members
Points: 52703 Visits: 17672
Most SAN\NAS technologies will allow you to mask off LUNs from one host and attach to another. However, it may be better to mirror the current LUNs to new LUNs and then break once synchronised and create a copy of the data that way. Your storage admin should be able to offer you more help here.

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" ;-)
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search