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

 Basic information
Release type: Patch
Release date: 2014-12-01
OS update support: None
Technote: TECH226412 -Storage Foundation High Availability Solutions for Windows , Storage Foundation for Windows and Symantec Cluster Server for Windows 6.0.2 Cumulative Patch 1 (CP1)
Documentation: None
Popularity: 615 viewed    64 downloaded
Download size: 7.11 MB
Checksum: 3591068238

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

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

This patch is obsolete. It is superseded by: Release date
sf-win_x64-CP2_SFW_602 2015-08-31

 Fixes the following incidents:
3151173, 3207622, 3486063, 3500082, 3509025, 3524979, 3544908, 3620166, 3645063

 Patch ID:
None.

 Readme file  [Save As...]
                          * * * READ ME * * *
              * * * Veritas Storage Foundation 6.0.2 * * *
                      * * * Patch 6.0.2.100 * * *
                         Patch Date: 2014-11-11


This document provides the following information:

   * PATCH NAME
   * OPERATING SYSTEMS SUPPORTED BY THE PATCH
   * PACKAGES AFFECTED BY THE PATCH
   * BASE PRODUCT VERSIONS FOR THE PATCH
   * SUMMARY OF INCIDENTS FIXED BY THE PATCH
   * DETAILS OF INCIDENTS FIXED BY THE PATCH
   * INSTALLATION PRE-REQUISITES
   * INSTALLING THE PATCH
   * REMOVING THE PATCH


PATCH NAME
----------
Veritas Storage Foundation 6.0.2 Patch 6.0.2.100


OPERATING SYSTEMS SUPPORTED BY THE PATCH
----------------------------------------
Windows 2012 X64



BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------
   * Veritas Storage Foundation 6.0.2


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: SFW CP1
* 3207622 (3061941) Two issues related to storage migration of a volume with SmartMove enabled
* 3486063 (3486061) Snapshot or backup of a Hyper-V virtual machine using NetBackup fails if the corresponding VHD is on a dynamic volume belonging to an SFW cluster disk group
* 3500082 (3497449) Cluster disk group loses access to majority of its disks due to a SCSI error
* 3509025 (3509023) System crashes because the vxio.sys driver accesses freed memory when the Driver Verifier's Special Pool option is enabled
* 3524979 (3231593) Memory leak occurs for SFW VSS provider while taking a VSS snapshot
* 3544908 (3456746) VxSvc services crashes with heap corruption in VRAS.dll
* 3620166 (3146194) In some cases, mount points configured under Microsoft Failover Cluster are lost.
* 3645063 (3645059) The Add Secondary operation fails due to a TCP socket connection timeout.
* 3151173 (3111073) SFW and SFWHA 6.0.2 unable to identify Hitachi HUS VM LUNs as thin reclaimable.


DETAILS OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
This patch fixes the following Symantec incidents:

Patch ID: SFW CP1

* 3207622 (Tracking ID: 3061941)

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.

File Name / Version:
vxconfig.dll / 6.0.20002.76

* 3486063 (Tracking ID: 3486061)

SYMPTOM:
Snapshot or backup of a Hyper-V virtual machine using NetBackup fails if the corresponding VHD is on a dynamic volume belonging to an SFW cluster disk group

DESCRIPTION:
This issue occurs while taking VSS-aware snapshot or backup of a Hyper-V virtual machine using Symantec NetBackup and the virtual machine's VHD is on a dynamic volume belonging to an SFW cluster disk group. When SFW is installed, auto-mounting is disabled by default. But, for a successful backup of a Hyper-V virtual machine (guest), VSS on the host machine expects the arrived partitions to be automatically mounted. Because VSS does not find the partitions to be mounted, the backup operation fails.

RESOLUTION:
This issue has been resolved by bringing the non-VxVM partitions online while handling volume arrival in the SFW PnP provider.

File Name / Version:
pnp5.dll / 6.0.20003.76

* 3500082 (Tracking ID: 3497449)

SYMPTOM:
Cluster disk group loses access to majority of its disks due to a SCSI error

DESCRIPTION:
This issue occurs while processing a request to renew or query the SCSI reservation on a disk belonging to a cluster disk group. Because of the following error in the SCSI command, the operation fails:
Unit Attention - inquiry parameters changed (6/3F/03)
Because of this, the cluster disk group loses access to majority of its disks.

RESOLUTION:
This issue has been resolved by retrying the SCSI reservation renew or query request.

File Name / Version:
vxio.sys / 6.0.20004.76

* 3509025 (Tracking ID: 3509023)

SYMPTOM:
System crashes because the vxio.sys driver accesses freed memory when the Driver Verifier's Special Pool option is enabled

DESCRIPTION:
This issue occurs when the Driver Verifier tool's Special Pool option is enabled and Driver Verifier finds that the vxio.sys driver is accessing memory that was freed. Because of this, the system crashes.

RESOLUTION:
This issue has been resolved so that now the vxio.sys driver accesses memory before freeing and not after it is freed.

File Name / Version:
vxio.sys / 6.0.20005.76

* 3524979 (Tracking ID: 3231593)

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.

File Name / Version:
vxvssprovider.exe / 6.0.20006.76

* 3544908 (Tracking ID: 3456746)

SYMPTOM:
VxSvc service crashes with heap corruption in VRAS.dll

DESCRIPTION:
VRAS decided to discard a malformed packet it received, since the size of the packet was too large. It encountered an issue while freeing the IpmHandle pointer and crashed eventually.

RESOLUTION:
This hotfix resolves the crash which occurred during the handling of malformed packet.

File Name / Version:
vras.dll / 6.0.20007.76

* 3620166 (Tracking ID: 3146194)

SYMPTOM:
In some cases, mount points configured under Microsoft Failover Cluster are lost.

DESCRIPTION:
This issue may occur either while assigning mount points in a Microsoft Failover Cluster environment or during a failover. During this, Microsoft's "GetVolumePathNamesForVolumeName" function, which is used by Volume Manager Disk Group (VMDg) resource mount handling, fails to return mount point information even though the mount points exist on the system. This happens because of an issue with the "GetVolumePathNamesForVolumeName" function. As a result of this behavior, the VMDg resource removes the mount points from the cluster database during the volume arrival notification and then from the system during a failover.

RESOLUTION:
This issue has been resolved by modifying the present handling of the existing mount points and new mount points during volume arrival. 

After installing this hotfix, you need to perform the following workaround in case of a dynamic disk group join operation where the target disk group is under the VMDg resource: 
After performing the dynamic disk group join operation, reset the VMDg resource property.
For example, if the value of the DiskRunChkDsk attribute is set to 1, do the following:
1. Edit the attribute, and change the value to 0.
Note: If the value of the DiskRunChkDsk attribute is set to 0, then change it to 1.
2. Click Apply. 
3. Re-edit the DiskRunChkDsk attribute, and change the value back to 1, and click Apply.

File Name / Version:
vxres.dll / 6.0.20008.76

* 3645063 (Tracking ID: 3645059)

SYMPTOM:
The Add Secondary operation fails due to a TCP socket connection timeout.

DESCRIPTION:
While adding a secondary, the Volume Replicator Administrative Service (VRAS) engine on the Primary host tries to establish a TCP connection to the secondary host. Since the TCP socket connection timeout is set at 2 seconds, if the connection takes more than 2 seconds, the Add Secondary operation fails.

RESOLUTION:
This issue has been resolved by adding a new Volume Replicator tunable for VRAS TCP socket connection time out. After installing the hotfix, you must create the following registry key at HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\VxSvc\CurrentVersion\VolumeManager\constants:

Name: VRAS_CONNECT_TIMEOUT
Type: DWORD
Value: 2 seconds (default)

File Name / Version:
vras.dll / 6.0.20009.76

* 3151173 (Tracking ID: 3111073)

SYMPTOM:
SFW and SFWHA 6.0.2 unable to identify Hitachi HUS VM LUNs as thin reclaimable.

DESCRIPTION:
This issue is regarding SFW and SFW HA 6.0.2 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.

File Name / Version:
ddlprov.dll / 6.0.20001.76



INSTALLING THE PATCH
--------------------
What's new in this CP
=====================|

The following hotfixes have been added in this CP:
 - Hotfix_6_0_20001_76_3151173
 - Hotfix_6_0_20002_76_3207622
 - Hotfix_6_0_20003_76_3486063
 - Hotfix_6_0_20004_76_3500082
 - Hotfix_6_0_20005_76_3509025
 - Hotfix_6_0_20006_76_3524979
 - Hotfix_6_0_20007_76_3544908
 - Hotfix_6_0_20008_76_3620166
 - Hotfix_6_0_20009_76_3645063

For more information about these hotfixes, see the "FIXED_INCIDENTS" section in this Readme.


Install instructions
====================|

Download the appropriate cumulative public patch (CP) executable file to a temporary location on your system.

Each cumulative public patch includes the individual hotfixes that contain enhancements and fixes related to reported issues.
See the "FIXED_INCIDENTS" 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 re-distributable is installed on the systems.



To install the CP in the silent mode
-----------------------------------:

Perform the following steps:

[1] Double-click the CP executable file to start the CP installation. 

The installer performs the following tasks:
    - Extracts all the individual hotfix executable files
      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.

[2] 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 the CP using the command line
----------------------------------------:

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> [/PreInstallScript:<PreInstallScript.pl>] [/silent [/forcerestart]]

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

    - 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>"
      
[2] In the same command window, run the following command to begin the CP installation in the silent mode:
vxhfbatchinstaller.exe /CP:<CPName> /silent

For example, to install a SFW 6.0.2 CP for Windows Server 2012, the command is:
vxhfbatchinstaller.exe /CP:CP1_SFW_602 /silent

The installer performs the following tasks:

    - Extracts all the individual hotfix executable files
      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 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 2 earlier.


VxHFBatchInstaller usage example
---------------------------------:

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

vxhfbatchinstaller.exe /CP:CP1_SFW_602 /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
============|
There are no known issues identified in this CP.

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


REMOVING THE PATCH
------------------
NO


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

Additional notes
================|

[+] To confirm the list of cumulative 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 cumulative 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.

[+] To confirm the latest cumulative patch installed on a system, run the following command from the directory where the CP files are extracted:
vxhfbatchinstaller.exe /cplevel

The output of this command displays the latest CP that is installed, the CP status, and a list of all hotfixes that were a part of the CP but not 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 following technotes:
http://www.symantec.com/docs/TECH225604
http://www.symantec.com/docs/TECH73443


OTHERS
------
NONE



Read and accept Terms of Service