1. Existing SnapDrive
2. Existing SnapManager for SQL
(Both Licensed)
SnapDrive 7.0 for Windows no longer requires that you have cluster credentials. You are required only to set up your virtual storage server credentials. You are required to have SnapRestore and FlexClone licenses before setting up your virtual storage server credentials.
My lab setup:
SnapManager for SQL Server NetApp, Inc. Version: 7.2.3.2841
SnapDrive Management SnapIn NetApp, Inc. Version: 7.1.5
SQL Server 2012 [11.0.5058]
7-mode : 8.1.4 [Simulator]
cDOT : 9.4 [Simulator]
Protocol : iSCSI via Microsoft Software Initiator
In order to migrate the Database LUNs from 7-mode to cDOT, you should have added both the storage systems to the SnapDrive console.
Make sure the LIF [192.168.0.214] is dedicated iSCSI Mgmt LIF for SVM, with data-protocol-access set to none.
Before Migration, create exactly similar (7-mode) LUNs via SnapDrive on cDOT filer to match with 7-mode LUNs.
Run SnapManager for SQL wizard - Run 'configure wizard:
To move the LUNs to cDOT, select the database and click 'Reconfigure' :
Next, select the existing LUN [Drive] and the LUN [Drive] to be migrated to:
Once done, go to next screen and do the same for 'Snapinfo' directory location, change it to the LUN on cDOT:
Just follow the prompts and it should do the trick:
Once it is successfully migrated, all the 'data' will be removed from the 7-mode LUNs [Drive], and if you go to the Windows Drive, they will be empty, all the data would have been moved to cDOT mapped LUNs Windows Drive.
Run a new Full backup, to make sure the migration has happened smoothly.
No comments:
Post a Comment