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.
sfw-win-Hotfix_5_1_10007_584_1959339
Sign in if you want to rate this patch.

 Basic information
Release type: Hot Fix
Release date: 2010-02-19
OS update support: None
Technote: TECH125075 - After rebooting the first starting node of a Microsoft Cluster using dynamic disk(s) for quorum, the Cluster Service fails or is delayed due to a quorum online time-out
Documentation: None
Popularity: 1354 viewed    221 downloaded
Download size: 4.59 MB
Checksum: 4147035160

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

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

 Fixes the following incidents:
1939313, 1959339

 Patch ID:
None.

 Readme file  [Save As...]
Date: 2010-02-11
OS: Windows
OS Version: Windows 2003, Windows 2008
Packages:  vssprov.dll, cluscmd64.cll
Etrack Incidents:  1939313, 1959339
Errors/Problems Fixed: Issue1-During first cluster service startup after reboot Quorum 
resource is taking long time to online. Issue2-IsAlive and LooksAlive calls takes long 
time to complete and time out. 
Fixes Applied for Products: SFW 5.1 SP1
Install/Uninstall Instructions: This package contains the following 
self-extracting files. Each file is the hotfix for a specific processor 
architecture and operating system version. Choose the appropriate file 
for your computer's configuration.


Operating System		Platform	File Name
-------------------------------------------------------------------------------------------
Microsoft Windows Server 2003	IA64		Hotfix_5_1_10007_584_1959339_w2k3_ia64.exe	
Microsoft Windows Server 2003	x64		Hotfix_5_1_10007_584_1959339_w2k3_x64.exe
Microsoft Windows Server 2003	x86		Hotfix_5_1_10007_584_1959339_w2k3_x86.exe
Microsoft Windows Server 2008	IA64		Hotfix_5_1_10007_584_1959339_w2k8_ia64.exe
Microsoft Windows Server 2008	x64		Hotfix_5_1_10007_584_1959339_w2k8_x64.exe
Microsoft Windows Server 2008	x86		Hotfix_5_1_10007_584_1959339_w2k8_x86.exe


Extract the hotfix
==================

The hotfix can be extracted from a file in one of two ways:

* Method 1
  Double-click the hotfix. The hotfix will be extracted and the install 
  wizard will automatically start and guide you through the installation 
  after the extraction has completed.

* Method 2
  Save your selected file to a local folder and then extract the hotfix 
  with the /x option.  For example, enter the command in the c:	mp 
  directory

  c:	mp>Hotfix_5_1_10007_584_1959339_w2k8_x64.exe /x
Hotfix files will be extracted to "Hotfix_5_1_10007_584_1959339" folder at:

on 32-bit system: "%CommonProgramFiles%Veritas SharedWxRTPrivates"
on 64-bit system: "%CommonProgramFiles(x86)%Veritas SharedWxRTPrivates"

Install the hotfix
==================

Refer to README.RTF file in "Hotfix_5_1_10007_584_1959339" folder for details on installation 
options for the hotfix.

To install the hotfix on Widows 2003 servers, Microsoft Core XML Services 
(MSXML) 6.0 need to be installed first. Please 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 web-site to 
download and install latest updates to Core XML Services 6.0.

Additional Notes: 
To install this hotfix on a host which is under VCS, It is required to perform following 
2 additional steps.
1. Before starting Hotfix install, stop HAD Service.
"net stop had"
2. After successful installation, start HAD Service.
"net start had"

Contents

1. Overview
2. Resolution
3. Before you begin
4. Installing the hotfix
     - GUI Install
     - Command Line Install
     - Additional Notes
5. Disclaimer

1. Overview
This  hotfix addresses 2 issues:

Issue1: 
	On 64-bit systems, IsAlive and LooksAlive calls takes long time and time out.

Symptoms Experienced: 
	On 64-bit systems, with NBU installed, vmdg resource suddenly fails over.

More Details: 
	cluscmd64 calls vxbridge to process IsAlive and LooksAlive calls. Vxbridge process calls serially 
and is busy in processing other calls and IsAlive, LooksAlive calls timeout. 

Issue2: 
	Dynamic Quorum resource fails to come online after rebooting the system and time out.

Symptoms Experienced: 
	The Online quorum took around 3 minutes to online the Quorum DG. So the service stopped
 due to Quorun online timeout. This happenes only during first cluster service start after reboot .  

More Details:
	vssprov acquired the ISIS database lock and waiting for CoCreateInstance call to complete. MountV provider is 
waiting for the ISIS database lock and MNTOP_GET_ALL_MOUNTPOINTS is taking longtime.

2. Resolution

Issue1: 
	Now cluscmd64 directly talks to vxio instead of calling vxbridge.
Issue2:
	vssprov acquires ISIS database lock after completing CoCreateInstance.

3. Before you begin

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 web-site to download 
and install latest updates to Core XML Services 6.0.

4. Installing the hotfix

<#FOR_FIXES_THAT_RESTART_VXVM#> ==

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.

== <#FOR_FIXES_THAT_RESTART_VXVM#>

<#FOR_THE_FIXES_THAT_REQUIRE_A_REBOOT#> == 

The hotfix installation requires a reboot of the system before the 
process is complete. Please ensure that the server can be rebooted before 
proceeding with the installation.

== <#FOR_THE_FIXES_THAT_REQUIRE_A_REBOOT#>

Extract the hotfix to a temporary location on the server. The hotfix 
archive contains a hotfix installer for the following Windows Server versions 
and architectures:

Operating System		Platform	File Name
-------------------------------------------------------------------------------------------
Microsoft Windows Server 2003	IA64		Hotfix_5_1_10007_584_1959339_w2k3_ia64.exe	
Microsoft Windows Server 2003	x64		Hotfix_5_1_10007_584_1959339_w2k3_x64.exe
Microsoft Windows Server 2003	x86		Hotfix_5_1_10007_584_1959339_w2k3_x86.exe

Microsoft Windows Server 2008	IA64		Hotfix_5_1_10007_584_1959339_w2k8_ia64.exe
Microsoft Windows Server 2008	x64		Hotfix_5_1_10007_584_1959339_w2k8_x64.exe
Microsoft Windows Server 2008	x86		Hotfix_5_1_10007_584_1959339_w2k8_x86.exe

This hotfix includes the following updated file(s):

================================================================================
Filename     | Version 	     |  Windows 2003  |	Windows 2008   |
================================================================================
cluscmd64.dll| 5.1.10007.584 | x64, ia64      |  x64, ia64     |
--------------------------------------------------------------------------------
vssprov.dll  | 5.1.10007.584 | x86, x64, ia64 | x86, x64, ia64 |
--------------------------------------------------------------------------------

The hotfix can be installed using the GUI or CLI. Instructions for both 
options are provided below:


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 the files have 
been extracted.

2. Click "Next" on the Welcome screen. 

3. The 'Hotfix Installation Task' screen lists the tasks that are performed 
by the installer.

4. Select the "Install Hotfix" button to install the hotfix. 

5. While the hotfix installation updates the system, the status of each 
task is updated as it completes.

6. After all tasks have completed, select 'Next', then 'Finish' to complete the 
installation process.

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

8. If this is a clustered configuration (SFW-HA or MSCS), please perform steps 1-7 
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:	emp><Hotfix_BuildVersion_IncidentNumber_OS_Platform>.exe /x
C:	emp><Hotfix_BuildVersion_IncidentNumber_OS_Platform>.exe /extract

Example:
For Windows Server 2003 32-bit: C:	emp>Hotfix_5_1_xxxxx_xxx_xxxxxxx_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 SharedWxRTPrivates<Hotfix_BuildVersion_IncidentNumber_OS_Platform>"

On 64-bit systems, the files are extracted to: 
"%commonprogramfiles(x86)%Veritas SharedWxRTPrivates<Hotfix_BuildVersion_IncidentNumber_OS_Platform>"

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

Note: <Hotfix_BuildVersion_IncidentNumber_OS_Platform> is the name of the hotfix file excluding the OS, platform, 
and .exe extension. This is also the name of the folder where the hotfix was 
extracted to under the WXRTPRIVATES directory.

Example: 
Hotfix Executable Name: Hotfix_5_1_xxxxx_xxx_xxxxxxx_w2k3_x86.exe
When installing the hotfix, the <Hotfix_BuildVersion_IncidentNumber_OS_Platform> name is 
Hotfix_5_1_xxxxx_xxx_xxxxxxx (note how the '_w2k3_x86.exe' was excluded).

Command:
VxHF.exe /install:Hotfix_5_1_xxxxx_xxx_xxxxxxx /silent

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 (SFW-HA or MSCS), please perform steps 1-5 
on all additional nodes in the cluster.

Additional Notes
----------------
- VxHF.exe logs are located at the following location: 
"%allusersprofile%Application DataVeritasVxHF"

- For general information about the VXHF installer, 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 
following technote: http://seer.entsupport.symantec.com/docs/329704.htm

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


5. 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.



Read and accept Terms of Service