Migrating using the Configuration wizard
To migrate your SQL Server databases from local disks to LUNs, SMB shares, or VMDKs or from one LUN, SMB share, or VMDK to another, complete the steps in the following table.
Attention: After an SQL Server database has been migrated using SnapManager, do not use a utility outside of SnapManager to move any other data in the SQL Server system. Doing so might prevent SnapManager from functioning correctly.
Before you begin
• The name of databases must not include a bracket ( [ or ] ).
• If you want to migrate databases using any LUN or VMDK configuration, you must have enabled the unrestricted database layout option. For details about the unrestricted
database layout option, see Enabling SnapManager to allow databases on any LUN or VMDK configuration on page 294.
Step Action
1 If you have not already done so, start the SnapManager application. To do this, go to the Windows Start menu and select Program Files > NetApp > SnapManager for SQL Server.
Result: The SnapManager for SQL Server console root opens.
2 Add a server from the Actions pane by clicking Add Servers to be Managed, selecting a server from the list, and clicking Add.
You can also use the Browse option to select a server.
Note: You can also add server instances using this option, because there can be many server instances within a domain or a single physical server.
For more information, see Starting SnapManager for the first time after installation on page 60.
3 In the left pane, double-click the name of the SnapManager host that you want to connect to.
Step Action
4 The Configuration wizard is launched and the Welcome screen appears. Click Next.
Result: If you cleared the Use control-file option, the Database Verification Server and Account Authentication screen appears.
5 Use the Database Verification Server panel to specify the SQL Server to be used to perform SQL Server database verification and account authentication; then click Next.
Note: For optimal performance, use an SQL Server that is different from the source (production) server.
If you want to specify the database verification server now, select an SQL Server in the Verification Server list and choose the security authentication method to be used to connect to that server. If you choose SQL Server authentication, you must also specify the login name and password.
If you want to specify the database verification server later, select the option Select a verification server later using the Options menu. Later, when you are ready to select a database verification server, you can do so by selecting Options > Database
Verification Settings to open the Verification Settings dialog box. For a detailed description of the Verification Settings dialog box, see Database integrity verification options on page 294.
You can set up a different verification server for each SQL Server host in the SnapManager GUI.
6 In the Database Selection panel, do the following and then click Next:
• In the Database Selection pane, select the database that you want to migrate.
• In the Disk Selection pane, select a location for the database.
Note: A VMDK that is a system drive appears in the Disk Selection pane.
• Click <=>.
You can view the changes that you made in the Database Location Results pane.
7 Complete the remaining wizard pages.
8 Click Finish.
Moving multiple SnapInfo directories to a single SnapInfo directory
Moving multiple SnapInfo directories to a single SnapInfo directory
If you previously configured multiple SnapInfo directories, you can rerun the Configuration wizard to move them to a single SnapInfo directory.
The Configuration wizard enables you to create multiple SnapInfo directories in the following ways:
• A default SnapInfo directory per SQL Server instance
• A separate SnapInfo directory for multiple databases on one or two LUNs, SMB shares, or VMDKs
• A different (non-default) SnapInfo directory for a database in an instance
If you currently have multiple SnapInfo directories, you can choose to combine them into a single directory.
To change your configuration from multiple SnapInfo directories to a single SnapInfo directory for all SQL Server instances and associated databases, complete the following steps.
Step Action
1 Start the Configuration wizard, then step through the following screens without specifying any configuration changes:
• Verification Settings and Account Authentication
• Database Selection
2 In the SnapInfo Settings screen, select the Single SnapInfo Directory option, and then click Next.
Result The Specify a Single SnapInfo Directory screen appears. Note that, in the Current SnapInfo Directory list, all the current SnapInfo directories are selected by default.
3 In the Available Disks window, select the LUN, SMB share, or VMDK to which you want to move all the SnapInfo directories.
4 Click the move (<=>) button.
Result The Result SnapInfo Directory box displays the path for the SnapInfo directory.
Note that the default directory name is SMSQL_SnapInfo.
5 If you want to specify a different location or name, modify the information in the Result SnapInfo Directory box.
Note: The Configuration wizard will allow you to create the SnapInfo directory only in valid locations.
6 Step through the remaining screens of the Configuration wizard without specifying any further configuration changes:
• Database Migration Options
• Add Microsoft iSCSI Service Dependency
• Configure Automatic Event Notification
7 In the Completing the Configuration Wizard screen, verify the changes you specified, and then click Finish.
Step Action
8 In the Configurator Status dialog box, click Start Now to close the dialog box, and then begin the Configuration wizard tasks you specified.
9 When a message box appears and notifies you that the configuration changes were completed successfully, click OK to close the message.
10 Click Close to close the Configurator Status dialog box.