Updated SnapDrive agent for VERITAS Cluster Server (tm) for Network Appliance Snapmirror 4.2 RP1 and 4.3 MP1

Article:TECH46106  |  Created: 2006-01-30  |  Updated: 2007-01-10  |  Article URL http://www.symantec.com/docs/TECH46106
Article Type
Technical Solution


Environment

Issue



Updated SnapDrive agent for VERITAS Cluster Server (tm) for Network Appliance Snapmirror 4.2 RP1 and 4.3 MP1

Solution



The updated SnapDrive agent for VERITAS Cluster Server (VCS) for Network Appliance Snapmirror 4.2 RP1 and 4.3 MP1 allows for the use of SnapDrive version 3.2 as well as other related Network Appliance software, such as Ontap 7.0, needed to use SnapDrive version 3.2.  This updated SnapDrive agent was designed to be used with 4.2 RP1 and 4.3 MP1 only.  If the base 4.2 and 4.3 products are being used, they must be upgraded to RP1 and MP1 (respectively) before applying the updated SnapDrive agent. See the Related Documents section below for downloads of RP1 and MP1

The SnapDrive agent for VCS) was designed to work specifically with SnapDrive version 3.0 R2.  Newer versions of the SnapDrive software have changed in such a way that the SnapDrive Agent for VCS no longer functions as expected when doing a site to site failover or migration.  In addition, SnapDrive 3.0 R2 is no longer available or supported by Network Appliance.

Below is the contents of the readme.txt file that is included in the download:

CONTENTS
-----------------+
I.PRIVATE OVERVIEW
 -Symptoms of the Problem
 -Resolution
II.INSTALLING THE PRIVATE
III.DISCLAIMER


I. PRIVATE OVERVIEW
----------------------+
The VERITAS Cluster Server for Network Appliance Snapmirror 4.2 RP1 and 4.3 MP1 PRIVATE 509639 provides a fix for a case related to the VCS agent for Network Appliance SnapMirror. The VERITAS incident number for this issue is 509639. This case originated from the customer. This Private is supported on VERITAS Cluster Server for Network Appliance Snapmirror 4.2 RP1 and 4.3 MP1.

Symptoms of the Problem
------------------------------+
- In a DR failover scenario, SnapDrive resources fail to come online. If a SnapMirror relationship was established using filer names, and if the user tries to use the filer IP address (instead of the filer name) in UNC path for disk create or connect operations, on the live SnapMirror destination volume, SnapDrive may not be able to determine the status of the volume and may fail.

- If SnapDrive 3.2 is installed, the Exchange Setup wizard was not able to discover NetApp volumes.


Resolution
-------------+
The updated Network Appliance SnapMirror agent resolves this issue. The Exchange Setup wizard has been modified so that it will detect NetApp volumes if snapDrive 3.2 is installed.


II. INSTALLING THE PRIVATE
-----------------------------+
1.Download and extract the Private zip file to a temporary location on your cluster node.
See the following table to determine which file you must download:

      --------------------------------------------------------------------------
      | Operating System | VCS version  |  Name of Private File to Download        |
      --------------------------------------------------------------------------
      | Windows 2003  | 4.2 RP1      |  Private_4_2_115_509639_w2k3.zip     |
      --------------------------------------------------------------------------
      | Windows 2000  | 4.2 RP1      |  Private_4_2_115_509639_w2k.zip       |
      --------------------------------------------------------------------------
      | Windows 2000     | 4.3 MP1      |  Private_4_3_1001_509639_w2k.zip        |
      --------------------------------------------------------------------------
      | Windows 2003     | 4.3 MP1      |  Private_4_3_1001_509639_w2k3.zip      |
      --------------------------------------------------------------------------
     
Each .zip file contains the following files:
      ------------------------------------------------------------------------------------------
      | Name of the file             | 4.2 RP1 New Version number | 4.3 MP1 New Version number |
      ------------------------------------------------------------------------------------------
      | NetAppSnapDrive.dll          |   4.2.115.0                |   4.3.1001.108                                |
      ------------------------------------------------------------------------------------------
      | NetAppSnapDriveDiscover.dll  |   4.2.115.0                |   4.3.1001.108                            |
      ------------------------------------------------------------------------------------------
      | ExchWizard.exe               |   4.2.115.0                |   4.3.1001.108                                 |
      ------------------------------------------------------------------------------------------
      | Setup.exe                    |   4.2.115.0                |   4.3.1001.108                                     |
      ------------------------------------------------------------------------------------------

2.Make sure that the cluster configuration is in read-only mode.

3.Stop VERITAS High Availability engine (HAD) on all the cluster nodes.
  Type the following on the command prompt:
C:\> hastop -all -force
 
4. Copy the extracted files to their respective locations, as mentioned in the following table:

      -------------------------------------------------------------------
      | Name of the file             |   Copy to directory                                         |
      -------------------------------------------------------------------
      | NetAppSnapDrive.dll          |   %VCS_HOME%\bin\NetAppSnapDrive      |
      -------------------------------------------------------------------
      | NetAppSnapDriveDiscover.dll  |   %VCS_HOME%\bin\NetAppSnapDrive  |
      -------------------------------------------------------------------
      | ExchWizard.exe               |   %VCS_HOME%\bin                                 |
      -------------------------------------------------------------------
      | Setup.exe                    |   %VCS_HOME%\bin\ExchSetup                    |
      -------------------------------------------------------------------

The variable %VCS_HOME% is the default installation directory for VCS, typically C:\Program Files\VERITAS\cluster server. The earlier versions of the files are replaced.

5.Replace this file on each cluster node that has VCS installed, and then start the VERITAS High Availability engine (HAD) on all the cluster nodes.
  Type the following on the command prompt:
  C:\> hastart -all


DISCLAIMER
------------------+
This Private is a supported fix that has not been fully regression tested and must be applied only to systems that are severely affected by the problem. For other situations, it is recommended that you wait for the next service pack that will contain this fix. For more information, contact Symantec Enterprise Technical Support





Attachments

509639_281668.exe (6.4 MBytes)


Legacy ID



281668


Article URL http://www.symantec.com/docs/TECH46106


Terms of use for this information are found in Legal Notices