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.
sf-win_x64-CP11_SFW_60
Obsolete
The latest patch(es) : sf-win_x64-CP14_SFW_60 
Sign in if you want to rate this patch.

 Basic information
Release type: P-patch
Release date: 2014-02-24
OS update support: None
Technote: TECH191975 - Storage Foundation for Windows High Availability, Storage Foundation for Windows and Veritas Cluster Server 6.0 Cumulative Patches
Documentation: None
Popularity: 627 viewed    46 downloaded
Download size: 41.31 MB
Checksum: 1438711105

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

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

This patch is obsolete. It is superseded by: Release date
sf-win_x64-CP12_SFW_60 (obsolete) 2014-04-30

This patch supersedes the following patches: Release date
sfw-win_x64-CP10_SFW_60 (obsolete) 2014-01-06
sfw-win_x64-CP9_SFW_60 (obsolete) 2013-09-26
sfw-win_x64-CP8_SFW_60 (obsolete) 2013-08-26
sfw-win_x64-CP7_SFW_60 (obsolete) 2013-07-29
sfw-win_x64-CP6_SFW_60 (obsolete) 2013-06-24
sfw-win_x64-CP5_SFW_60 (obsolete) 2013-04-29
sfw-win_x64-CP4_SFW_60 (obsolete) 2013-02-26
sfw-win_x64-CP3_SFW_60 (obsolete) 2012-09-24
sfw-win_x64-CP2_SFW_60 (obsolete) 2012-08-29

 Fixes the following incidents:
2593039, 2677127, 2704183, 2713791, 2715104, 2730657, 2736679, 2740833, 2744349, 2752096, 2755133, 2763375, 2783096, 2791125, 2791301, 2810516, 2845295, 2869461, 2871478, 2877405, 2885211, 2897781, 2904593, 2912682, 2913240, 2919276, 3082932, 3105024, 3137880, 3160235, 3202548, 3210766, 3226691, 3252941, 3377535, 3378041, 3381786, 3421570, 3431608

 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-02-24
OS: Windows
OS Version: 2008, 2008 R2
Packages:

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

Etrack Incidents: 
2715104, 2763375, 2677127, 2704183, 2736679, 2713791, 2730657, 2740833, 2752096, 
2744349, 2791301, 2783096, 2810516, 2755133, 2845295, 2593039, 2869461, 2877405, 
2871478, 2885211, 2791125, 2904593, 2913240, 2919276, 2897781, 2912682, 3082932,
3137880, 3160235, 3202548, 3210766, 3226691, 3105024, 3252941, 3377535, 3378041,
3381786, 3421570, 3431608




Fixes Applied for Products
==========================|
Storage Foundation (SFW) 6.0 for Windows


What's new in this CP
=====================|

The following hotfixes have been added in this CP:
 - Hotfix_6_0_00035_362_3381786
 - Hotfix_6_0_00036_362_3421570
 - Hotfix_6_0_00037_362_3431608

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 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 name is CP11_SFW_60_W2K8_x64.exe, specify it as CP11_SFW_60.

	- 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 6.0 x64 CP for Windows Server 2008, the command is:
vxhfbatchinstaller.exe /CP:CP11_SFW_60 /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_00001_2763375_w2k8_x64.exe:

vxhfbatchinstaller.exe /CP:CP11_SFW_60 /Exclude:HotFix_6_0_00001_2763375_w2k8_x64.exe, HotFix_6_0_00001_2763375_w2k8_x64.exe /silent

[+] Install CP in silent mode, restart automatically:

vxhfbatchinstaller.exe /CP:CP11_SFW_60 /silent /forcerestart


Known issues
============|
The following section describes the issues related to the individual hotfixes that are included in this CP:

[1] The post-installation task of starting the Plugin-Host service fails on Windows Server Core system.

The Plugin-Host service requires that the .NET Framework is present on the system where the service is to be started. As the .NET Framework is not supported on the Windows Server Core systems, the service cannot be started on these systems. Hence for the hotfixes that have the post-installation task of starting the Plugin-Host service, the task fails. This is expected behavior and can be safely ignored.


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

[1] Hotfix name: Hotfix_3_4_531_0_2715104

Symptom:
VEA GUI prompts for login credentials when a logged-in user or domain administrator connects to VEA server.

Note:
Please note that if you have set up SFW cluster environment for Microsoft Clustering or VCS, then you must install the hotfix Hotfix_6_0_00005_362_2736679 before installing this hotfix.

Description:
In Veritas Storage Foundation for Windows 6.0, this issue occurs when a logged-in user or domain administrator connects to a Veritas Enterprise Administrator (VEA) server through the VEA GUI. The VEA GUI prompts for login credentials each time the user connects to a VEA server. 
This happens if the DCOM-based authentication in VEA GUI fails and the existing 32-bit midlman.dll for VEA server cannot be loaded into the 64-bit VEA VxSVC service.

Resolution:
The DCOM-based authentication is enabled in VEA GUI and, in addition to the 32-bit midlman.dll, a 64-bit midlman64.dll is added for the server component so that it is loaded into VxSVC service.

Note: 
This hotfix is applicable to server components only. 
A separate hotfix is available for client components. Contact Symantec Technical Support for more details.

Binary / Version:
midlman64.dll / 3.4.531.0 
ci.jar	/ 3.4.29.0  
cicustom.jar / 3.4.29.0 
obCommon.jar / 3.4.29.0 
OBGUI.jar / 3.4.29.0

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

[2] Hotfix name: HotFix_6_0_00001_2763375

Symptom:
The Fire Drill, Disaster Recovery, and Quick Recovery wizards, and the Solutions Configuration Center did not support Microsoft SQL Server 2012.

Description:
Need to provide support for SQL Server 2012 in the Fire Drill, Disaster Recovery, and Quick Recovery wizards, and the Solutions Configuration Center. 

Resolution:
Added support for SQL Server 2012 in the Fire Drill, Disaster Recovery, and Quick Recovery wizards, and the Solutions Configuration Center.

Note 1: For the Quick Recovery wizard to function properly with SQL Server 2012, you must apply Hotfix_6_0_00011_363_2744349 along with this hotfix.
Note 2: This hotfix is applicable to server components only. A separate hotfix is available for client components. Contact Symantec Technical Support for more details.

Binary / Version:
DRPluginProxy.dll / 6.0.1.709
FireDrillStep.dll / 6.0.1.709
qrpages.dll / 6.0.0.701 
QuickRecovery.dll / 6.0.1.709
CCFEngine.exe.config / NA

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

[3] Hotfix name: Hotfix_6_0_00001_362_2677127

Symptom:
This hotfix addresses an issue related to the SFW component, mount.dll, that causes the Veritas Enterprise Administrator (VxSvc) Service to crash if pagefile is not configured.

Description:
This issue occurs when the VxSVC service starts without a configured pagefile.
The vxsvc.exe service crashes because of an exception in mount.dll.

Resolution:
VxSvc service used to crash because an empty string variable was passed to free function. 
The component has been updated to address the issue.

Binary / Version:
mount.dll / 6.0.00001.362

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

[4] Hotfix name: Hotfix_6_0_00002_362_2705769

Symptom:
The Quick Recovery Configuration Wizard fails to create snapshot schedules on ApplicationHA-managed node.

Description:
When Veritas Storage Foundation for Windows (SFW) 6.0 is installed on the Symantec ApplicationHA 6.0 managed node, the Quick Recovery Configuration Wizard fails to create snapshot schedules for the application.

The wizard displays the following error messages:
- Failed to Create, Modify or Delete volume settings for one or more schedules
- Failed while getting cluster related information for the application

Resolution:
The VxSnapSchedule.dll file has been updated to address the issue.

Binary / Version:
VxSnapSchedule.dll / 6.0.00002.362 

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

[5] Hotfix name: Hotfix_6_0_00004_364_2704183

Symptom:
In some cases, Microsoft Failover Cluster disk resources fault when a disk group comes online.

Note:
If you have set up SFW cluster environment for Microsoft Clustering or VCS, then you must install the hotfix Hotfix_6_0_00005_362_2736679 before installing this hotfix.

Description:
In some cases, while importing a disk group, Storage Foundation for Windows (SFW) clears the reservation of all the disks except those belonging to the imported disk groups. It also clears the reservation of offline  and basic disks. However, Microsoft Failover Cluster disk resources, which contains the basic disks, do not try to re-reserve the disks and, therefore, they fault.

The following are some of the scenarios in which this may happen:
1. A new disk group is created.
2. The Veritas Enterprise Administrator (VEA) VxSVC service on a node or the node itself crashes, and a failover is triggered.
3. The storage is disconnected from one of the nodes and a failover is triggered.

Resolution:
For the first scenario above, no reservation clearing is required, and it has been fixed.
For the other scenarios where reservations need to be cleared, SFW skips the disks that are offline or basic.

Binary / Version:
vxconfig.dll / 6.0.4.363 

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

[6] Hotfix name: Hotfix_6_0_00005_362_2736679

Symptom:
In a clustered environment, hotfix installation fails as the installer cannot stop the VxSVC service.

Description:
This issue occurs while installing a hotfix, during which the installer stops the Veritas Enterprise Administrator (VEA) VxSVC service for updating binaries. However, if Microsoft Failover Cluster is configured or the Microsoft Failover Cluster option is selected during the SFW installation, then the cluster service (clussvc) needs to be stopped before the VxSVC service is stopped. In such cases, VxSVC fails to stop if clussvc is already stopped. 
Therefore, the hotfix installation fails.

Resolution:
This issue has been resolved by properly stopping the cluster provider module for the VxSVC service stop request.

Binary / Version:
cluster.dll / 6.0.00005.362

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

[7] Hotfix name: Hotfix_6_0_00006_368_2713791

Symptom:
This hotfix addresses an issue wherein mount points created on a local system drive are lost after a system reboot or on performing several Live Migration operations on Hyper-V virtual machines in a Microsoft Failover Cluster (FOC) environment.

Note:
If you have set up SFW cluster environment for Microsoft Clustering or VCS, then you must install the hotfix Hotfix_6_0_00005_362_2736679 before installing this hotfix.

Description:
This issue occurs where SFW is used to manage storage for Microsoft Hyper-V virtual machines in a Microsoft Failover Cluster environment.
If Hyper-V virtual machines are stored on mount points that reside on local system drives (C:\ for example), then these mount points are lost after a system reboot or on performing several Live Migration operations between the cluster nodes. 
Due to the loss of mount points, the live migration does not work and the virtual machines fail to start.
This issue occurs because in a Microsoft Hyper-V cluster environment, mount points created on local system drive do not persist after a system reboot.

Resolution:
This issue has been addressed; SFW now does not delete the mount point information during an offline or after a system reboot.

Binary / Version:
vxres.dll / 6.0.6.368

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

[8] Hotfix name: Hotfix_6_0_00007_362_2730657a

Symptom:
This hotfix addresses an issue where volumes created on LUNs exposed from a Hitachi Open-V array are not track aligned.

Note:
If you have set up SFW cluster environment for Microsoft Clustering or VCS, then you must install the hotfix Hotfix_6_0_00005_362_2736679 before installing this hotfix.

Description:
LUNs belonging to a Hitachi array are being discovered by SFW with ProductID as OPEN instead of OPEN-V. This causes track alignment to ignore the arrays and set  the Veritas Disk ID and Product ID (VDID/PID) as DEFAULT. 
The track alignment is set to the default offset of 64 instead of the recommended value of 128.
As a result volumes created on this array are not track aligned.

Resolution:
This issue has been addressed in the SFW binary Hitachi.dll that discovers Hitachi arrays. 
SFW now correctly discovers and identifies Hitachi Open-V arrays.

Binary / Version:
Hitachi.dll / 6.0.7.362

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

[9] Hotfix name: Hotfix_6_0_00008_362_2740833

Symptom:
VxSVC service fails to start because DDLProv provider does not load.

Description:
This issue occurs when the VEA VxSVC service is loading the SFW providers during startup. 
During this, the DDLProv provider fails to load while copying the SCSI mode page 0x31 response for the connected Fujitsu DX400 disks. 
This happens because of the provider's incorrect buffer size.

Resolution:
This issue has been resolved by modifying the buffer size of the DDLProv provider. 

Binary / Version:
ddlprov.dll / 6.0.8.362 

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

[10] Hotfix name: Hotfix_6_0_00010_363_2752096

Symptom:
Memory leak occurs in the SFW components vxvds.exe, vxvdsdyn.exe; the vxvdsdyn.exe component crashes.

Description:
This issue occurs if you repeatedly perform the create and delete volume operations multiple times. 
Because of this, memory leak occurs in the VDS Dynamic software provider (vxvds.exe) and Super VDS provider  (vxvdsdyn.exe) components. 
Also, the Super VDS provider (vxvdsdyn.exe) component crashes.

Resolution:
Most of the memory leak issues have been fixed in the vxvds.exe and vxvdsdyn.exe components. 
The components have been updated to address the memory leak issue. 
Also, the vxvdsdyn.exe component has been updated so that it does not crash.

Binary / Version:
vxcmd.dll / 6.0.00010.363   
vxvds.exe / 6.0.00010.363
vxvdsdyn.exe / 6.0.00010.363 
mount.dll / 6.0.00010.363
vxvm.dll / 6.0.00010.363   

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

[11] Hotfix name: Hotfix_6_0_00011_363_2744349

Symptom:
This hotfix addresses several issues where SFW snapshot and scheduling operations fail for Microsoft SQL Server 2012 databases.

Description:
The following SFW issues may occur for SQL Server 2012 databases: 
- While running the restore operation with the automatic log replay, the vxsnap command fails to bind to the SQL Server instance and as a result the restore operation is unable to complete and the SQL database remains in the restoring state. 
The following error is logged: 
Failed to complete the operation V-76-58657-1059: Error trying to bind to the SQL Server Instance. 

This issue occurs because SFW is unable to discover a change in a SQL registry value created during SQL Server installation. 
- Schedules created using the Quick Recovery (QR) Configuration Wizard fail to execute. 
- Schedules created using the Quick Recovery (QR) Configuration Wizard or the Veritas Enterprise Administrator (VEA) are not replicated across cluster nodes.

Resolution: These issues have been fixed in the updated SFW binaries. 

For the changes in this hotfix to take effect, ensure that the [NT AUTHORITY\SYSTEM] account is granted "sysadmin" server role (from SQL Management Studio Console). 

Binary / version:
vssprov.dll / 6.0.00011.363
vxsnapschedule.dll / 6.0.00011.363 
vxschedservice.exe / 6.0.00011.363

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

[12] Hotfix name: Hotfix_6_0_00013_362_2791301

Symptom:
In VEA GUI, commands to deport and destroy a dynamic disk group are unavailable even if Volume Manager disk group resource is removed from failover clustering

Description:
In a clustered environment, this issue occurs while trying to deport or destroy a dynamic disk group using the Veritas Enterprise Administrator (VEA) GUI. 
In the VEA GUI, the Deport Dynamic Disk Group and Destroy Dynamic Disk Group commands are unavailable even if the Volume Manager disk group resource is removed from Microsoft failover clustering, both from “Services and Applications” and “Storage”. This happens because the "VXATTR_IS_CLUSTER_RESOURCE_BOOL" property does not get updated correctly.

Resolution: The "VXATTR_IS_CLUSTER_RESOURCE_BOOL" property has been updated to resolve this issue.

Binary Name / Version:
cluster.dll / 6.0.13.362

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

[13] Hotfix name: Hotfix_6_0_00015_362_2783096

Symptom:
The Storage Migration Wizard pages appear truncated.

Description:
This hotfix addresses an issue where the Storage Migration Wizard pages appear truncated, as a result it is not possible to perform the storage migration tasks using the wizard. 
This issue is observed on operating systems where the locale is set to Japanese.

Resolution: The hotfix fixes the Storage Migration Wizard binaries. 

Binary / Version:
VxVmCE.jar / NA

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

[14] Hotfix name: Hotfix_6_0_00016_362_2810516

Symptom:
Snapback operation causes too many blocks to resynchronize for the snapback volume.

Description:
During a snapback operation, SFW determines the blocks to be synced using the Disk Change Object (DCO) logs, which maintain information about the changed blocks. It syncs all the changed blocks from the original volume to the snapback volume and, because of a bug, also updates the DCO logs so that the resynced blocks appear modified on the original volume.
Now, if there is another volume on which a snapback operation needs to be performed, then it copies extra blocks on the new snapback volume.

For example, consider the following scenario:
1. Create two snapshots of volume "F" (snapshots "G" and "H").
2. Make "G" writable, and copy files to "G".
3. Snapback "G" using data from "F".
4. Snapback "H" using data from "F".

In the above scenario, in Step 4, there should be nothing to resynchronize as no changes are made to "F" and "H". However, it is observed that the number of blocks to be synchronized is the same as in Step 3. This is because the blocks resynced in Step 3 are treated as modified. 
This causes the extra blocks to be resynced.

Resolution: For a snapback operation, corrected the DCO log handling to not treat the resynced blocks as modified.

Binary / Version:
vxio.sys / 6.0.16.362
vvxconfig.dll / 6.0.16.362

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

[15] Hotfix name: Hotfix_6_0_00017_362_2845295

Symptom:
VxSVC service crashes during disk group import and during the subsequent restart.

Description:
This issue occurs while trying to import a disk group. The maximum buffer size value of the "LastUpdatedDgList" key is set to 1024 at the following registry path: HKLM\SOFTWARE\VERITAS\VxSvc\CurrentVersion\VolumeManager\CBR If you have several disk groups with lengthy names and the combined length of all the disk group names is greater than 1024, then it results in a buffer overrun in the Volume Manager for Windows (vxvm) provider specific to the VxCBR code. Because of this, the Veritas Storage Foundation for Windows (VxSVC) service crashes. The service crashes again when you try to restart it.

Resolution: 
This issue has been resolved by allocating buffer dynamically.

Binary / Version:
vxvm.dll / 6.0.00017.362

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

[16] Hotfix name: Hotfix_6_0_00018_362_2593039

Symptom:
Provisioned size of disks is reflected incorrectly in striped volumes after thin provisioning reclamation.

Description:
This hotfix addresses an issue where thin provisioning (TP) reclamation in striped volumes shows incorrect provisioned size for disks. This issue is observed on Hitachi and HP arrays.

Resolution: 
This issue has been fixed by increasing the map size for striped volumes.

Binary / Version:
vxconfig.dll / 6.0.00018.362

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

[17] Hotfix name: Hotfix_6_0_00019_362_2869461

Symptom:
Veritas VDS software provider log file grows to a very large size.

Description:
This hotfix addresses an issue where the Veritas Virtual Disk Service (VDS) software provider keeps logging in the log file without checking its size or recycling it.  This results in a very large log file. 

Resolution: 
The hotfix fixes the issue with the help of the following two registry keys that tune the VDS software provider logging:

1. MAXSIZE gives the maximum size of an individual log file in KB units. A backup log file is created when the log file exceeds the default size. The default value of MAXSIZE is 16384 KB. However, you can customize the default value by running the command Regedit to open the registry editor. Locate the MAXSIZE of the VDS software provider in the registry under the following key:
SOFTWARE\Veritas\VxSvc\CurrentVersion\Tracing\vds\MaxSize

2. MAXFILES gives the maximum number of log files that can be present at a time.
The old log files are deleted once they exceed the limit of maximum number of files. The default value of MAXFILES is 5. However, you can customize the default value by running the command Regedit to open the registry editor. Locate the MAXFILES of the VDS software provider in the registry under the following key:
SOFTWARE\Veritas\VxSvc\CurrentVersion\Tracing\vds\MaxFiles

The Veritas VDS software provider logs are found at:
Location: %vmpath%/log
Filenames: vxvds.log and vxvdsdyn.log

Binary / Version:
vdsprovutil.dll / 6.0.00019.362

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

[18] Hotfix name: Hotfix_6_0_00020_362_2877405

Symptom:
svchost.exe crashes because of a fault in shsvcs.dll.

Description:
This hotfix addresses the issue where svchost.exe crashes because of a fault in shsvcs.dll. This issue occurs when shsvcs calls COM interface to query disk extents, causing the WMI and Hardware shell detection services to terminate unexpectedly.

Resolution: 
The hotfix fixes the binaries that caused svchost.exe to crash.

Binary / Version:
vxvds.exe / 6.0.00020.362 
vxvdsdyn.exe / 6.0.00020.362

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

[19] Hotfix name: Hotfix_6_0_00022_362_2871478

Symptom:
Volume shrink operation in SFW does not work correctly for the "New volume size" option.

Description:
In Storage Foundation for Windows (SFW), this issue occurs if you are using the "New volume size" option of the online volume shrink feature. When you provide the new size for the volume in the "New volume size" box, the volume shrink operation incorrectly shrinks the volume by the new volume size instead of shrinking it by the difference of the current and the specified new size of the volume.

Resolution: 
This issue has been resolved by correcting the online volume shrink functionality.

Binary / Version:
VxVmCE.jar / NA

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

[20] Hotfix name: Hotfix_6_0_00023_362_2885211

Symptom:
In some cases, Windows prompts to format the volume created using VEA.

Description:
In SFW, while creating a volume using the New Volume Wizard from the Veritas Enterprise Administrator (VEA), if you choose to assign a drive letter or mount the volume as an empty NTFS folder, then Windows wrongly prompts to format the volume. This happens because, as part of volume creation, SFW creates RAW volumes, assigns mount points, and then proceeds with the formatting of volumes. Therefore, mounting RAW volumes explicity causes Windows to display the volume format dialog box. However, the volume is successfully created, and you can close the dialog box displayed by Windows and access the volume.

Resolution: 
This issue has been resolved. SFW now assigns drive letters or mount paths only after the volume formatting task is completed.

Binary / Version:
vxvm.dll / 6.0.00023.362

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

[21] Hotfix name: Hotfix_3_4_545_0_2791125

Symptom:
Memory leak occurs in the SFW component vxsvc.exe.

Description:
This issue occurs in SFW when you perform an action repeatedly and multiple times. Because of this, memory leak occurs in actionprovider.dll and, therefore, in vxsvc.exe.

Resolution: 
This issue has been resolved by fixing the memory leak in actionprovider.dll and deleting the event notification jobs immediately on completion. 

Binary / Version:
vxvea3.dll / 3.4.545.0 
actionprovider.dll / 3.4.545.0

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

[22] Hotfix name: Hotfix_6_0_00024_362_2904593

Symptom:
SFW is unable to discover the EMC Symmetrix LUNs as thin reclaimable, having firmware version 5876.

Description:
This hotfix addresses an issue where EMC Symmetrix array, after a firmware upgrade to version 5876, is unable to identify the thin provisioning reclaimable LUNs.

Resolution:
The hotfix enhances an SFW library to identify the EMC Symmetrix thin reclaimable LUNs having firmware version 5876.

Binary / Version:
ddlprov.dll / 6.0.00024.362

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

[23] Hotfix name: Hotfix_6_0_00026_362_2913240

Symptom:
MountV resource faults because SFW removes a volume due to delayed device removal request.

Description:
This issue occurs when SFW removes a volume in response to a delayed device removal request. Because of this, the VCS MountV resource faults.

Resolution:
This issue has been resolved by not disabling the mount manager interface instance if it is active when the device removal request arrives.

Binary / Version:
vxio.sys / 6.0.00026.362 
vxconfig.dll / 6.0.00026.362

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

[24] Hotfix name: Hotfix_6_0_00025_362_2919276

Symptom:
Dynamic disk groups created on external disks are not supported in VMNSDg agent.

Description:
Currently, the VMNSDg (Volume Manager Non-Shared Diskgroup) agent does not support the dynamic disk groups created on external disks.

Resolution:
This issue has been resolved by removing the cluster disk group check from SFW for the VMNSDg agent requests.

Binary / Version:
cluscmd.dll / 6.0.00025.362

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

[25] Hotfix name: HotFix_6_0_00015_2897781

Symptom:
Dynamic disk groups created on external disks are not supported in VMNSDg agent.

Description:
Currently, the VMNSDg (Volume Manager Non-Shared Diskgroup) agent does not support the dynamic disk groups created on external disks.

Resolution:
To support the dynamic disk groups configured on external disks, the hotfix installer adds the SkipStorageValidation attribute to the VMNSDg agent. By default, this attribute blocks the configuration of disk groups containing external disk (shared or non-shared). In case of SCSI controllers, the disks are considered as internal (non-shared) if they are attached to the same controller as the boot/OS disk, while all the other disks are considered as external. In case of IDE controllers, all the disks are considered as internal.

To allow configuration of VMNSDg resource on the dynamic disk groups with external disks, set the SkipStorageValidation attribute to True. Once the attribute is set, the agent shall not differentiate between internal or external disks. 

Note 1: Please use this attribute with caution. If not configured properly, this attribute can lead to data corruption in certain scenarios, such as split-brain.
Note 2: This hotfix depends on Hotfix_6_0_00025_362_2919276.

Binary / Version:
VMNSDg.dll / 6.0.00015.524
VMNSDg.xml / 6.0.00015.524
IMFCommon.dll / 6.0.00015.524
vcs_w2k3bagents_msgs_en.dll / 6.0.00015.524

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

[26] Hotfix name: Hotfix_3_4_564_0_2912682 

Symptom:
In some cases, capacity monitoring email notification fails

Description:
This issue occurs when the capacity monitoring feature is enabled so that when the used disk space on a volume reaches a user-specified threshold, an email alert message is sent. However, for some SMTP servers, the email notification for capacity monitoring fails with the following error message even if the provided email addresses of the recipients were valid: No valid recipients. Because Action Provider does not enclose recipient email addresses in angle brackets (< >) in the RCPT command, the SMTP server rejects the email addresses though they are valid.

Resolution:
The issue has been resolved by modifying Action Provider so that it now encloses recipient email addresses in angle brackets.

Binary / Version:
actionprovider.dll / 3.4.564.0

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

[27] Hotfix name: Hotfix_6_0_00027_362_3082932

Symptom:
Data corruption may occur if the volume goes offline while a resynchronization operation is in progress.

Description:
This issue occurs where SFW SmartMove is enabled and data resynchronization operations such as subdisk move, mirror resync, or mirror attach are being performed on a volume. If the volume goes offline (for example, because the MountV resource of the volume went offline) while a resync operation is in progress, the resync task completes abnormally and the volume may report data corruption. The task progress on the GUI may suddenly jump to 100%, but the actual task does not complete. This issue occurs due to improper error handling by SFW.

Resolution:
This issue has been fixed by adding correct handling of error conditions.


Binary / Version: 
vxconfig.dll / 6.0.00027.362

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

[28] Hotfix name: Hotfix_6_0_00028_362_3137880

Symptom:
Tagging of snapshot disks fails during the fire drill operation, causing disk import to fail.

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

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

[29] Hotfix name: Hotfix_6_0_00029_362_3160235

Symptom:
On an EMC SRDF setup, VEA VxSVC service may crash during a rescan if there are stale records on Secondary node.

Description:
In an SFW HA environment with the EMC SRDF agent, this issue may occur when a rescan (automatic or manual) is performed on the Secondary node and the node holds some stale records. During the rescan, the Veritas Enterprise Administrator service (VxSVC) tries to access the stale records on the Secondary. As the records contain invalid data, VxSVC crashes.

Resolution:
This issue has been resolved by modifying the affected binary so that the VxSVC service now ignores the stale records.

Binary / Version:
vxconfig.dll / 6.0.00029.362 

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

[30] Hotfix name: Hotfix_6_0_00030_362_3202548

Symptom:
Missing disks cannot be removed from a disk group using the vxdg rmdisk command.

Description:
This issue occurs when you try to remove a missing disk from a disk group using the vxdg rmdisk command. In the command, you need to mandatorily provide the name of disk group that the missing disk needs to be removed from. Despite providing the correct disk group name, the command fails because of a bug in the internal check performed for the disk group name.

Resolution:
This issue has been resolved by modifying the way a missing disk can be removed from a disk group. With this hotfix, while using the vxdg rmdisk command, you can remove a missing disk from a disk group either by specifying only its display name (for example, "Missing Disk (disk#)") or by specifying both its internal name and name of the disk group to which it belongs.

Binary / Version:
vxdg.exe / 6.0.00030.362 

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

[31] Hotfix name: Hotfix_6_0_00031_363_3210766

Symptom:
On a system with multiple DRL-enabled volumes, a write I/O hang may occur on one of the volumes when write I/O operations are happening on all the volumes.

Description:
This issue may occur on a system that has multiple volumes with dirty region logging (DRL) added. When heavy write I/O operations are happening on the DRL-enabled volumes, the writes are processed first by the DRL module and then they are written to the disk. If the I/O writes exceed the maximum limitation of I/Os that the DRL module can process, then the next I/O write for a DRL-enabled volume gets stuck in the retry queue of the volume and subsequently hangs on the system.

Resolution:
This issue has been fixed by maintaining a global retry queue and restarting the write I/O operations when any write I/Os complete in the DRL module.

Binary / Version:
vxio.sys / 6.0.31.363
vxconfig.dll / 6.0.31.363 

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

[32] Hotfix name: Hotfix_3_4_554_0_3226691

Symptom:
VEA GUI may time out while connecting to a server.

Description:
In some cases, when you try to log on to the VEA GUI, the connection times out while it is trying to connect to the VxSVC service on an SFW server. This happens if, during the connection, the process of SSL initialization takes a long time and exceeds the connection timeout value of 30 seconds. 

Resolution:
This issue has been resolved by optimizing the SSL initialization process so that now it happens when the VxSVC service is starting up rather than during the VEA GUI connection.

Binary / Version:
vxvea3.dll / 3.4.554.0

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

[33] Hotfix name: Hotfix_6_0_00021_3105024c

Symptom:
The Disaster Recovery (DR) wizard and the Fire Drill (FD) wizard fail when you run them in an environment that contains a hardware replication setup.

Description:
When a large number of LUNs are discovered in a hardware replication setup, a buffer overflow occurs that causes the Plugin Host service used by the DR and FD wizards to crash.

Resolution:
This issue has been fixed and the DR and FD wizards can now successfully complete their respective configurations.

Binary / Version:
CommonUtility.dll / 6.0.00021.733
clusffconfigrator.exe.config 

NOTE: 
#1. This hotfix depends on HotFix_6_0_00001_2763375. 
#2. This hotfix supersedes Hotfix_6_0_00021_3105024, Hotfix_6_0_00021_3105024a, and Hotfix_6_0_00021_3105024b which were released earlier.

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

[34] Hotfix name: Hotfix_6_0_00032_362_3252941

Symptom:
In a Microsoft Failover Cluster environment, creating a virtual machine fails if the volume has folder mount points.

Description:
In a Microsoft Failover Cluster environment, when you try to create a virtual machine where the volume has folder mount points, Microsoft Failover Cluster sends the IOCTL_DISK_GET_DRIVE_LAYOUT_EX control code. Because of an improper handling of the IOCTL control code, the virtual machine creation fails and incorrect error messages are sent for the code requests. For the boot devices, when checking for the buffer size, incorrectly the VKE_EINVAL message is sent instead of STATUS_BUFFER_TOO_SMALL. For the non-boot devices, the request is not processed and, incorrectly, the VKE_ENXIO message is sent. The following are the error message values and their descriptions: VKE_EINVAL: An invalid parameter was passed to a service or function. STATUS_BUFFER_TOO_SMALL: The buffer is too small to contain the entry. No information has been written to the buffer. VKE_ENXIO: The specified request is not a valid operation for the target device.

Resolution:
This issue has been fixed by correcting the handling of the IOCTL control code. Now, for the boot devices, when checking for the buffer size, the STATUS_BUFFER_TOO_SMALL message is sent if the supplied buffer is small. And for the non-boot devices, the request is processed successfully by passing the call to the next layer of drivers in the stack.

Binary / Version:
vxio.sys / 6.0.00032.362

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

[35] Hotfix name: Hotfix_6_0_00033_362_3377535

Symptom:
In a disaster recovery fire drill configuration, the disks containing the snapshot of the replicating data appear offline and the SRDFSnap resource from the fire drill service group fails.

Description:
In a disaster recovery fire drill configuration, the disks containing the snapshot of the replicating application data are offline. This issue typically occurs in the following environment: - The disks are shared between cluster nodes on the secondary site. - The cluster systems run Windows Server 2008 or Windows Server 2008 R2 operating system. As per Windows SAN policy for shared disks, the shared disks are initialized in an Offline Shared mode. Since the disks are offline, SFW fails to tag the disks. As a result, the SRDFSnap resource from the fire drill service group fails and the service group fails to come online, on the secondary site.

Resolution:
SFW behaviour is now updated such that the disks are brought online before they are tagged. This enables the SRDFSnap resource to come online.

Binary / Version:
vxconfig.dll / 6.0.33.362

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

[36] Hotfix name: Hotfix_6_0_00034_362_3378041

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

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

[37] Hotfix name: Hotfix_6_0_00035_362_3381786

Symptom:
On an SRDF setup with multiple nodes at Secondary, the local failover at Secondary fails due to disk reservation errors on the target node.

Description:
On an EMC SRDF setup with multiple nodes at Secondary, this issue occurs while trying to perform a local failover of a Fire Drill service group. There is a stale SCSI reservation thread created on the node when the SRDF disk group is imported for the first time. When the failover is attempted, this thread is not killed and it keeps defending disks when the target node challenges for reservation. Because of this, the disk group import on the target node fails and, therefore, the failover also fails.

Resolution:
This issue has been resolved so that the stale reservation threads are removed during an SRDF disk group import.

Binary / Version:
vxconfig.dll / 6.0.35.362

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

[38] Hotfix name: Hotfix_6_0_00036_362_3421570

Symptom:
VMDg resource fails to come online during first RO-to-RW import at the time of a failover, resulting in RHS process restart.

Description:
When the FastFailover property of a disk group is set to TRUE on the active node, the disk group is imported as Read Only on passive node and all volumes from the disk group arrives as part of import on the passive node. Sometimes, due to successive transactions within a short time, the PnP device interface property of volume is not updated properly. Therefore, during failover to the passive node, the VxVM provider queries for device name using device interface property and it fails. Because of this, the process to bring the VMDg resource online times out and, as a result, the RHS process restarts.

Resolution:
This issue has been resolved so that the VxVM provider queries device name using the volume name property in case PnP device interface property is NULL.

Binary / Version:
vxvm.dll / 6.0.00036.362

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

[39] Hotfix name: Hotfix_6_0_00037_362_3431608

Symptom:
In a disk group with even number of disks of which only half of the disks go missing, you cannot remove the missing disks if any volumes are present on the non-missing disks.

Description:
This issue occurs when there are even number of disks in a disk group with half of the disks missing. In this case, if there are any volumes on the non-missing disks, then removing the missing disks is not allowed. If you try to remove them, then it fails with the "Cannot remove last disk in dynamic disk group" error. This happens because the operation to remove disks incorrectly compares the number of disks to be removed with that of the non-missing disks. If the number is equal, then the operation tries to remove the complete disk group. However, the presence of volume resources prevents the removal of the disk group and the intended missing disks as well.

Resolution:
This issue has been resolved so that the operation to remove disks now compares the number of disks to be removed with the total number of disks in the disk group and not with the number of non-missing disks.

Binary / Version:
vxconfig.dll / 6.0.00037.362

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



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