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_x64-CP3_SFWHA_601
Obsolete
The latest patch(es) : sfha-win_x64-CP8_SFWHA_601 
Sign in if you want to rate this patch.

 Basic information
Release type: Patch
Release date: 2014-01-28
OS update support: None
Technote: TECH209086 - Storage Foundation for Windows High Availability, Storage Foundation for Windows and Veritas Cluster Server 6.0.1 Cumulative Patches
Documentation: None
Popularity: 18696 viewed    120 downloaded
Download size: 12.93 MB
Checksum: 4001638068

 Applies to one or more of the following products:
Storage Foundation HA 6.0.1 On Windows x64

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

This patch is obsolete. It is superseded by: Release date
vcs-win_x64-CP4_SFWHA_601 (obsolete) 2014-04-28

This patch supersedes the following patches: Release date
vcs-win_x64-CP2_SFWHA_601 (obsolete) 2013-10-29
vcs-win_x64-CP1_SFWHA_601A (obsolete) 2013-07-29

 Fixes the following incidents:
2938704, 3054751, 3061942, 3065921, 3099727, 3099805, 3113887, 3124269, 3164649, 3186666, 3231486, 3231600, 3298600, 3300849, 3334544, 3347495, 3352705, 3360992, 3369234, 3386077

 Patch ID:
None.

 Readme file  [Save As...]
This readme has the following sections:

=====================|
* Date
* OS/Version
* Packages
* Etrack Incidents
* Fixes Applied for Products
* What's new in this CP
* Install instructions
* - Before you begin
* - To install in the verbose mode
* - To install in the non-verbose (silent) mode
* Post-install steps
* Known issues
* Errors/Problems fixed
* Additional notes
* Disclaimer
=====================|

Date: 2014-27-01
OS: Windows
OS Version: 2008, 2008 R2
Packages:

===============================================
Architecture/OS  Windows Server 2008 / 2008 R2
===============================================
x64 	         CP3_SFWHA_601_W2k8_x64.exe
-----------------------------------------------

Etrack Incidents: 
3065921, 2938704, 3099727, 3054751, 3164649, 3186666, 3113887, 3061942, 3099805, 3124269, 3231600, 3298600, 3300849, 3334544, 3231486, 3369234, 3386077, 3352705, 3360992, 3347495



Fixes Applied for Products
==========================|
Storage Foundation and High Availability Solutions (SFW HA) 6.0.1 for Windows


What's new in this CP
=====================|
The following hotfixes have been added in this CP:
 - Hotfix_6_0_10020_3369234
 - Hotfix_6_0_10022_3386077
 - Hotfix_6_0_10010_308_3352705
 - Hotfix_6_0_10011_308_3360992
 - Hotfix_6_0_10012_308_3347495

For more information about these hotfixes, see the "Errors/Problems fixed" section in this readme.


Install instructions
====================|
Download the appropriate cumulative public patch (CP) executable file to a temporary location on your system. You can install the CP in a verbose mode or in a non-verbose mode. Instructions for both options are provided below.

Each cumulative public patch includes the individual hotfixes that contain enhancements and fixes related to reported issues.
See "Errors/Problems fixed" section for details.

Before you begin
----------------:
[1] Ensure that the logged-on user has privileges to install the CP on the systems.

[2] One or more hotfixes that are included with this CP may require a reboot.
Before proceeding with the installation ensure that the system can be rebooted.

[3] Symantec recommends that you close the Cluster Manager (Java Console) and the Veritas Enterprise Administrator (VEA) Console before installing this CP.

[4] Ensure that you close the Windows Event Viewer before proceeding with the installation.

[5] Before installing CP, ensure that the Startup type of the VCS Authentication Service is set to Automatic. This is applicable only if you have configured a secure cluster and installed CP or Agent Pack 2Q2012 on your system. 

[6] Before installing CP on Windows Server Core systems, ensure that Visual Studio 2005 x86 redistributable is installed on the systems.


To install in the verbose mode
------------------------------:
In the verbose mode, the cumulative public patch (CP) installer prompts you for inputs and displays the installation progress status in the command window.

Perform the following steps:
[1] Double-click the CP executable file to extract the contents to a default location on the system.
The installer displays a list of hotfixes that are included in the CP.
On 64-bit systems, the hotfixes executable files are extracted to:
"%commonprogramfiles(x86)%\Veritas Shared\WxRTPrivates\<CPName>"

The installer also lists the hotfixes that require a reboot of the system after the installation. If system reboot is not an option at this time, you can choose not to install these hotfixes. In such a case, exit the installation and then launch the CP installer again from the command line using the /exclude option.
See "To install in a non-verbose (silent) mode" section for the syntax.

[2] When the installer prompts whether you want to continue with the installation; type Y to begin the hotfix installation.
The installer performs the following tasks:
	- Extracts all the individual hotfix executable files
	  On 64-bit systems the files are extracted at %commonprogramfiles(x86)%\Veritas Shared\WxRTPrivates\<HotfixName>
	- Runs the pre-install tasks
	- Installs all the hotfixes sequentially
	- Runs the post-install tasks
The installation progress status is displayed in the command window.

[3] After all the hotfixes are installed, the installer prompts you to restart the system.
Type Y to restart the system immediately, or type N to restart the system later. You must restart the system for the changes to take effect.

Note that the installer prompts for a system restart only if hotfixes that require a reboot are included in the CP and are installed.

To install in the non-verbose (silent) mode
-------------------------------------------:
In the non-verbose (silent) mode, the cumulative public patch (CP) installer does not prompt you for inputs and directly proceeds with the installation tasks. The installer displays the installation progress status in the command window.

Use the VxHFBatchInstaller.exe utility to install a CP from the command line.
The syntax options for this utility are as follows:

vxhfbatchinstaller.exe /CP:<CPName> [/Exclude:<HF1.exe>,<HF2.exe>...] [/PreInstallScript:<PreInstallScript.pl>] [/silent [/forcerestart]]

where,
	- CPName is the cumulative public patch executable file name without the platform, architecture, and .exe extension.
For example, if CP executable file name is CP3_SFWHA_601_W2K8_x64.exe, specify it as CP3_SFWHA_601.

	- HF1.exe, HF2.exe,... represent the executable file names of the hotfixes that you wish to exclude from the installation. Note that the file names are separated by commas, with no space after a comma. The CP installer skips the mentioned hotfixes during the installation.

	- PreInstallScript.pl is the Perl script that includes the pre-installation steps. These steps forcefully kill the required services and processes in case a graceful stop request does not succeed.
    Symantec recommends that you use this option and script only in case the CP installer fails repeatedly while performing the pre-installation tasks.

	- /silent indicates the installation is run in a non-verbose mode; the installer does not prompt for any inputs during the installation.

	- /forcerestart indicates that the system is automatically restarted, if required, after the installation is complete.

	
Perform the following steps:
[1] From the command prompt, navigate to the directory where the CP executable file is located and then run the file to extract the contents to a default location on the system. The installer displays a list of hotfixes that are included in the CP.
	- On 64-bit systems, the hotfixes executable files are extracted to:
	  "%commonprogramfiles(x86)%\Veritas Shared\WxRTPrivates\<CPName>"

The installer also lists the hotfixes that require a reboot of the system after the installation. If system reboot is not an option at this time, you can choose not to install these hotfixes. In such a case, launch the CP installer from the command line using the /exclude option.

[2] When the installer prompts whether you want to continue with the installation; type N to exit the installer.

[3] In the same command window, run the following command to begin the CP installation in the non-verbose mode:
vxhfbatchinstaller.exe /CP:<CPName> /silent

For example, to install a SFW HA 6.0.1 x64 CP for Windows Server 2008, the command is:
vxhfbatchinstaller.exe /CP:CP3_SFWHA_601 /silent

The installer performs the following tasks:
	- Extracts all the individual hotfix executable files
          On 64-bit systems the files are extracted at %commonprogramfiles(x86)%\Veritas Shared\WxRTPrivates\<HotfixName>
	- Runs the pre-install tasks
	- Installs all the hotfixes sequentially
	- Runs the post-install tasks
The installation progress status is displayed in the command window.

[4] After all the hotfixes are installed, the installer displays a message for restarting the system.
You must restart the system for the changes to take effect.


Note that the installer prompts for a system restart only if hotfixes that require a reboot are included in the CP and are installed. The installer automatically restarts the system if you had specified the /forcerestart option in step 3 earlier.

VxHFBatchInstaller usage examples
----------------------------------:
[+] Install CP in silent mode, exclude hotfixes HotFix_6_0_00001_2763375_w2k8_x64.exe and Hotfix_6_0_00002_362_2705769_w2k8_x64.exe:

vxhfbatchinstaller.exe /CP:CP3_SFWHA_601/Exclude:HotFix_6_0_00001_2763375_w2k8_x64.exe, Hotfix_6_0_00002_362_2705769_w2k8_x64.exe /silent

[+] Install CP in silent mode, restart automatically:
vxhfbatchinstaller.exe /CP:CP3_SFWHA_601 /silent /forcerestart


Post-install steps
=================-|
The following section describes the steps that must be performed after installing the hotfixes included in this CP.

Ensure that VIP_PATH environment variable is set to "C:\Program Files\Veritas\Veritas Object Bus\bin" and NOT to "C:\<INSTALLDIR_BASE>\Veritas Object Bus\bin". Assuming that C:\ is the default installation drive.


Known issues
============|
The following section describes the issues related to the individual hotfixes that were included in the previous 6.0.1 CP1:

[1] Hotfix_6_0_10004_308_3124269, Hotfix_6_0_10003_308_3099805, and Hotfix_6_0_10001_308_3061942

 - These HFs were initially part of CP1 and they were re-archived in CP2 to ensure that VIP_PATH is set to correct value.

 - In CP1, after installing/un-installing these hotfixes, VIP_PATH environment variable was incorreclty getting set to "C:\<INSTALLDIR_BASE>\Veritas Object Bus\Bin" instead of "C:\Program Files\Veritas\Veritas Object Bus\Bin".



Errors/Problems fixed
=====================|
The fixes and enhancements that are included in this cumulative public patch (CP) are as follows:

[1] Hotfix name: HotFix_6_0_10002_3065921

Symptom:
VMwareDisks agent does not work if ESX is not on the same network as VM.

Description:
VMwareDisks agent accepts an ESXDetails attribute which contains the details of ESX to be used to perform online/offline operations. In case ESX is not accessible from the VM network, agent will not work.

Resolution:
VMwareDisks agent has been modified to work with vCenter details as well. ESXDetails attribute will now accept either ESX details or vCenter deatils. No attribute change is involved, the same attribute will be used.

Limitation - With vCenter given in the ESXDetails attribute, and if VMHA is not enabled, then if the ESX of the node where application is running faults, then the agent will not be able to detach disks from the faulted ESX's VM. Application failover will not be impacted. The subsequent power ON of the faulted ESX's VM will involve extra manual step to detach disks from the VM. Otherwise VM power ON will not go through.

Binary / Version:
VMwareDisks.dll / 6.0.10002.264
VMwarelib.dll /  6.0.10002.264

-------------------------------------------------------+ 

[2] Hotfix name: HotFix_6_0_10004_2938704

Symptom:
This hotfix addresses an issue where the MSMQ resource failed to bind to the correct port.

Description:
When the MSMQ agent was brought online, the Event Viewer reported an error stating that Message Queuing failed to bind to port 1801. This error could occur due to various reasons. Even though the binding failed, the agent reported the MSMQ resource as Online.

Resolution:
The MSMQ agent has been enhanced to verify that the clustered MSMQ service is bound to the correct virtual IP and port. By default, the agent performs this check only once during the Online operation. If the clustered MSMQ service is not bound to the correct virtual IP and port, the agent stops the service and the resource faults. You can configure the number of times that this check is performed. To do so, create the DWORD tunable parameter 'VirtualIPPortCheckRetryCount' under the registry key 'HKLM\SOFTWARE\VERITAS\VCS\BundledAgents\MSMQ'. If this parameter is set to a value greater than 1, the agent starts the clustered MSMQ service again and verifies its virtual IP and port binding as many times. It waits 2 seconds between each verification attempt. If the clustered MSMQ service is bound to the correct virtual IP and port, the agent reports Online.

Binary / Version:
MSMQ.dll / 6.0.10004.268

-------------------------------------------------------+

[3] Hotfix name: Hotfix_6_0_10005_3099727

Symptom:
[Issue 1] An online Lanman resource takes 1 minute or longer to go offline. [Issue 2] A newly created Lanman resource appears ONLINE even though the service group is not brought online.

Description:
The Lanman agent does not correctly identify the virtual name (configured under the Lanman resource) that is being monitored or taken offline on a cluster node. This happens if the following conditions are satisfied on the node where the operation is being performed: (a) NetBIOS over TCPIP (NetBT) is disabled on the network adapter. (b) The first few characters of the virtual name (for example, Site10_Svr_ExchApp) are identical to any other virtual name (configured under another Lanman resource) or physical computer name registered on the node (for example, Site10_Svr). No issues occur if the first few characters of the virtual name configured under the Lanman resource (for example, Site10_Svr_ExchApp) are not identical to any other computer name registered on the node (for example, Site10_Svr_EV or Site11_Svr).

Resolution:
The Lanman agent has been updated to correctly identify the Lanman resource on which an operation is being performed; it now reports the accurate resource status.

Binary / Version:
Lanman.dll / 6.0.10005.269

-------------------------------------------------------+

[4] Hotfix name: Hotfix_6_0_10006_3054751b

Symptom:
Windows Server Backup fails to perform a system state backup with the following error: Error in backup of C:\program files\veritas\\cluster server\ during enumerate: Error [0x8007007b] The filename, directory name, or volume label syntax is incorrect.

Description:
The backup operation fails because the VCS service image path contains an extra backslash (\) character, which Windows Server Backup is unable to process.

Resolution:
This issue has been fixed by removing the extra backslash character from the VCS service image path. 
This hotfix changes the following registry keys: 
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Had\ImagePath 
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HADHelper\ImagePath 
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Cmdserver\ImagePath 
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VCSComm\ImagePath

NOTE: 
#1. This hotfix supersedes Hotfix_6_0_10006_3054751a, which was released earlier.

-------------------------------------------------------+

[5] Hotfix name: Hotfix_6_0_10007_3164649

Symptom:
The Exchange 2010 Database Agent Configuration Wizard does not create a MountV resource for certain transaction logs.

Description:
This issue occurs only if the transaction logs folder of the Exchange 2010 database is located directly on the folder mount, instead of being located within another folder on the root drive.

Resolution:
The Exchange 2010 Database Agent Configuration Wizard has been updated to resolve this issue. It now creates the MountV resource for the transaction logs even if they are located in a subfolder on the root drive.

Binary / Version:
Exch2010Wizard.exe / 6.0.10007.274

-------------------------------------------------------+

[6] Hotfix name: Hotfix_6_0_10019_3334544

Symptom:
Issue 1:
Users are unable to add or modify custom settings on printers clustered under VCS.

Issue 2:
The memory usage of the PrintSpool agent increases continuously. This might result in a low virtual memory condition, following which the system reboots and a message similar to following error appears in the Event Viewer Log: Log Name: System Source: Microsoft-Windows-Resource-Exhaustion-Detector Event ID: 2004 Task Category: Resource Exhaustion Diagnosis Events Level: Warning Keywords: Events related to exhaustion of system commit limit (virtual memory). User: SYSTEM Computer: <system_name> Description: Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: VCSAgDriver.exe (<process_ID>) consumed <number_of_bytes> bytes

Fix for issue #1 was earlier released as Hotfix_6_0_10008_3186666. It is now included in this hotfix.

Description:
Issue 1:
When a printer with custom settings (like printing shortcuts) is added to VCS clustered virtual name, the printer settings become unavailable. This issue occurs because any customizations to printer settings are not recognized after a printer is clustered.

Issue 2:
The memory leak occurs only while adding or deleting printers, or while modifying printer settings.

Resolution:
Issue 1:
This hotfix addresses the issue. However, for the hotfix to work, you need to perform the following tasks manually. Create the following DWORD registry key and set its value to 1. - For global configurations, create: HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\VCS\BundledAgents\PrintSpool\__GLOBAL__\PrinterDriverSupport - For per resource configurations, create: HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\VCS\BundledAgents\PrintSpool\ <resource_name>\PrinterDriverSupport After creating this key, do one of the following: - If a PrintSpool resource if offline, bring it online. - If a PrintSpool resource is already online, probe it. Upon installing the hotfix, the PrintSpool agent creates the 'HKEY_LOCAL_MACHINE\Cluster' key. Make sure that the key exists, and then add printers to the virtual name. NOTE: Existing printers will continue to have this issue. Symantec recommends deleting and re-creating such printer resources. CAUTION: This hotfix may cause unexpected effects on other applications that can be clustered (or are already clustered) on the same node.

Issue 2:
This hotfix fixes the memory leak issue.

Binary / Version:
PrintSpool.dll / 6.0.10019.286

-------------------------------------------------------+

[7] Hotfix name: Hotfix_6_0_10010_3113887

Symptom:
After every 49.7 days, VCS logs report that the Global Counter VCS attribute is not updated. This error is reported on all nodes in the cluster, except the node with the lowest node ID value. The 'GloablCounter not updated' error also appears in the Event Viewer.

Description:
The error indicates that there could be communication issues between the cluster nodes. However, this error is incorrectly reported, and no communication issues actually occur.

Resolution:
This issue has been fixed and the error is no longer reported at that odd interval.

Binary / Version:
had.exe / 6.0.10010.277
hacf.exe / 6.0.10010.277

-------------------------------------------------------+

[8] Hotfix name: Hotfix_6_0_10001_308_3061942

Symptom:
Two issues related to storage migration of a volume with SmartMove enabled.

Description:
In some cases, the following two issues are observed when storage migration is performed for a volume (with operations, such as subdisk move, mirror resync, mirror attach, etc.) and SmartMove is enabled: 1. If the VCS MountV resource for the volume is brought offline, then the migration task completes abnormally and the volume may report data corruption. 2. If the data migration is performed for a volume of size 2 TB or greater, then the task never reaches 100% completion because of integer overflow while handling large offsets.

Resolution:
The two issues mentioned above have been fixed. The first has been fixed by adding correct handling of error conditions so that the task is aborted if the volume is taken offline. The second issue has been fixed by using a 64-bit variable for that purpose.

Binary / Version:
vxconfig.dll / 6.0.20002.76

-------------------------------------------------------+

[9] Hotfix name: Hotfix_6_0_10003_308_3099805

Symptom:
SFW and SFWHA 6.0.1 unable to identify Hitachi HUS VM LUNs as thin reclaimable.

Description:
This issue is regarding SFW and SFW HA 6.0.1 not able to identify the Hitachi Unified Storage VM (HUS VM) LUNs as thin reclaimable LUNs because thin provisioning and storage reclamation is not supported on Hitachi HUS VM LUNs.

Resolution:
The issue has been resolved by enhancing ddlprov.dll to add thin provisioning and storage reclamation support for the Hitachi HUS VM array.

Binary / Version:
ddlprov.dll / 6.0.10003.308

-------------------------------------------------------+

[10] Hotfix name: Hotfix_6_0_10004_308_3124269

Symptom:
Tagging of snapshot disks fails during the fire drill operation, because of which disk import also fails.

Description:
This issue occurs while performing the fire drill operations in case of hardware replication agents, which involve tagging of snapshot disks so that they can be imported separately from the original disks. Because of an issue with SFW, it does not write tags to the disks, and also proceeds without giving any error. Then, the import operation on the snapshot disks also fails because there are no disks present with the specified tag.

Resolution:
This was an existing issue where SFW did not write to disks that are marked as read-only. The issue has been resolved by allowing the fire drill tag to be written to a disk even if the disk is marked as read-only.

Binary / Version:
vxconfig.dll / 6.0.10004.308

-------------------------------------------------------+

[11] Hotfix name: Hotfix_6_0_10006_308_3231600

Symptom:
Memory leak occurs for SFW VSS provider while taking a VSS snapshot.

Description:
This issue occurs during a VSS snapshot operation when VSS is loading and unloading providers. The SFW VSS provider connects to VEA database during the loading and disconnects during the unloading of providers. Because of an issue in the VEA database cleanup during the unloading, the memory leak occurs.

Resolution:
This issue has been resolved so that now SFW VSS provider does not connect to and disconnect from VEA during every load and unload operation. Instead, it creates a connection at the beginning and disconnects when the Veritas VSS Provider Service (vxvssprovider.exe) is stopped.

Binary / Version:
vxvssprovider.exe / 6.0.10006.308

-------------------------------------------------------+

[12] Hotfix name: Hotfix_6_0_10013_3298600

Symptom:
The MountV resource faults when bringing a fire drill service group online at the DR site.

Description:
This issue occurs in case of folder mounts whose base mount is also configured under VCS and replicated. Even though the PurgeStaleMountPoints attribute for a MountV resource is set, the stale mount points are not cleared and the resource faults.

Resolution:
The hotfix addresses this issue, and a MountV resource no longer fails due to stale mount points.

Binary / Version:
MountV.dll / 6.0.10013.281

-------------------------------------------------------+

[13] Hotfix name: Hotfix_6_0_10014_3300849

Symptom:
A fire drill service group fails to come online, because a required MountV resource is in the UNKNOWN state.

Description:
This issue occurs because the Fire Drill Wizard does not set a required MountV attribute correctly when using mount points. The VMDGResName attribute is set to the MountV resource name that this MountV resource depends on, instead of the appropriate VVRSnap resource name.

Resolution:
The Fire Drill Wizard has been updated to set the correct value for the VMDGResName attribute of the MountV resource.

Binary / Version:
FireDrillVVRStep.dll / 6.0.10014.366
CCFEngine.exe.config

-------------------------------------------------------+

[14] Hotfix name: Hotfix_6_0_10009_3231486

Symptom:
The SQL Server 2008 Agent Configuration Wizard crashes with an "VCS component - SQL server 2008 Wizard has stopped working" error, after you click Next on the User Databases List panel.

Description:
This issue occurs while configuring a SQL Server service group (SQL Server 2008, 2008 R2, and 2012). The SQL Server 2008 Agent Configuration Wizard displays the instances of the selected SQL Server version and the corresponding installed services, on the SQL Server Instance Selection panel. If you select only the SQL Server instances and click Next, the wizard proceeds to the User Databases List panel. However, due an internal error the wizard crashes after you click Next on the User Databases List panel.

Resolution:
The wizard behavior is now modified to address this issue. Even if you select only the SQL Server instances on the SQL Server Instance Selection panel, the wizard now proceeds with the configuration without an error.

Binary / Version:
SQL2008Wizard.exe / 6.0.10009.280

-------------------------------------------------------+

[15] Hotfix name: Hotfix_6_0_10020_3369234

Symptom:
When adding the relevant services after the initial configuration, the VCS SQL Server 2008 Agent Configuration Wizard does not update the paths to the shared storage.

Description:
The initial SQL Server agent configuration was done, and the Analysis service was added. When the VCS SQL Server 2008 Agent Configuration Wizard was run again, although the resources were created, the paths for those resources were not in sync.

Resolution:
This hotfix resolves the issue by updating the OLAP path after running the initial configuration.

Binary / Version:
SQL2008Wizard.exe / 6.0.10020.289

-------------------------------------------------------+

[16] Hotfix name: Hotfix_6_0_10022_3386077

Symptom:
VMDg resource faults and goes offline unexpectedly in a fire drill configuration.

Description:
This issue occurs if multiple fire drill service groups are configured and kept online. In that case, the VMDg resource may fault and go offline unexpectedly.

Resolution:
A new VMDg attribute, ForFireDrill, has been introduced in this hotfix that resolves this issue. The ForFireDrill attribute defines whether the disk group being monitored by the agent is a fire drill disk group. The value 1 indicates that the disk group being monitored is a fire drill disk group. Default is 0, which means that the disk group being monitored is not a fire drill disk group. Note: After installing the hotfix and before performing a fire drill, manually set the ForFireDrill attribute as ‘true’ for the existing VMDg resources that belong to the fire drill service group.

Binary / Version:
VMDg.dll / 6.0.10022.291
VMDg.xml / NA

-------------------------------------------------------+

[17] Hotfix name: Hotfix_6_0_10010_308_3352705

Symptom:
"vxdmpadm disk list" may display the disk name multiple times and it may crash by itself.

Description:
On some system, "vxdmpadm disk list" may display the disk name multiple times and sometimes it may crashes by itself. This happens due to incorrect logic in vxcmd.dll, where vxdmpadm tries to access invalid memory.

Resolution:
This issue has been resolved by implementing correct logic code in vxcmd library.

Binary / Version:
vxcmd.dll / 6.0.10010.308

-------------------------------------------------------+

[18] Hotfix name: Hotfix_6_0_10011_308_3360992

Symptom:
Server crashes during high write I/O operations on mirrored volumes.

Description:
This issue occurs when heavy write I/O operations are performed on mirrored volumes. During such high I/O operations, the server crashes due to a problem managing the memory for data buffers.

Resolution:
This issue has been resolved by appropriately mapping the system-address-space described by MDL for the write I/Os on mirrored volumes.

Binary / Version:
vxio.sys / 6.0.10011.308

-------------------------------------------------------+

[19] Hotfix name: Hotfix_6_0_10012_308_3347495

Symptom:
After a failover, VEA sometimes does not show the drive letter or mounted folder paths of a successfully-mounted volume.

Description:
This issue may occur after a failover when VEA sometimes does not show the drive letter or mounted folder paths of a volume even though the volume is successfully mounted with the expected drive letter or folder paths. During a failover, when a disk group gets imported, SFW mounts all volumes of the disk group by querying the mount points using Microsoft API GetVolumePathNamesForVolumeName(). Sometimes, this API fails to return the correct drive letter or mounted folder paths because of which VEA fails to update the same.

Resolution:
NOTE: Please note that using the following workaround has a performance impact on the service group offline and failover operations. This happens because, during the service group offline or failover operation, the performance of the disk group deport operation is impacted by "n/2" seconds maximum, where "n" is the number of volumes in the disk group. To resolve this issue, the operation needs to be retried after a few milliseconds so that the Microsoft API GetVolumePathNamesForVolumeName() returns correct information. As a workaround, a new retry logic is added to the GetVolumePathNamesForVolumeName() API so that it retries the operation in case the mount path returned is empty. It will retry after every 100 milliseconds for "n" number of attempts (5 by default), which can be configured using the registry. This retry logic is disabled by default.

To use the workaround, do the following:
1. Enable the retry logic by changing the value of the registry entry "RetryEnumMountPoint" from 0 to 1 under the registry key 
- HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\VxSvc\CurrentVersion\VolumeManager
2. Configure the number of retry attempts by changing the value of the registry entry "RetryEnumMPAttempts" under the registry key
- HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\VxSvc\CurrentVersion\VolumeManager


Binary / Version:
mount.dll / 6.0.10012.308

-------------------------------------------------------+


Additional notes
================|
[+] To confirm the list of patches installed on a system, run the following command from the directory where the CP files are extracted:
vxhfbatchinstaller.exe /list

The output of this command displays a list of patches and the hotfixes that are installed as part of a CP. 
This command also displays the hotfixes that are included in a CP but are not installed on the system.

[+] To confirm the installation of the hotfixes, perform one of the following:
	- Run the following command:
	  vxhf.exe /list
	  The output of this command lists the hotfixes installed on the system.
	- In the Windows Add/Remove program, click "View installed updates" to view the list of the hotfixes installed on the system.

[+] The CP installer (vxhfbatchinstaller.exe) creates and stores logs at:
"%allusersprofile%\Application Data\Veritas\VxHF\VxHFBatchInstaller.txt"

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

[+] For general information about the hotfix installer (vxhf.exe), please refer to the following technote:
http://www.symantec.com/docs/TECH73446

[+] To view a list of hotfixes already installed on a system, please refer to the steps mentioned in the following technote:
http://www.symantec.com/docs/TECH73438

[+] For information on uninstalling a hotfix, please refer to the steps mentioned in the following technote:
http://www.symantec.com/docs/TECH73443


Disclaimer
==========|
This fix is provided without warranty of any kind including the warranties of title or implied warranties of merchantability, fitness for a particular purpose and non-infringement. Symantec disclaims all liability relating to or arising out of this fix. 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 if you sign up for notifications from the Symantec support site http://www.symantec.com/business/support and/or from Symantec Operations Readiness Tools (SORT) http://sort.symantec.com.



Read and accept Terms of Service