This page lists publically-released patches for Veritas Enterprise Products.
For Product GA build, see Veritas Entitlement Management System(VEMS) by clicking the Veritas Support 'Licensing' option.
For information on private patches, contact Veritas Technical Support.
Veritas is making it easier to find all software installers and updates for Veritas products with a completely redesigned experience. NetBackup HotFixes and NetBackup Appliance patches are now also available at the new Veritas Download Center.
Patches for your product can have a variety of names. These names are based on product, component, or package names. For more information on patch naming conventions and the relationship between products, components, and packages, see the SORT online help.
vcs-win-Hotfix_5_1_01008_1803180
Sign in if you want to rate this patch.

 Basic information
Release type: Hot Fix
Release date: 2009-09-08
OS update support: None
Technote: 331495 - MountV goes into a clean loop if a Volume fails to arrive or goes Missing
Documentation: None
Popularity: 764 viewed    36 downloaded
Download size: 2.54 MB
Checksum: 1803725940

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

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

This patch requires: Release date
sfw-win64-5.1AP1 2008-12-20
sfw-win32-5.1AP1 2008-12-20

 Fixes the following incidents:
1803180

 Patch ID:
None.

 Readme file  [Save As...]
Date: 2009-07-10
OS: Windows
OS Version: 2003, 2008
Packages: Private_5_1_01008_1803180_dotnet.exe, Private_5_1_01008_1803180_x64.exe, Private_5_1_01008_1803180_ia64.exe
Etrack Incidents: 1803180
Errors/Problems Fixed: 
This private provides a fix for the case 240-985-321 related to VMDg and MountV agents. The Symantec incident number for this issue is 1803180. This private is 
supported on Storage Foundation and High Availability Solutions 5.1 AP1 for Windows .
When a disk group is imported and the MountV resource is brought online, 
sometimes there may cases where volumes fail to arrive or may go missing. In such cases the MountV resource goes into an UNKNOWN state and the service 
group is unable to fail over.The updated WinVM components, and the VCS VMDg and MountV agents resolve this issue. If the MountV agent detects missing or 
unarrived volumes during online or other operations, the MountV resource faults and this initiates a service group failover. Also in order to provide more information 
at the disk group level, the VMDg agent detects missing or unarrived volumes during detail monitoring and logs the issue.
Fixes Applied for Products: 
Storage Foundation and High Availability Solutions 5.1 AP1 for Windows 
Install/Uninstall Instructions:
Download the appropriate private executable to a temporary location on your system.
For Windows 2003 systems, this private requires Microsoft XML Core Services (MSXML) version 6.0. Make sure you install MSXML Core Services 6.0 before installing the private.
Refer to the following link for more information:
http://www.microsoft.com/downloads/details.aspx?FamilyId=70C92E77-9E5A-41B1-A9D2-64443913C976&displaylang=en
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 SharedWxRTPrivates"
On 64-bit systems, the files are extracted to:
"%commonprogramfiles(x86)%Veritas SharedWxRTPrivates"
The Hotfix Installer Wizard is automatically launched after all the files are extracted.
2. Click "Next" on the Welcome screen.
The Hotfix Installation Tasks panel lists the tasks that are performed by the installer. 
3. Click "Install Private" to install the hotfix.
The status of each task is updated as it gets completed.
4. After the tasks are complete, click "Next" and then click "Finish" to complete the installation process.
5. Repeat these steps for all the cluster nodes.
To install the hotfix using the command line
----------------------------------------------------------------
1. At the command prompt run any of the following commands to extract the hotfix files to the default location:
C:	emp><PrivateName_Platform.exe> /x
or
C:	emp><PrivateName_Platform.exe> /extract
For example, to extract this hotfix on a 32-bit cluster node, the command is:
C:	emp>Private_5_1_01008_1803180_dotnet.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 SharedWxRTPrivates"
On 64-bit systems, the files are extracted to:
"%commonprogramfiles(x86)%Veritas SharedWxRTPrivates"
3. At the command prompt, run the following command to install the hotfix:
VxHF.exe /install:<PrivateName> /silent
Here, <PrivateName> is the name of the private file without the platform and the .exe extension.
For example, to install this hotfix on a 32-bit cluster node, the command is:
VxHF.exe /install:Private_5_1_01008_1803180 /silent
4. Follow the instructions displayed in the command prompt to complete the hotfix installation.
5. Repeat these steps for all the cluster nodes.
Additional notes
------------------------
- VxHF.exe logs are located at the following location:
"%allusersprofile%Application DataVeritasVxHF"
- For information on a list of hotfixes installed on the node, use the following command:
VxHF.exe /List
- For details about a particular hotfix, use the following command:
VxHF.exe /Display:<PrivateName>
Here, <PrivateName> is the name of the private file without the platform and the .exe extension.



Read and accept Terms of Service