March 4, 2013 at 5:45 pm
At the office, we have a 2-nodes cluster configuration running a SQL Server instance on each node (active/active). We need to move all of the data in the current SAN drive (M:) to another (N:), so we're able to decomission the current SAN.
-Current folder structure----------------
Disk M: (current SAN drive)
...|-DATA
......|-all the user databases files
...|-MSSQL10_50.INSTANCE_A
......|-MSSQL
..........|-Backup
..........|-DATA
.............|-all system databases files (master, model, msdb)
..........|-FTData
..........|-JOBS
..........|-Log
..........|-repldata
Disk N: (new SAN drive)
------------------------
We had scheduled a day to make the change on one of the nodes, but I came to notice that the SQL Server instance folder structure (MSSQL10_50.INSTANCE_A\MSSQL and its subfolders; Backup, DATA, JOBS, Log, etc) which contains the instance system databases currently resides in the drive we want to remove... so I want to know... is there a way to make the move of the whole folder structure to the new SAN without removing the cluster configuration and create it all over again?.
First idea that came to my mind (a naive one perhaps) was that if we stop the SQL Server instance, copy to the new SAN all of the user databases files and the SQL Server instance folder structure containing the system databases and other files, and once the copy finishes, change the new SAN drive letter to that of the old SAN drive, so once that the SQL Server instance starts, it would read the files from the "same path" as if nothing had been changed. I don't really know if this could be performed without causing the cluster to malfunction or something going wrong... i'm not very experienced in the field of cluster administration, this is the first time i've got to deal with an issue that affects such an environment. I hope someone would give me some clue or piece of advice about what we want to do in our current scenario.
Help is much appreciated, thanks in advance.
March 4, 2013 at 10:33 pm
Create luns and vloume of the new san disk then try to move the database files and other dependecy one by one to the new san disk. Once done with it then remove the old san disk.
Found one similar discussion please check it http://social.msdn.microsoft.com/Forums/en-US/sqldisasterrecovery/thread/9e2503f7-1c8c-425a-87fb-b03aa0ece231
"More Green More Oxygen !! Plant a tree today"
March 6, 2013 at 10:46 am
Hello, Minaz... thank you for your quick reply. I checked the link you provided and the problem exposed there is aparently the same as ours, and the solution steps mentioned are more or less (if not the same) what I had thought could be done. We're going to set a small environment so we can test if it works.
Thanks again for taking time to answer!
March 6, 2013 at 9:26 pm
hmm. Is it possible to have two sans attached to box and configure it so the cluster also could see it. The second san will be the replica of 1st one only we need the sql cluster to recognize and get connect .
Once done with your testing please share this is will be good learning for all of us.:-)
"More Green More Oxygen !! Plant a tree today"
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply