Sqlservercluster replacing the instance root directory

The company has a SQL Server cluster storage is HP P2000, because the HP P2000 offline need to transfer the entire database storage to the Dell storage, the user database Umount and then copy the files to the new storage and then attach,instance The root directory disk needs to be replaced on Windows cluster, as follows:

1. Mount the new disk to the server first (a series of operations such as on-line, initialize, etc.)

Note: do not add to Windows cluster

2. Offline the database service to avoid changes to the file during the move of the data file.

3. On-line old data disk Y: (i.e. on-line system database disk)

4. Run the Robocopy command to copy the data file from the Y: disk to the new disc Z: (Please copy the system database to the new disk separately)

Robocopy<source path><destination path>/copyall/e/dcopy:t/B/R:3/W:1/LOG:C:\ROBOCOPY-LOG.TXT/NP

*/E for Recursive directories

*/copyall to preserve permssions

*/dcopy:t Copy all Directorys ' timestamps (your need to remove this parameter on Server 2003, it's only supported after 2 008)

*/b to use Backup mode

*/r:3 to retry 3 times fail

*/w:1 to wait 1 second when retry

*/log:c:\robocopy-log.txt Enable Logging

*/NP Specifies that the progress of the copying operation (the number of files or directories copied so far) won't be Displayed.

5. Put the old disk y: offline:

6. Right-click More Actions ... Click Repair:

7. In the pop-up repair a disk resource window, select the new data disk and click OK. (The drive letter is not shown here, so you can see the disk information of the z: Disks in Disk Management.) ）

8. After the Repair is complete, the new disk can be online.

9. Please check the current online letter, if it is the same as the original drive, then do not need to change, if different from the original drive, you need to modify the disk symbol for the original y:

10. At this point, you can unblock the database startup mode and bring the database online.

Fallback method:

1. Please bring SQL Server resources back offline
2. will need to rollback the disk resources offline

3. Repair again, replace with the old disk

4. Check the drive letter after online and always ensure that the drive letter used by SQL Server is unchanged

5. Bring the SQL Server resource online

Sqlservercluster replacing the instance root directory