Installing or upgrading the SnapDrive components

Use this procedure to install or upgrade the SnapDrive for Windows components.

Before you begin

Make sure that you have prepared your host for SnapDrive and that all the minimum requirements are met.
Perform this procedure from the system console, not from a Terminal Service client.
If you are upgrading SnapDrive on a server cluster, install SnapDrive on all nodes, starting with the nodes that do not own the cluster resources and rotating which system is the owner until all nodes in the cluster have the same version of SnapDrive installed.
If you are running NetApp Host Agent, stop the NetApp Host Agent service.
If a version of SnapDrive is already installed on your system, stop the SnapDrive service, if you have not already done so, and close the Microsoft Management Console (MMC) window.
If VMware vCenter or guest OS is present, the vCenter or ESX server user name that you enter must be assigned a vCenter role that has at least the minimum required privileges.
Use vCenter credentials if the virtual machines on which SnapDrive is being installed will belong to a Microsoft cluster.
If you want to enable Snapshot copy management of VMDKs on NFS and VMFS datastores, ensure that VMtools is installed.
Have your Virtual Storage Console configured and have the Virtual Storage Console IP address or server name and the TCP port number available when prompted.
If you want to enable Hyper-V pass-through disk provisioning, have your Hyper-V server local host IP address and TCP port number available and enter when prompted.

Steps

Browse to the location of the SnapDrive installation package and double-click the executable file.
Click Next on the Welcome to the SnapDrive Installation Wizard screen.
If this is a new SnapDrive installation, read and accept the license agreement, and then click Next.
If you are upgrading SnapDrive, the Program Maintenance panel appears. Select Modify/Upgrade, and then click Next.
The SnapDrive License panel is displayed. Select which type of licensing you want to use, enter your license key in the space provided if you are using host-side (per server) licensing, and then click Next. (If you are upgrading, the license information will already be filled in.)
If you choose storage system licensing, you can install SnapDrive without entering a license key, and you will be able to execute SnapDrive operations only on storage systems that have a SnapDrive or SnapManager license installed.
If this is a new installation, follow the procedure in this step. If you are upgrading, skip to the next step.
1. In the Customer Information panel, type your user name and organization name, and then click Next.
2. The Destination Folder panel prompts you for a directory in which to install SnapDrive on the host. By default, this is C:\Program Files\NetApp\SnapDrive\ for new installations.
  
  To accept the default, click Next and then proceed to the next step.
  
  To specify a different location, click the Change button. In the Change Current Destination Folder panel, either type the path to the target directory in the Folder Name text box, or navigate to the folder you prefer and select it. When the correct target location appears in the Folder Name text box, click OK to return to the Destination Folder panel, and then click Next.
  
  Note: If you are upgrading SnapDrive from a version earlier than 4.1, the default installation directory is C:\Program Files\SnapDrive\.
If the VMware ESX guest OS is detected, you are prompted to enter the IP address and a user name having the appropriate vCenter or ESX server privileges. On the VirtualCenter or ESX Server Web Service Credentials screen, type in the IP address of the vCenter or ESX server and the user name and password for SnapDrive to use for Web service authentication. If you want to be able to use VMotion, make sure you use the vCenter.

Note: Selecting "Enable VirtualCenter or ESX Server Settings" enables SnapDrive to use RDM pass-through LUNs. Select this option if you plan to use RDM pass-through disks. This option is not selected by default.
If Virtual Storage Console is detected, you are prompted to enter the Virtual Storage Console server IP address and the TCP port number if it is something other than the default of 8043.
On the SnapDrive Management Service Credentials screen, if you are upgrading and the account name is already filled in, type the account password in both the Password and Confirm Password text boxes, and then click Next. Otherwise, you can type in the account you want to use, or complete the following steps to select a user account.
1. Click Add.
  The Select User window is displayed.
2. In the "From this location" field, verify that the location is set to the proper domain if your storage system is in a domain, or click the Locations button and select the local host if your storage system is in a workgroup.
3. In the "Enter the object name to select" text box, type the user name with administrator privileges that you want to use, and then click the Check Names button to verify the user you entered. Click OK.
  
  Note: If you are installing SnapDrive for use with a storage system in a workgroup, enter the name of the user that you configured for pass-through authentication.
4. Type the account password in both the Password and Confirm Password text boxes, and then click Next.
In the SnapDrive Web Service Configuration window, leave the default ports unless any of them are already being used exclusively by another service. Click Next.
In the Transport Protocol Default Setting window, leave the default setting of RPC unless your environment requires the use of HTTP or HTTPS.
1. If you choose to use HTTP or HTTPS, type the user name and password for SnapDrive to use for authentication. The default ports of 80 for HTTP or 443 for HTTPS are filled in automatically.
  
  Note: If you set up SnapDrive to use HTTP or HTTPS to communicate with storage systems, using the domain Administrator account for authentication results in significantly reduced performance. To avoid this issue, use a storage system account for authentication instead of the domain account.
2. Click Next.
If you want to enable SnapDrive to communicate with Operations Manager, complete the following steps on the Operations Manager Configuration screen.
1. Select the Enable Protection Manager Integration checkbox.
2. Type the name or IP address of the Operations Manager server in the Operations Manager Name/IP Address field.
3. Select HTTP or HTTPS.
4. Leave the default port of 8088 for HTTP or 8488 for HTTPS, unless Operations Manager is configured to use a different port.
5. Type the user name and password for SnapDrive to use for authentication.
6. Click Next.
Note: If you do not enable Protection Manager integration during the installation, you can configure these settings later using the SnapDrive command-line interface.
On the Ready to panel, click Install or Upgrade.
When the SnapDrive Installation Completed screen appears, click Finish.

Note: If you are upgrading a server cluster and you try to use MMC after upgrading SnapDrive on the first node and before upgrading SnapDrive on the remaining nodes, you get an error message indicating that the SnapDrive service is unavailable owing to an invalid tag. This message is the result of the temporary presence of two versions of SnapDrive on the same cluster. No corrective action is needed; just upgrade SnapDrive on the other nodes.

Result

A shortcut to the standalone SnapDrive for Windows Management Console is added to the Start Menu, and you can also access the SnapDrive snap-in in MMC.

After you finish

If you are running Windows Server 2008, you must configure the Windows Firewall to allow SnapDrive communications.
If you are upgrading or installing SnapDrive to support a SnapManager installation, and you use verification servers, you must install SnapDrive on the verification servers as well as on the production systems, and both the verification server and the production servers must be using the same version of SnapDrive.
If a verification server will be connecting to LUNs over an iSCSI session, make sure you also install the Microsoft iSCSI Software Initiator on the verification server and establish a session from the verification server to the iSCSI target on the storage system where the database to be verified resides. This connection enables the verification server to connect to the Snapshot copy LUN that contains the database, and you must create it explicitly before the verification server attempts to connect to the LUN.