Sunteți pe pagina 1din 5

Requirement:

We have a requirement to migrate our Storage from NetApp to HP as our


organization migrating all out storage to HP. Presently we have NetApp
storage .We have Standalone and cluster SQL servers.
The migration of standalone servers is easy but we had the challenge to
Migrate SQL server clusters.
We prepared and implemented the below plan to achieve our migration.

Solution:

Following steps needs to be executed to fulfill this requirement.

Cluster DB server Details:

Os: Windows 2008 R2 Enterprise Edition

SQL : SQL 2008 R2 Enterprise Edition

Before Migration:

Please note down the server configuration and also take the backup.

S.N
O Activity
Note the SQL server configuration and
1 windows details
2 Stop the application
3 Backup the All the databases
Backup Jobs , Login, Operators and linked
4 servers
5 Move all the disks and resources to Node1

Present the new LUNs

Please prepare the new LUNs from new storage with same size as old
storage, We have below LUNS in our production environment, hence we have
prepared the size LUNS from new storage.

Cluster Quorum
MSDTC Disk
SQL Data Disk
SQL Log Disk
SQL Temp DB Disk
Present the new LUNs:

Next we will add each of the new RDM Disks to our primary cluster node
and secondary cluster node, Your SAN admin will take care of this.

Preparing the new RDMs in Windows:

Note: these steps need to preform only one node 1

S.N
O Activity
1 Open Disk Management and Rescan the server for new disks
2 Right click on the first new drive and select Online
3 Right click again on the first new disk and select Initialize
Now right click in the right area of the first new disk and pick
4 Create Volume
Complete the new volume wizard and assign a temporary drive
5 letter
6 Repeat Step 2 5 for each new drive

Add the new drives to the cluster:

S.N
O Activity
1 Open Failover Cluster Manager
Expand out the cluster you are working on and select the Storage item in
2 the left tree.
3 On the right click Add a Disk
Make sure there are check marks beside all of the new drives you wish to
4 add as a cluster disk
5 Click OK
Verify that the new disks now appear under Available Storage in the middle
6 column

Now you have added new storage to our cluster, we have both HP and
NetApp storage to our cluster; we need to move our data from NetApp to
HP.
Move the Cluster Quorum Disk:

S.N
O Activity
1 Open the Cluster Manager MMC, expand the cluster.
In the left hand pane, click the cluster name at the top of the list. In
the actions pane go to More Options and select Configure Cluster
2 Quorum Settings
Follow through the wizard and the only thing you need to change is on
the Configure Storage Witness page. On this page, simply select the
3 check next to the new storage disk.
You have now successfully moved your cluster quorum to another
drive, but lets verify it. Open Windows explorer and view the new
drive. You should now see a folder called Cluster, which verifies the
4 move
If you want to reuse the old drive letter (Typically Q:), then right click
the old drive under the Available Storage group and select Change
Drive Letter. Now you can right click the old drive and select delete,
which will remove it from the Available Storage group in Cluster
5 Manager
In order to assign your new drive to the previously used drive letter,
6 simply right click it in Cluster Manager and select Change Drive Letter.
After changing the drive letter you now need to restart the cluster
7 service

Move MSDTC Disk:

S.N
O Activity
Open the Cluster Manager MMC, expand the cluster, and select
1
storage in the left hand pane.
You In Cluster Manager, expand your MSDTC group, right click the
2
MSDTC resource and select Delete.
In the actions pane on the right, click Add Resource and under More
3
Resources select Add Distributed Transaction Coordinator.
Double click the resource and go to the dependencies tab. Here you
4 need to make it dependent on both the network name and the new
cluster disk you just added. Click OK and bring the resource online
You have now successfully moved your cluster MSDTC to another
drive, but lets verify it. Open Windows explorer and view the new
5
drive. You should now see a folder called MSDTC, which verifies the
move.
The last thing you want to do is some clean up. Go back into Cluster
Manager and select the Storage node in the left hand pane. Under
6 your MSDTC group, right click the old MSDTC disk and select Remove.
This will remove the old storage drive from the cluster group and put
it back into the available storage group.
If you want to reuse the old drive letter (Typically M:), then right click
the old drive under the Available Storage group and select Change
7 Drive Letter. Now you can right click the old drive and select delete,
which will remove it from the Available Storage group in Cluster
Manager
In order to assign your new drive to the previously used drive letter,
simply right click it in Cluster Manager and select Change Drive
8 Letter. The old drive letter will now be available, so simply select it.
After changing the drive letter you now need to restart the MSDTC
group.

Move the SQL Data Disk/Log Disk/Temp DB Disk:

S.N
O Activity
1 Open Failover Cluster Manager
Expand out the cluster youre working on and select SQL Server under
2
Services and applications
3 Select Add storage from the menu on the right
4 Select the new drive from the list, and click OK
5 Take SQL offline
6 Verify that SQL Server and SQL Server Agent are offline
Open Windows Explorer and copy the SQL data from the old drive to the
7
new drive
Open Windows Explorer and copy the SQL Log from the old drive to the
8
new drive
In New Temp DB drive --Create the folder structure as it is in old Temp DB
9
drive
Back in Failover Cluster Manger right click on the old disk and select
10
Change drive letter
Make the old drive a temporary drive letter other than what it currently is,
11
Click OK
Next right click the new drive and select change drive letter, set the new
12
drives letter to what the old drive was for both Data /Log and Temp
Right click on SQL Server and select Bring this resource online, do the
13
same for SQL Server Agent
14 Do the failover to Second node and test the failover
15 Verify the all your databases and other components in SQL server
16 Now bring the SQL offline
Remove the Old storage drives from SQL dependencies and Windows
17
cluster
18 remove the old storage from server level
19 Bring the SQL online and check

Finally we done with storage migration from NetApp to HP..

S-ar putea să vă placă și