Understanding the Configuration Wizard

The primary function of the Configuration Wizard is to migrate SQL Server databases to Data ONTAP LUNs so that the databases can be backed up and restored using SnapManager. For more information, go to any of the following topics:

What the Configuration Wizard does

The Configuration Wizard enables you to move your SQL Server databases in the following ways.

Type of database migration	Purpose
From local disk to LUN	To enable management by SnapManager
From LUN to LUN	If resource management issues require this
From LUN to local disk	If no longer managed using SnapManager

You can choose whether you want to verify your migrated databases and, if you are migrating your databases to LUNs, whether you want to delete your original databases after a successful migration.

The Configuration Wizard also guides you through several application settings. These settings include setting up the SnapInfo directory, enabling notification of SnapManager events using e-mail, and enabling notification of SnapManager events using the storage system Syslog or the AutoSupport feature.

What the Configuration Wizard does not do

Do not use the SnapManager Configuration Wizard to migrate replicated databases or databases used in the replication process. For information about configuring replication-specific databases, see your Microsoft SQL Server documentation.

When to use the Configuration Wizard

You can use the Configuration Wizard in the following situations.

For initial configuration

In order to use SnapManager to back up and restore SQL Server databases, you must use the SnapManager Configuration Wizard to migrate those databases from your SQL servers to the LUNs you configured on your storage system with SnapDrive. The Configuration Wizard also sets up a SnapInfo directory that SnapManager uses to store information about the backup sets and the backed-up transaction logs.

To view or change the database configuration

After the initial configuration, you can rerun the Configuration Wizard at any time to review or make changes to your SQL Server database configuration.

To validate the database configuration

If you add more databases or move databases to different LUNs without using SnapManager, you must run the Configuration Wizard to ensure that the databases are stored in valid locations and to create a mapping between those databases and their respective SnapInfo subdirectories.

Configuration Wizard screens

Brief descriptions of the Configuration Wizard screens are provided in the following paragraphs.

Database Verification Server and Account Authentication

Use this screen to specify the SQL Server you want used to verify the SQL Server databases in your SnapManager backups.

Where to Move Databases

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

Number of Databases that Can be Backed Up Concurrently

Use this screen to specify the maximum number of databases that can be backed up concurrently and to choose whether you want to view and optionally change the SQL Server "maximum worker threads" parameter for each SQL Server instance.

Modify SQL Server Max Thread Option

Use this screen to view and optionally change the maximum number of worker threads for each SQL Server instance.

Note
If you choose to change the maximum number of worker threads, the affected SQL Server instances will be rebooted after you complete the Configuration Wizard sequence.

SnapInfo Directory Type

Use this screen to choose how you want the SnapInfo directory or directories configured:

To specify a single SnapInfo directory for all SQL Server instances and their associated databases, select the Single SnapInfo Directory option. After you click Next, the Specify a Single SnapInfo Directory screen appears.
To specify multiple SnapInfo directories, select the Advanced SnapInfo Directories option. After you click Next, a sequence of screens appear:
- Where to Put the Default SnapInfo Directory for Each SQL Server Instance
  Use this screen to specify a default SnapInfo directory for all the databases owned by a specific SQL Server instance.
- 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 this screen to specify a common SnapInfo directory location for those databases.
- Where to Put the SnapInfo Directory for Each Database
  If you want the SnapInfo directory for an individual database to be stored on a LUN other than in the default location for that SQL Server instance, use this screen to specify that information.

Database Migration Options

Use this screen to select options for the database migration:

Run the DBCC command to verify your migrated databases.
Delete the original database files after the migration finishes successfully.
Run UPDATE STATISTICS on tables before detaching the databases.

Add Microsoft iSCSI Service Dependency

Use this screen to specify, on a per-instance basis, whether the Microsoft iSCSI service should be a dependency for the Microsoft SQL Server services.

Configure Automatic E-mail Notification

Use this screen to configure automatic SMTP e-mail notification for event notification.

Configure SnapManager Event Logging to Filer Syslog and AutoSupport

Use this screen to enable Syslog (storage system event log) support and to enable AutoSupport for SnapManager.

Settings configurable only with the Configuration Wizard

The following table lists SnapManager database management settings that can be configured or changed only through the Configuration Wizard. For each setting, the table lists the name of the corresponding screen in the Configuration Wizard.

SnapManager setting	Configuration Wizard screen
Database-LUN mapping	Where to Move Databases
Maximum worker threads for each SQL Server instance	Modify SQL Server Max Worker Thread Option
SnapInfo directory location	SnapInfo Directory Type Single SnapInfo Directory Advanced SnapInfo Directories
Migration-specific options: Run DBCC before migration, after migration, or both? Delete original databases after successful migration?	Database Migration Options
Microsoft iSCSI Service as a dependency	Add Microsoft iSCSI Service Dependency