SQL 2008 R2 SP1 Cluster SAN Migration

Question

Dears,
I am doubting about procedure and steps that must be followed while doing SAN Migration for my cluster 2008 R2 SP1 SQL.
For me, I already did cluster Quorum SAN Migration, but I am doubting about all remaining steps such:
Some one told me about disk signatures, what should I do for this?
What are steps for MSDTC migration?
How to Migrate SQL Instance?
What about Master and other system databases?
What about Apps Database, logs, and temps?
What about below commands: FOR WHAT IT IS NEEDED?
ALTER DATABASE
msdb
MODIFY FILE ( NAME = MSDBData,
FILENAME = '
H:\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\
MSDBData.mdf' )
ALTER DATABASE
msdb
MODIFY FILE ( NAME = MSDBLog,
FILENAME = '
H:\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\
MSDBLog.ldf' )
SELECT name, physical_name AS CurrentLocation, state_desc
FROM sys.master_files WHERE database_id = DB_ID(N'msdb');
ALTER DATABASE
model
MODIFY FILE ( NAME = modeldev,
FILENAME = '
H:\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\
model.mdf' )
ALTER DATABASE
model
MODIFY FILE ( NAME =
modellog,
FILENAME = '
H:\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\
modellog.ldf' )
Please help on this coz I am afraid about my information!

Answer 1

Some one told me about disk signatures, what should I do for this?
If you can present in disks from both SANs at the same time then this shouldn't be an issue. At a high-level you can add the new disks in and remove the old ones from the cluster when you're finished with them. The disks are just seen as new disks...not swapped
ones.
What are steps for MSDTC migration?
- Personally I've simply deleted and re-created the MSDTC, there might be a nicer way to do this, but re-creating it works. 
How to Migrate SQL Instance?
- You mean elements that are on a SAN attached drive that aren't part of the cluster? You can stop the instance and copy the files (use
xcopy to preserve permissions), Then swap the drive letters around & restart the instance. 
What about Master and other system databases?
For system databases I would
- bring the new disk into the cluster, give it a temporary drive letter, make sure sql server has a dependency on it (look at how the current drives are setup)
- stop the services
- copy the folders/files to the new drive using xcopy preserving permissions
- give the current drive an unused drive letter (via cluster manager)
change the new drive letter to match the original drive (via cluster manager)
- remove the old drive (remove dependencies before doing this)
- bring the server online
What about Apps Database, logs, and temps?
-You can do this 'online' while the sql server is running, just bring the new disk into the cluster and following the Microsoft recommended approach outlined
here
What about below commands: FOR WHAT IT IS NEEDED?
- that's for msdb and model, you'll have already handled those databases with the other system dbs.