This page lists publically-released patches for Veritas Enterprise Products.
For information on private patches, contact Veritas Technical Support.
For NetBackup Enterprise Server and NetBackup Server patches, see the NetBackup Downloads.
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.
The latest patch(es) : vcs-win_x64-CP14_VCSW_60
|Sign in if you want to rate this patch.|
|OS update support:||None|
|Popularity:||363 viewed 16 downloaded|
|Download size:||9.16 MB|
Applies to one or more of the following products:
Cluster Server 6.0 On Windows x64
Obsolete patches, incompatibilities, superseded patches, or other requirements:
Fixes the following incidents:
2650336, 2695917, 2722108, 2786159
Readme file [Save As...]
Date: 2012-08-27 OS: Windows OS Version: 2008, 2008 R2 Packages: ================================================ Architecture/OS Windows Server 2008 / 2008 R2 ================================================ x64 CP2_VCSW_60_W2k8_x64.exe ------------------------------------------------ Etrack Incidents: 2650336, 2695917, 2722108, 2786159 Fixes Applied for Products ==========================| Veritas Cluster Server (VCSW) 6.0 for Windows 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 ----------------:  Ensure that the logged-on user has privileges to install the CP on the systems.  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.  Symantec recommends that you close the Cluster Manager (Java Console) and the Veritas Enterprise Administrator (VEA) Console before installing this CP.  Before installing CP2, 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 CP1 or Agent Pack 2Q2012 on your system. 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:  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.  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.  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 CP2_VCSW_60_W2K8_x64.exe, specify it as CP2_VCSW_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:  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.  When the installer prompts whether you want to continue with the installation; type N to exit the installer.  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 VCSW 6.0 x64 CP for Windows Server 2008, the command is: vxhfbatchinstaller.exe /CP:CP2_VCSW_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.  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 hotfix Hotfix_6_0_00003_2650336_w2k8_x64.exe: vxhfbatchinstaller.exe /CP:CP2_VCSW_60 /Exclude:Hotfix_6_0_00003_2650336_w2k8_x64.exe /silent [+] Install CP in silent mode, restart automatically: vxhfbatchinstaller.exe /CP:CP2_VCSW_60 /silent /forcerestart Errors/Problems Fixed =====================| The fixes and enhancements that are included in this cumulative public patch (CP) are as follows:  Hotfix name: Hotfix_6_0_00003_2650336 Symptom: This hotfix addresses an issue related to the VCS PrintSpool agent where information about printers that were newly added in the virtual server context is lost in case of a system crash or unexpected failures that require a reboot. Description: The PrintSpool agent stores printer information to the configuration during its offline function. Therefore if printers are added in the virtual server context but the printspool resource or the printshare service group is not gracefully taken offline or failed over, the new printers information does not get stored to the disk. In such a case, if the node where the service group is online hangs, shuts down due to unexpected failures, or reboots abruptly, all the new printer information is lost. The printshare service group may also fail to come online again on the node. Resolution: This issue has been fixed in the PrintSpool agent. A configurable parameter now enables the agent to save the printer information periodically. A new attribute, 'SaveFrequency', is added to the PrintSpool agent. SaveFrequency specifies the number of monitor cycles after which the PrintSpool agent explicitly saves the newly added printer information to the cluster configuration. The value 0 indicates that the agent does not explicitly save the information to disk. It will continue to save the printer information during its offline function. The default value is 5. Binary / Version: PrintSpool.dll / 188.8.131.526 PrintSpool.xml / NA -------------------------------------------------------+  Hotfix name: HotFix_6_0_00006_2695917 Symptom: This hotfix addresses an issue where the VCS engine log is flooded with information messages in case of a network congestion. Description: MOMUtil.exe is a VCSAPI client. It uses VCS APIs to get information from VCS and present that to SCOM Server. MOMUtil.exe is invoked after every 5 minutes as part of VCS monitoring. This connects to the VCS Cluster running on the system and tries to fetch the information to display the current status of service groups. In case of a network congestion, the engine is unable to send the data to the client immediately. In this scenario, the following information message is logged after every 5 minutes: Could not send data to peer MOMUtil.exe at this point; received error 10035 (Unknown error), will resend again The engine successfully sends data to the client (MOMUtil.exe) after some time. By this time, the engine log is flooded with the information messages. Resolution: The engine has been modified to print the information messages as debug messages. So the messages will appear in the engine log only if DBG_IPM debug level is set. If you need to log the information messages in the engine log, run the following command to set the debug level DBG_IPM: halog -addtags DBG_IPM Binary / Version: had.exe / 184.108.40.2065 hacf.exe / 220.127.116.115 -------------------------------------------------------+  Hotfix name: HotFix_6_0_00007_2722108 Symptom: This hotfix addresses an issue related to the VCS FileShare agent wherein non-scoped file shares are not accessible using virtual server name or IP address if NetBIOS and WINS are disabled. Description: VCS FileShare and Lanman agents can support non-scoped file shares on Windows Server 2008 and 2008 R2 systems if the DisableServerNameScoping registry is created and set to 1. The VCS FileShare agent depends on NetBIOS and DNS to resolve the virtual name. If NetBIOS and WINS are disabled and the DNS is not updated, the agent is unable to resolve the virtual name. This may typically occur when the file share service groups are configured to use localized IP addresses. When the service group is switched or failed over, the virtual name to IP address mapping changes. In such a case if WINS database and the DNS are not updated, the agent is unable to resolve the virtual name. As a result the FileShare resources fault and the shares become inaccessible. The following message is seen in the agent log: VCS INFO V-16-10051-10530 FileShare:<servicegroupname>:online:Failed to access the network path (\\virtualname) RESOLUTION: The FileShare agent is enhanced to address this issue. The FileShare agent behavior can be controlled using the following registry keys: - HKLM\SOFTWARE\VERITAS\VCS\BundledAgents\Lanman\__Global__\DisableServerNameScoping Set the DisableServerNameScoping key to enable non-scoped file share support. - HKLM\SOFTWARE\VERITAS\VCS\BundledAgents\Lanman\__Global__\DisableStrictVirtualNameCheck Set the DisableStrictVirtualNameCheck key to have the FileShare agent make the file shares accessible irrespective of whether or not the virtual name is resolvable. You must manually create these registry keys after installing this hotfix. See the topic "Setting the DisableServerNameScoping and DisableStrictVirtualNameCheck registry keys" in this readme for more details. Notes: - The registry key DisableVirtualNameCheck will take effect only if DisableServerNameScoping key value is set to 1. - This FileShare agent behavior is applicable only for non-scoped file shares. - In the earlier procedure you created these registry keys at the global level. If there are multiple file share service groups that are to be used in the non-scoped mode, you may have to create these registry keys manually for each virtual server and then set the values. You must create these keys at the following location: HKLM\SOFTWARE\VERITAS\VCS\BundledAgents\Lanman\<VirtualName>\. Here <VirtualName> should be the virtual computer name assigned to the file share server. This is the VirtualName attribute of the lanman resource in the file share service group. - In case these registry parameters are configured at a global level and also configured for individual file share virtual servers, the registry settings for individual virtual servers takes precedence. - You must create this key only for lanman resources that are part of VCS file share service groups. Configuring this key for lanman resources that are part of other VCS service groups may result in an unexpected behavior. Binary / Version: Fileshare.dll / 18.104.22.1683 -------------------------------------------------------+  Hotfix name: HotFix_6_0_00011_2786159 Symptom: This hotfix addresses an issue related to the VCS Cluster Manager (Java Console) where a service group switch or failover operation to the secondary site fails due to a user privilege error. Description: This issue occurs in secure clusters set up in a disaster recovery (DR) environment. When you switch or failover a global service group to the remote site, the operation fails with the following error: Error when trying to failover GCO Service Group. V-16-1-50824 At least Group Operator privilege required on remote cluster. This error occurs even if the user logged on to the Java Console is a local administrator, which by default has the Cluster Administrator privilege in the local cluster. This issue occurs because the local administrator is not explicitly added to the cluster admin group at the remote site. During a switch or a failover, the Java Console is unable to determine whether the logged-on user at the local cluster has any privileges on the remote cluster and hence fails the operation. If you use the Java Console to grant the local administrator with operator or administrator privileges to the remote cluster, the Java Console only assigns guest privileges to that user. RESOLUTION: This issue is fixed in the Java Console. The Java Console now allows you to assign the local administrator at the local cluster with cluster admin or cluster operator privileges in the remote cluster. This change is applicable only on Windows. Binary Name / Version VCSGui.jar / NA -------------------------------------------------------+ Post-install steps ==================| The following section describes the steps that must be performed after installing the hotfixes included in this CP. Note that these steps are applicable only to the hotfixes listed in this section.  HotFix_6_0_00007_2722108 Perform the following steps only if you have installed HotFix_6_0_00007_2722108 as part of the CP installation. Setting the DisableServerNameScoping and DisableStrictVirtualNameCheck registry keys Perform the following steps to create and set the DisableServerNameScoping and DisableStrictVirtualNameCheck registry keys that are used by the FileShare agent to support non-scoped file shares and disable virtual name availability as a requirement for file shares to be available on the network. Caution: Incorrectly editing the registry may severely damage your system. Make a backup copy before making changes to the registry. To configure DisableServerNameScoping and DisableStrictVirtualNameCheck registry parameters: 1. To open the Registry Editor, click Start > Run, type regedit, and then click OK. 2. In the registry tree (on the left), navigate to HKLM\SOFTWARE\VERITAS\VCS\BundledAgents. 3. Click Edit > New > Key and create a key by the name Lanman, if it does not exist already. 4. Select Lanman and then click Edit > New > Key and create a key by the name __GLOBAL__. (underscore-underscore-GLOBAL-underscore-underscore) 5. Select __GLOBAL__ and add a DWORD type and specify Value name as DisableServerNameScoping and Value data as 1. The value 1 indicates that the FileShare agent supports non-scoped file shares on Windows Server 2008 and 2008 R2 systems. 6. Select __GLOBAL__ and add a DWORD type and specify Value name as DisableStrictVirtualNameCheck and Value data as 1. Setting this registry value to 1 allows the FileShare agent to make the file shares available even if the virtual name is not available on the network. You must create the DisableStrictVirtualNameCheck key parallel to the file share scoping key DisableServerNameScoping. 7. Save and exit the Registry Editor. -------------------------------------------------------+ 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, run the following command: vxhf.exe /list The output of this command lists 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/business/support/index?page=content&id=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/business/support/index?page=content&id=TECH73438 [+] For information on uninstalling a hotfix, please refer to the steps mentioned in the following technote: http://www.symantec.com/business/support/index?page=content&id=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.