About this section The primary function of the Configuration Wizard is to migrate SQL Server databases to 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” on page 123
◆ “What the Configuration Wizard does not do” on page 124
◆ “When to use the Configuration Wizard” on page 124
◆ “Settings configurable only with the Configuration Wizard” on page 126
◆ “Settings configurable only with the Configuration Wizard” on page 126
What the Configuration Wizard does
The Configuration Wizard enables you to move your SQL Server databases in the following ways:
From local disk to LUN: To enable management by SnapManager.
◆ If databases need to be moved, the wizard dismounts the databases, moves the database and transaction log files to the selected LUN, and remounts the databases.
Note
SnapManager takes databases offline during the move operation.
◆ The wizard creates a SnapInfo directory that SnapManager uses to store information about the backup sets and the backed-up transaction logs.
◆ The wizard disables circular logging for all databases that are moved to a LUN, to enable up-to-the-minute recovery of those databases.
◆ The wizard also guides you through several application settings. These settings include enabling notification of SnapManager events using e-mail, and enabling notification of SnapManager events using the storage system Syslog or the AutoSupport feature.
From LUN to LUN: If resource management issues require this. For example, consolidating SQL server on another storage system.
From LUN to local disk: Even if the databases are no longer managed using SnapManager, you can migrate them back to your local drive.
124 Understanding the Configuration wizard
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.
Note
If you are migrating ReportServer database from your local disk to a LUN, ensure that SQL Server Agent and SQL Server Reporting Services are not running.
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.
Chapter 7: Using the SnapManager Configuration Wizard 125
Attention
Use the SnapManager Configuration wizard to move databases, transaction logs, or database system files. SnapManager ensures that these files are place in locations that meet SnapManager configuration requirements. Incorrectly located database, transaction logs, or database system files impair SnapManager operation. If some other medium is used to move the database, transaction logs, or database system files, run the SnapManager Configuration wizard after the operation to ensure that these files are in correct locations.
When to re-run the Configuration Wizard
Whenever you change the configuration manually using SnapDrive or the System Manager, you need to re-run the Configuration wizard to inform SnapManager that configuration has been modified. For example, when you manually change the SnapManager configuration from using volume mountpoints to drive letters, or from using drive letters to volume mountpoints, you need to run the
Configuration wizard again for the changes to take effect. Another example of when the Configuration wizard needs to be run is when a new database is added using the SQL Management Studio.
About
SnapManager components
When you use the Configuration wizard, you are specifying the placement of several components of SQL Server and SnapManager.
Server instance system path: Path to the directory that contains the server instance files. SnapManager places instance system files on the same LUN that stores the transaction logs for that database. The server instance system files must remain where the Configuration wizard places them.
Server instance databases: The databases in a database or store. The .mdf file is the primary database file. The .ndf file is the secondary database file.
Transaction log files: The location of the transaction logs. The transaction logs contain changes made to the databases since the last backup, enabling an up-to-the-minute restore. The .ldf file is the transaction log file.
SnapInfo directory: Contains SnapManager backup information, copies of transaction log files, and other data critical to the backup set.
126 Understanding the Configuration wizard
Settings
configurable only with the
Configuration Wizard
The following table lists the 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 Select a database to move to a LUN 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
Note
If an FCP or iSCSI hardware initiator is present on your system, then the option to add Microsoft iSCSI Service as a dependency is displayed as inactive.
Chapter 7: Using the SnapManager Configuration Wizard 127