Windows 2008 R2 Cluster - migrating data to new SAN storage - Detailed Steps?

Question

We have a project where some network storage is falling out of warranty and we need to move the data to new storage.  I have found separate guides for moving the quorum and replacing individual drives, but I can't find an all inclusive detailed step
by step for this process, and I know this has to happen all the time.
What I am looking for is detailed instructions on moving all the data from their current san storage to new san storage, start to finish.  All server side, there is a separate storage team that will present the new storage.  I'll then have to install
the multi-pathing driver; then I am looking for a guide that picks up at this point.
The real concern here is that this machine controls a critical production process and we don't have a proper set up with storage and everything to test with, so it's going to be a little nerve racking.
Thanks in advance for any info.

Answer 1

I would ask Hitachi.  As I said, the SAN vendors often have tools to assist in this sort of thing.  After all, in order to make the sale they often have to show how to move the data with the least amount of impact to the environment.  In fact,
I would have thought that inclusion of this type of information would have been a requirement for the purchase of the SAN in the first place.
Within the Microsoft environment, you are going to deal with generic tools.  And using generic tools the steps will be similar to what I said. 
1. Attach storage array to cluster and configure storage.
2. Use robocopy or Windows Server Backup for file transfer.  Use database backup/recovery for databases.
3. Start with applications that can take multiple interruptions as you learn what works for your environment.
Every environment is going to be different.  To get into much more detail would require an analysis of what you are using the cluster for (which you never state in either of your posts), what sort of outages you can operate with, what sort of recovery
plan you will put in place, etc.  You have stated that your production environment is going to be your lab because you do not have a non-production environment in which to test it.  That makes it even trickier to try to offer any sort of detailed
steps for unknown applications/sizing/timeframes/etc.
Lastly, the absolute best practice would be to build a new Windows Server 2012 R2 cluster and migrate to a new cluster.  Windows Server 2008 R2 is already out of mainstream support. That means that you have only five more years of support on your
current platform, at which point in time you will have to perform another massive upgrade.  Better to perform a single upgrade that gives you a lot more length of support.
. : | : . : | : . tim