Starting SnapManager for the First Time

Start SnapManager 2.1 for Microsoft SQL Server. To do this, go to the Start menu and select Program Files > SnapManager for SQL Server.

If you have just upgraded to SnapManager 2.1 for Microsoft SQL Server, SnapManager automatically connects to the default SQL Server already configured. Go to Step 4.

If you have just installed SnapManager for the first time, the Connect to SQL Server dialog box appears so that you can specify the default SQL Server.

Specify the default SQL Server.

Select the SQL Server you want to manage.

1. In the SQL Server box, specify the SQL Server you want to manage.
2. In the Connection panel, choose the security authentication method to be used to connect to the SQL Server.
3. If you selected SQL Server authentication, you must also specify the login name and password.
4. Click OK.

For more detailed information, see Connecting to an SQL Server instance.

Result

SnapManager connects to the specified SQL Server, using the specified security authentication method.

SnapManager creates a share for remote access to the Report directory.

The first time SnapManager is launched, it creates a Report directory share, SMSQLReportFolder, to allow for remote administration. The following accounts are granted Full Control on this share:

• The logged-in user on the local machine
• The Administrators group on the local machine

  If another user is logged onto a remote administration server with an account that belongs to the Administrators group on this machine, that user can connect to this SQL Server and view the SnapManager reports.

If SnapManager was just upgraded from SnapManager 2.0, there might be other existing accounts with permissions on the share.

• If only the existing group Everyone has permissions on the Report directory share, SnapManager removes the Full Control permissions to the Reports directory for that group.
• If multiple existing accounts (including Everyone) have permissions on the Report directory share, SnapManager does not modify those accounts.

SnapManager checks the SQL Server version.

If SnapManager detects that the SQL Server 2000 or 2005 software does not have the minimum service pack level required by SnapManager, an error message box appears.

If this occurs, see the table of Windows host system requirements and note the requirements for Microsoft SQL Server.

• If you have a different SQL Server instance that has the minimum service pack required by SnapManager, you can connect to that instance instead.
  1. Open the Connect to SQL Server dialog box. To do this, select Action > Connect to Another SQL Server.
  2. Return to Step 2.
• Otherwise, close the SnapManager application, upgrade Microsoft SQL Server as needed, then restart SnapManager.

If SQL Server 2005 is installed, SnapManager checks the MDAC version.

If SnapManager detects that SQL Server 2005 is installed on a Windows host that does not have the MDAC version required by SQL Server 2005 for the installed version of Windows, an event is posted to the Windows Application event log.

If this occurs, do the following:

1. See the table of Windows host system requirements and note the operating system requirements with respect to SQL Server 2005.
2. Close the SnapManager application, upgrade the MDAC as needed, then restart SnapManager.

SnapManager checks the SnapDrive version.

If SnapManager detects that SnapDrive is installed but that it is a version not supported with this version of SnapManager, a warning dialog box appears.

If this occurs, see the Windows host system requirements and note the requirements for Microsoft SQL Server 2000 or 2005. Close the SnapManager application, upgrade SnapDrive as needed, then restart SnapManager.

SnapManager reminds you to run the Configuration Wizard.

If, after connecting to the default SQL Server, SnapManager detects that no databases have been configured for use with SnapManager, a message box appears and prompts you to run the Configuration Wizard.

Click OK.

Result

The message box closes, and SnapManager automatically launches the Configuration Wizard.

Plan your database migration before you run the Configuration Wizard.

For now, click Cancel to exit the Configuration Wizard without specifying any database or LUN configuration information yet.

After you have planned your database migration (as described in Chapter 6, Preparing to Migrate SQL Server Databases), start the Configuration Wizard manually and specify database and LUN configuration details (as described in Chapter 7, Using the SnapManager Configuration Wizard).