Migrating SQL Server databases to LUNs

If you have not already done so, start the SnapManager for SQL Server application. To do this, go to the Windows Start menu and select Program Files > SnapManager for SQL Server.

Result

SnapManager for SQL Server main window opens.

Connect to SQL Server

If you want to view or change the SQL Server managed by SnapManager, do this using the Connect to SQL Server dialog box. To open the dialog box, go to the SnapManager menu bar and select Action > Connect to a different SQL Server.

For more information, see Appendix C, Configuring SnapManager Application Settings.

Start the Configuration Wizard

Start the Configuration Wizard.

• From the SnapManager Wizards tab, click Configuration Wizard.
• From the SnapManager menu bar, select Wizard > Configuration Wizard.

Result

The Configuration Wizard is launched and the Welcome screen appears.

Welcome

At the Configuration Wizard Welcome screen, click Next.

Result

The Database Verification Server and Account Authentication screen appears.

Database Verification Server and Account Authentication

Use the Database Verification Server and Account Authentication screen to specify the SQL Server to be used to perform SQL Server database verification and account authentication.

Note
For optimal performance, use an SQL Server that is different from the verification 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. For a detailed description of these specifications, see Using the Database Verification Server and Account Authentication screen.
• If you want to specify the database verification server later, select the option labeled "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.

Click Next.

Result

The Where to Move Databases screen appears.

Where to Move Databases

Use the Where to Move Databases screen to specify the databases (or individual data files or transaction log files) you want to move and where you want them moved.

For more information about any LUN in the Disk List, move the mouse over the LUN name. This causes a tooltip to appear and display the IP address or host name of the storage system and the name of the volume that houses the LUN.

Note
If the SnapManager host system is running SQL Server 2005 and the Disk List does not display any LUNs, be sure that the SQL Browser service was configured to start automatically.

From this screen, you can do any of the following:

• Migrate databases from local disk to LUNs. See Migrating SQL Server databases from local disk to LUNs.
• Move databases from one LUN to another. See Moving SQL Server databases to different LUNs.
• View the path of a database that resides on a LUN. See Viewing the full path for a database on a LUN.

Click Next.

Result

The Number of Databases that Can be Backed Up Concurrently screen appears and displays the current value.

Number of Databases that Can be Backed Up Concurrently

Use the Number of Databases that Can be Backed Up Concurrently screen to change the maximum number of databases that can be backed up concurrently.

1. If you need to change the maximum number of databases that can be backed up concurrently for each SQL Server instance, change the value in the "Maximum databases..." box. The default setting is 255 databases.
2. If you also want to view and optionally change the maximum number of SQL Server worker threads for any SQL Server instance, select the Modify SQL Server "Maximum Worker Threads" Parameter option. This option is deselected by default.

For more detailed information, see Using the Number of Databases that Can Be Backed Up Concurrently screen.

Click Next.

Result

The next screen that appears depends on whether you chose to modify the SQL Server maximum number of worker threads allowed.

If...

Then...

You did not select the Modify SQL Server "Maximum Worker Threads" Parameter option

The SnapInfo Directory Type screen appears. Go to Step 13.

You selected the Modify SQL Server "Maximum Worker Threads" Parameter option

The Modify SQL Server Maximum Worker Threads Parameter screen appears. Go to Step 11.

Modify SQL Server Maximum Worker Threads Parameter

Use the Modify SQL Server Maximum Worker Threads Parameter screen to specify whether you want to modify the maximum number of worker threads for any SQL Server instance. You have the following options:

• Leave the current maximum number of worker threads unchanged for all SQL Server instances
• Apply all of the recommended new values displayed in the New Max Worker Threads column
• Edit one or more of the recommended new values before applying the changes

For more detailed information, see Using the Modify SQL Server Maximum Worker Threads Parameter screen.

Note
If you choose to change the maximum number of worker threads for any SQL Server instances, those instances will be restarted when you click Finish in the Completing the Configuration Wizard screen.

After you have finished viewing and optionally changing this SQL Server parameter, click Next.

Result

The SnapInfo Directory Type screen appears.

SnapInfo Directory Type

Use the SnapInfo Directory Type screen to choose how you want the SnapInfo directory or directories configured.

Note
By default, the Single SnapInfo Directory option is selected. If SnapManager was previously configured with multiple SnapInfo directories, the SnapInfo Directory Type screen is displayed with the Advanced SnapInfo Directories option preselected.

If you want to...

Then do this...

Create one SnapInfo directory for all SQL Server instances and their associated databases (including multiple databases sharing one or two LUNs)

Go to Step 14.

Create a different SnapInfo directory for each SQL Server instance, or for multiple databases sharing one or two LUNs, or for each database in an SQL Server instance

Go to Step 18.

Move multiple SnapInfo directories to a single directory

Go to Step 18.

Specify a Single SnapInfo Directory

Select the Single SnapInfo Directory option, then click Next.

Result

The Specify a Single SnapInfo Directory screen appears.

Note
For more information about any LUN in the Disk List, move the mouse over the LUN name. This causes a tooltip to appear and display the IP address or host name of the storage system and the name of the volume that houses the LUN.

Use the Specify a Single SnapInfo Directory screen to specify how you want to create a single SnapInfo directory for all your databases. By default, the SnapInfo directory name is SMSQL_SnapInfo. However, you can specify a different SnapInfo directory path by modifying the information in the Result SnapInfo Directory box.

For more detailed information, see Using the Specify a Single SnapInfo Directory screen.

Result

The Result SnapInfo Directory field displays the mount point for the newly specified SnapInfo directory.

Click Next.

Result

The Database Migration Options screen appears.

Proceed to Step 25.

Where to Put the Default SnapInfo Directory for Each SQL Server Instance

Select the Advanced SnapInfo Directories option, then click Next.

Result

The Where to Put the Default SnapInfo Directory for Each SQL Server Instance screen appears.

Note
For more information about any LUN in the Disk List, move the mouse over the LUN name. This causes a tooltip to appear and display the IP address or host name of the storage system and the name of the volume that houses the LUN.

Use the Where to Put the Default SnapInfo Directory for Each SQL Server Instance screen to create a default SnapInfo directory for all the databases owned by a specific SQL Server instance.

In subsequent screens, you will have the opportunity to override this setting for specific cases:

• Multiple databases that share one or two LUNs
• A single database

  Note
  You can also use this screen to change from multiple SnapInfo directories to a single SnapInfo directory.

By default, the SnapInfo directory name is SMSQL_SnapInfo. However, you can specify a different SnapInfo directory path by using the Default SnapInfo Property dialog box.

For more detailed information, see Using the Where to Put the Default SnapInfo Directory for Each SQL Server Instance screen.

Click Next.

Result

The Where to Put the Default SnapInfo Directory for LUNs Shared by Multiple Databases screen appears.

Note
For more information about any LUN in the Disk List, move the mouse over the LUN name. This causes a tooltip to appear and display the IP address or host name of the storage system and the name of the volume that houses the LUN.

Where to Put the Default SnapInfo Directory for LUNs Shared by Multiple Databases

If you have multiple databases that reside on one or two LUNs, use the Where to Put the Default SnapInfo Directory for LUNs Shared by Multiple Databases screen to specify a common SnapInfo directory location for those databases.

By default, the SnapInfo directory name is SMSQL_SnapInfo. However, you can specify a different SnapInfo directory path by using the Default SnapInfo Property dialog box.

For more detailed information about using the Where to Put the Default SnapInfo Directory for LUNs Shared by Multiple Databases screen, see Using the Where to Put the Default SnapInfo Directory for LUNs Shared by Multiple Databases screen.

Click Next.

Result

The Where to Put the SnapInfo Directory for Each Database screen appears.

Note
For more information about any LUN in the Disk List, move the mouse over the LUN name. This causes a tooltip to appear and display the IP address or host name of the storage system and the name of the volume that houses the LUN.

Where to Put the SnapInfo Directory for Each Database

If you want to place the SnapInfo directory for an individual database on a LUN other than in the default location for that SQL Server instance, use the Where to Put the Default SnapInfo Directory for Each Database screen to select the database and specify the SnapInfo directory location.

By default, the SnapInfo directory name is SMSQL_SnapInfo. However, you can specify a different SnapInfo directory path by using the Default SnapInfo Property dialog box.

For more detailed information about using the Where to Put the Default SnapInfo Directory for Each Database screen, see Using the Where to Put the SnapInfo Directory for Each Database screen.

Click Next.

Result

The Database Migration Options screen appears.

Note
The next time you run the Configuration Wizard, the Advanced SnapInfo Directories option will be preselected (in the SnapInfo Directory Type screen) if the previous configuration operation was performed with two or more SnapInfo directories.

Database Migration Options

Use the Database Migration Options screen to select options for the database migration:

• When you want to run the DBCC command to verify your migrated databases
• Whether you want to delete the original database files after the migration finishes successfully
• Whether you want to run UPDATE STATISTICS on tables before detaching the databases

For a more detailed description, see Using the Database Migration Options screen.

Click Next.

Result

The next screen that appears depends on whether SnapManager is installed in an MSCS environment or on a stand-alone Windows host.

If...

Then...

You are configuring SnapManager in a MSCS environment -or- the Microsoft iSCSI service is not running on the Windows host system

The Configure Automatic Event Notification screen appears. Go to Step 29.

You are configuring SnapManager on a stand-alone Windows host system

The Add Microsoft iSCSI Service Dependency screen appears. Proceed to Step 27.

Add Microsoft iSCSI Service Dependency

Use the Add Microsoft iSCSI Service Dependency screen to optionally configure the Microsoft iSCSI service as a dependency for the Microsoft SQL Server services on a particular SQL Server instance.

For each SQL Server instance, if you are migrating databases to LUNs accessed using the iSCSI protocol, then select the option to ensure that the Microsoft iSCSI service will be added as a dependency for the Microsoft SQL Server services in that instance. This will prevent Microsoft SQL Server from starting before the Microsoft iSCSI service is ready to accept connections.

Note
You can click Select All to select every option in the list. You can click Unselect All to clear every option.

Click Next.

Result

The Configure Automatic Event Notification screen appears.

Configure Automatic Event Notification

Use the Configure Automatic Event Notification screen to configure the automatic event notification options for SnapManager:

• Configure automatic SMTP e-mail notification for event notification.
• Enable Syslog (storage system event log) support.
• Enable AutoSupport for SnapManager.
• Limit event logging to failure events

  Note
  NetApp strongly recommends that you enable the automatic event notification options.

After you complete the Configuration Wizard, you can also view or change these settings by selecting Options > Notification Settings to access the Auto Notification Settings dialog box. For more detailed information, go to Event notification options.

Result

The Completing the Configuration Wizard screen appears.

Completing the Configuration Wizard

In the Completing the Configuration Wizard screen, click Finish to close the Configuration Wizard so that you can begin the actual database configuration process.

Note
If you chose to change the maximum number of worker threads for any SQL Server instances (specified in the Modify SQL Server Maximum Worker Threads Parameter screen), those instances will be restarted when you click Finish.

Result

The Configuration Wizard closes, and the Configurator Status dialog box appears.

Configurator Status

To migrate your databases to the LUNs you specified and to set up the SnapInfo directory as specified, click Start Now.

Result

The Configuration Wizard moves the databases and logs to their specified LUNs and displays a task check-off list.

• Migrating SQL Server databases causes them to be taken offline during the copy operation.
• In a Windows cluster, if you migrate a database file to a Data ONTAP LUN that does not have dependency set on the SQL Server cluster resource, SnapManager adds the LUN dependency on the cluster resource.

  Note
  It is a Windows cluster requirement that a resource must be taken offline prior to adding a dependency to it.

  In order to add this LUN dependency on the cluster resource, SnapManager places all resources directly or indirectly dependent on that LUN into an offline state, adds the dependency on the cluster resource, then brings the resources back online.

• If a database copy or a database attach fails, SnapManager attaches the original database file to the SQL Server.

When the migration finishes successfully, SnapManager displays a message box. This message also reminds you to make a backup immediately.

Click OK to close the message box.

Back up your databases immediately.

Any time you use the Configuration Wizard to move data from one drive to another, backups performed prior to the move become invalid. After you migrate your databases to a new LUN, perform an immediate backup.