sfw-Hotfix_5_1_20015_89_2330902

 Basic information
Release type: Hot Fix
Release date: 2011-05-26
OS update support: None
Technote: TECH159868 -Import and Deport task of a Cluster Diskgroup fails due to timeout issues caused by VxVDS plugin
Documentation: None
Popularity: 4282 viewed    downloaded
Download size: 7.42 MB
Checksum: 3814688051

 Applies to one or more of the following products:
Storage Foundation 5.1SP2 On Windows 32-bit
Storage Foundation 5.1SP2 On Windows IA64
Storage Foundation 5.1SP2 On Windows x64
Storage Foundation HA 5.1SP2 On Windows 32-bit
Storage Foundation HA 5.1SP2 On Windows IA64
Storage Foundation HA 5.1SP2 On Windows x64

 Obsolete patches, incompatibilities, superseded patches, or other requirements:
None.

 Fixes the following incidents:
2330902

 Patch ID:
None.

Readme file
Date: 2011-05-24
OS: Windows
OS Version: 2003, 2008
Packages: vxvds.exe vxvdsdyn.exe vdsprovutil64.dll vdsprovutil.dll vxcmd.dll vxvm.dll vxvm_msgs.dll vxvm_msgs.txt
Etrack Incidents: 2330902

Errors/Problems Fixed
----------------------+ 
Performing import/deport disk group in a cluster environment fails due to VxVDS refresh operation. 

Overview
---------
VxVDS refresh operation interferes with disk group import/deport operation resulting in timeout and delay. This happens as both refresh and import/deport disk group processes try to read disk information at the same time. 

Resolution
-----------
To abort the refresh operation if disk group import/deport operation is in progress. Instead of doing full refresh on all the disk groups, refresh operation will now be performed only on disk groups that are being imported/deported.

Fixes Applied for Products
--------------------------+
Storage Foundation 5.1 SP2 for Windows



Install/Uninstall Instructions
------------------------------+
This package contains self-extracting files that are specific to the processor architecture and operating system version.
Choose the appropriate file for your computer's configuration.

==================================================================================
Operating System	Platform	File Name
==================================================================================
Windows Server 2003	IA64		Hotfix_5_1_20015_89_2330902_w2k3_ia64.exe	
			x64		Hotfix_5_1_20015_89_2330902_w2k3_x64.exe
			x86		Hotfix_5_1_20015_89_2330902_w2k3_x86.exe
----------------------------------------------------------------------------------
Windows Server 2008	IA64		Hotfix_5_1_20015_89_2330902_w2k8_ia64.exe	
			x64		Hotfix_5_1_20015_89_2330902_w2k8_x64.exe
			x86		Hotfix_5_1_20015_89_2330902_w2k8_x86.exe
----------------------------------------------------------------------------------

Download the appropriate hotfix executable to a temporary location on your system.
You can install this hotfix using the GUI or from the command line. Instructions for both options are provided below.

Each self-extracting file includes the following updated file(s):

=====================================================================
Filename          | Version 	 |  Windows 2003   | Windows 2008   |
=====================================================================
 vxvds.exe        | 5.1.20015.89 |  x86, x64, ia64 | x86, x64, ia64 |
---------------------------------------------------------------------
 vxvdsdyn.exe     | 5.1.20015.89 |  x86, x64, ia64 | x86, x64, ia64 |
---------------------------------------------------------------------
 vdsprovutil64.dll| 5.1.20015.89 |  x86, x64, ia64 | x86, x64, ia64 |
---------------------------------------------------------------------
 vdsprovutil.dll  | 5.1.20015.89 |  x86, x64, ia64 | x86, x64, ia64 |
---------------------------------------------------------------------
 vxcmd.dll        | 5.1.20015.89 |  x86, x64, ia64 | x86, x64, ia64 |
---------------------------------------------------------------------
 vxvm.dll         | 5.1.20015.89 |  x86, x64, ia64 | x86, x64, ia64 |
---------------------------------------------------------------------
 vxvm_msgs.dll    | 5.1.20015.89 |  x86, x64, ia64 | x86, x64, ia64 |
---------------------------------------------------------------------
 vxvm_msgs.txt    |              |  x86, x64, ia64 | x86, x64, ia64 |
---------------------------------------------------------------------


Before you begin
-----------------
[1] This is applicable only for Windows Server 2003.

This hotfix requires Microsoft Core XML Services (MSXML) 6.0 pre-installed in your setup. Download and install MSXML 6.0 before installing the hotfix.
Refer to the following link for more information:
http://www.microsoft.com/downloads/details.aspx?FamilyId=993c0bcf-3bcf-4009-be21-27e85e1857b1&displaylang=en

Microsoft posted service pack and/or security updates for Core XML Services 6.0.
Please contact Microsoft or refer to Microsoft website to download and install latest updates to Core XML Services 6.0.
Refer to the following link for more information:
http://www.microsoft.com/downloads/details.aspx?FamilyId=70C92E77-9E5A-41B1-A9D2-64443913C976&displaylang=en

[2] The hotfix installation requires stopping the Storage Agent (vxvm) 
service which will cause the 'Volume Manager Disk Group' (VMDg) resources 
in a cluster environment (MSCS or VCS) to fault. If this hotfix is 
being applied to a server in cluster, make sure any cluster groups 
containing a VMDg resource are taken offline or moved to another node in 
the cluster before proceeding. 

[3] Please make sure to close the Windows Event Viewer before installing this hotfix.

To install the hotfix using the GUI
------------------------------------
1. Double click the hotfix executable file to extract the contents to a default location on the cluster node.
On 32-bit systems, the files are extracted to:
"%commonprogramfiles%\Veritas Shared\WxRTPrivates"

On 64-bit systems, the files are extracted to:
"%commonprogramfiles(x86)%\Veritas Shared\WxRTPrivates"

The Hotfix Installer Wizard is automatically launched after the files are extracted.

2. Click "Next" on the Welcome screen. 
The 'Hotfix Installation Task' screen lists the tasks that are performed by the installer.

3. Click "Install Hotfix" to begin the hotfix installation. 
The status of each installation task is updated as it completes.

4. After the tasks are complete, click "Next" and then click "Finish" to complete the installation process.

5. If prompted to restart the server, do so.

6. If this is a clustered configuration (VCS or MSCS), please perform steps 1-5 on all additional nodes in the cluster.


To install the hotfix using the command line
---------------------------------------------
1. At the command prompt, run one of the following commands to extract the hotfix files to the default location:
C:\temp><Hotfix_BuildVersion_IncidentNumber_OS_Platform>.exe /x
or
C:\temp><Hotfix_BuildVersion_IncidentNumber_OS_Platform>.exe /extract

For example, to extract this hotfix on a 32-bit Windows 2003 system, the command is:
C:\temp>Hotfix_5_1_20015_89_2330902_w2k3_x86.exe /x

2. From the command prompt, navigate to the default location where the hotfix files are extracted.
On 32-bit systems, the files are extracted to:
"%commonprogramfiles%\Veritas Shared\WxRTPrivates\<Hotfix_BuildVersion_IncidentNumber>"

On 64-bit systems, the files are extracted to: 
"%commonprogramfiles(x86)%Veritas Shared\WxRTPrivates\<Hotfix_BuildVersion_IncidentNumber>"

3. At the command prompt, run the following command to install the hotfix:
VxHF.exe /install:<Hotfix_BuildVersion_IncidentNumber> /silent

Here, <Hotfix_BuildVersion_IncidentNumber> is the name of the hotfix file excluding the OS, platform, and .exe extension.

For example, to install this hotfix on a 32-bit Windows 2003 system, the command is:
VxHF.exe /install:Hotfix_5_1_20015_89_2330902 /silent

Hotfix Executable Name is Hotfix_5_1_20015_89_2330902_w2k3_x86.exe.
When installing the hotfix, the <Hotfix_BuildVersion_IncidentNumber> name is Hotfix_5_1_20015_89_2330902.
(note how the "_w2k3_x86.exe" is excluded).

4. Follow the instructions displayed in the command prompt to complete the hotfix installation.

5. If prompted to restart the server, do so at this time.

6. If this is a clustered configuration (VCS or MSCS), please perform steps 1-5 on all additional nodes in the cluster.

Known Issue
----------------------+
Known Issue reported with this hotfix is as follows:

VDS Refresh fails to complete successfully after a storage disconnect/reconnect. All subsequent VDS Refresh operations fail (2346508)

Workaround: To resolve the above issue, perform the following through the command line interface:

1. Net stop vds

2. Net stop vxvm

3. Taskkill /F /IM vxvds.exe

4. Taskkill /F /IM vxvdsdyn.exe (only on Windows 2008 and onwards)

5. Net start vds

6. Net start vxvm

Additional Notes
----------------------+
- To confirm the installation of the hotfix, run the following command:
vxhf.exe /list

The output of this command lists the hotfixes installed on a system.

- For details about a particular hotfix, run the following command:
vxhf.exe /display:<HotfixName>

Here, <HotfixName> is the name of the hotfix file without the platform and the .exe extension.

- The hotfix installer (vxhf.exe) creates and stores logs at:
"%allusersprofile%\Application Data\Veritas\VxHF"

- For general information about the hotfix installer (vxhf.exe), please refer to the following technote:
http://seer.entsupport.symantec.com/docs/329713.htm

- To view a list of hotfixes already installed on a system, please refer to the steps mentioned in the following technote: 
http://seer.entsupport.symantec.com/docs/329704.htm

- For information on uninstalling a hotfix, please refer to the steps mentioned in the following technote: 
http://seer.entsupport.symantec.com/docs/329709.htm


DISCLAIMER
------------------+
This fix has not been fully tested. It is recommended that the fix be evaluated in a test environment before implementing it in your production environment. When the fix is incorporated into a Storage Foundation for Windows maintenance release, the resulting Hotfix or Service Pack must be installed as soon as possible. Symantec Technical Services will notify you when the maintenance release (Hotfix or Service Pack) is available.