Table of ContentsView in Frames

Installing SnapManager on a stand-alone Windows host system

This section describes how to install SnapManager on a stand-alone Windows host system used for any of the following purposes:

Note: You do not need to stop SQL Server instances before or during the SnapManager software installation process.

Modes of installing SnapManager

The software installation utility for SnapManager can be run in either interactive mode or unattended mode. These two modes are described in the following table.

Feature SnapManager installation mode
Interactive Unattended

Access

Requires user interaction and access to the user interface.

Allows automated installation by executing a script or command line.

Minimum required input

  • SnapManager service account
  • User name
  • Password

Optional input

  • Organization name
  • SnapManager server-side license key
  • SnapManager installation directory

After the installation finishes

If a system reboot is required to activate new software, a dialog box appears and prompts you to select whether you want to reboot the target system.

If a system reboot is required to activate new software, a dialog box appears and prompts you to choose whether you want to reboot the target system. You can override this default behavior by including an optional command line parameter.

Installing in interactive mode

To install SnapManager using the software installation utility in interactive mode, complete the following steps.

Step Action
1

Download the software from the NetApp Support Site at support.netapp.com and then launch the installation program.

Attention: Do not use Terminal Services for any type of SnapManager administration, because you might miss critical information that is displayed only in pop-up boxes at the system console.
2

In the Welcome screen, click Next.

Result: At this time the installer checks the system for required Microsoft SQL Server components. If they are not present or current, the InstallShield Wizard lists the items. You must click Install to continue the installation.

3

In the Customer Information screen, specify the user name, the organization name, and the SnapManager license type. See Verifying Windows host system requirements for details about the two license types.

If you have a storage-system-side license for SnapManager, select Per storage system, and be sure that the SnapManager system-side license is enabled on the storage system.

If you have an SQL-Server-side license for SnapManager, select Per Server and use the License Key box to enter the license key for your server-side license.

Note: If a server-side license key is unavailable during installation, you can leave the License Key text box empty. After the installation completes, you can enter the license key through the SnapManager for Microsoft SQL Server GUI by right-clicking the server name and selecting License Settings.
4

Click Next.

Result: The Destination Folder screen appears.

5

In the destination folder, note the full path of the folder in which SnapManager will be installed.

The default installation directory for SnapManager for Microsoft SQL Server is as follows:

C:\Program Files\NetApp\SnapManager for SQL Server\

6

(Optional) If you want to install SnapManager in a directory other than the default installation directory, do the following:

  1. Click Change to open the Change Current Destination Folder dialog box.
  2. Browse to an alternate installation directory.
  3. Click OK to close the dialog box.

    The Destination Folder screen displays the new specified installation directory path.

Record the newly specified installation directory path.

7

Click Next.

Result: The SnapManager Server Identity screen appears.

8

In the Account box of the SnapManager Server Identity screen, specify the user account you want to use to run SnapManager.

For information about account requirements, see SnapManager service account requirements.

If SnapDrive is installed and configured, the text box is populated with the account for which SnapDrive is configured. Otherwise, browse to find and select the account name. The user account name is specified in either of the following formats:

  • DomainName\UserName
  • UserName@DomainName
9

In the Password box and in the Confirm Password box, enter the user password. Leave the password blank if you entered a group Managed Service Account in the user name field.

10

Click Next.

Result: The Ready to Install the Program screen appears. All the installation specifications are complete.

11

Optional. Review or change your current installation specifications before proceeding by clicking Back.

12

To proceed with the installation using your current specifications, click Install.

Result: The installation process begins, and the Installing SnapManager for SQL Server screen appears. The screen displays the progress of the installation process.

13

If you are running SQL Server on virtual machine using VMDK, install SnapManager on the virtual machines so you can use SnapManager for SQL Server to back up and restore databases on those virtual machines.

14

After the InstallShield Wizard Completed screen appears, click Finish to exit the software installation utility.

15

Proceed to Starting SnapManager for the first time after installation.

After you finish

Fractional space reservation is disabled by default. If you are not using fractional space reservation on the storage system volumes that contain LUNs that are used for SQL Server, the monitoring can be disabled. Doing so improves backup completion times. For details on how to enable and disable monitoring, see Managing fractional space reservation.

Installing SnapManager in unattended installation mode

This topic describes how to install SnapManager by running the software installation utility from a command line. This enables you to install the SnapManager software under the control of a script for an unattended installation.

Note: You do not need to stop SQL Server instances before or during the SnapManager software installation process.

How to start the unattended installation To install SnapManager in unattended mode, enter the following command either directly at the command line or through a script:

CommandName /s /v”/qn SILENT_MODE=1 [USERNAME=UserName]

[COMPANYNAME=CompanyName] [ISX_SERIALNUM=LicenseKey]

[INSTALLDIR=InstallationDirectory] SVCUSERNAME=Domain\UserName

SVCUSERPASSWORD=Password SVCCONFIRMUSERPASSWORD=Password

[REBOOT=0] [/L* TempDirPath\LogFileName]”

The following table describes each of the parameters.

Command or parameter Description

CommandName

The location and name of the executable.

SILENT_MODE=1

Runs the installer in silent mode.

USERNAME=UserName

Optional. If not specified, the default value is retrieved from the registry.

COMPANYNAME=CompanyName

Optional. If not specified, the default value is retrieved from the registry.

ISX_SERIALNUM=LicenseKey

Optional. Only used to specify an SQL Server-side license for SnapManager.

INSTALLDIR=InstallationDirectory

Optional. If not specified, the default installation directory is used:

C:\Program Files\NetApp\SnapManager for SQL Server\

SVCUSERNAME=Domain\UserName

The account from which SnapManager is to be run.

For information about account requirements, see SnapManager service account requirements.

Do not use the password parameters if you entered a group Managed Service Account in the user name field.

SVCUSERPASSWORD=Password

SVCCONFIRMUSERPASSWORD=Password

REBOOT= 0

Optional.

After the installation finishes, the installation utility automatically reboots the Windows host system if that is required to activate updated software.

If you specify this option, however, the system is not be rebooted.

/L* TempDirPath\LogFileName

Optional.

If you specify this option, detailed information about the installation is written to the specified log file. This information can be used to investigate details about how a particular instance of SnapManager for Microsoft SQL Server is installed.

The asterisk (*) is a wildcard character specifying that all the installation information (such as status messages, nonfatal warnings, and error messages) is to be logged.

TempDirPath is the fully qualified name of the directory in which the installation log is created or overwritten.

LogFileName is the name of the file to which the transaction logs are written.

Example

"C:\NetApp\downloads\SMSQL7.0_x64.exe" /s /v"/qn SILENT_MODE=1 SVCUSERNAME=MKTG2\Administrator SVCUSERPASSWORD=**** SVCCONFIRMUSERPASSWORD=*** ISX_SERIALNUM=***"

After you finish