|
---|
Release type: | Hot Fix |
Release date: | 2014-11-21 |
OS update support: | None |
Technote: | None |
Documentation: | None |
Popularity: | 503 viewed downloaded |
Download size: | 536.45 KB |
Checksum: | 1031895697 |
Cluster Server 6.0.2 On Windows x64
Storage Foundation HA 6.0.2 On Windows x64 |
None.
|
3557163
|
None.
|
* * * READ ME * * * * * * Veritas Cluster Server 6.0.2 * * * * * * Patch 6.0.2.010 * * * Patch Date: 2014-04-07 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 Cluster Server 6.0.2 Patch 6.0.2.010 OPERATING SYSTEMS SUPPORTED BY THE PATCH ---------------------------------------- Windows 2012 X64 BASE PRODUCT VERSIONS FOR THE PATCH ----------------------------------- * Veritas Cluster Server 6.0.2 * Veritas Storage Foundation HA 6.0.2 SUMMARY OF INCIDENTS FIXED BY THE PATCH --------------------------------------- Patch ID: Hotfix_6_0_20010_3557163 * 3557163 (3557192) The startup type of the VCS Authentication Service was set to Manual after installing a hotfix. DETAILS OF INCIDENTS FIXED BY THE PATCH --------------------------------------- This patch fixes the following Symantec incidents: Patch ID: Hotfix_6_0_20010_3557163 * 3557163 (Tracking ID: 3557192) SYMPTOM: The startup type of the VCS Authentication Service was set to Manual after installing a hotfix on VCS for Windows 6.0.2 or SFWHA 6.0.2. DESCRIPTION: When you perform a fresh installation of VCS for Windows or SFW HA, the startup type of the VCS Authentication Service is Manual. This startup type is changed to Automatic when you configure a secure cluster. However, when you apply a hotfix to such a configuration, the hotfix installer restores the startup type of the service to Manual. RESOLUTION: This hotfix addresses the issue by updating the installer, so that the startup type of the VCS Authentication Service does not change when you apply any hotfix. NOTE: This is a required hotfix. Do not uninstall this hotfix. FILE / VERSION: N/A INSTALLING THE PATCH -------------------- This package contains self-extracting files that are specific to the processor architecture and the operating system version on a system. Download the appropriate hotfix executable to a temporary location on your system. You can install this hotfix using the GUI or the CLI. Instructions for both these options are provided below. To install the hotfix on server systems using the GUI ------------------------------------ 1. Double-click the hotfix executable file to extract its contents to a default location on the cluster node. By default, the files are extracted to: "%programfiles(x86)%\Common Files\Veritas Shared\WxRTPrivates" The Hotfix Installer Wizard is automatically launched after the files are extracted. 2. Click "Next" on the Welcome screen. The 'Hotfix Installation Task' screen lists the tasks that are performed by the installer. 3. Click "Install Hotfix" to begin the hotfix installation. The status of each installation task is updated as it completes. 4. After the tasks are complete, click "Next" and then click "Finish" to complete the installation process. 5. If this is a clustered configuration (VCS or MSCS), please perform steps 1-4 on all additional nodes in the cluster. To install the hotfix on server systems using the CLI --------------------------------------------- 1. Navigate to the following location at the command prompt: "C:\temp" 2. Run one of the following commands to extract the hotfix files to the default location: <Hotfix_BuildVersion_IncidentNumber_OS_Platform>.exe /x or <Hotfix_BuildVersion_IncidentNumber_OS_Platform>.exe /extract 3. Navigate to the default location where the hotfix files are extracted. By default, the files are extracted to: "%programfiles(x86)%\Common Files\Veritas Shared\WxRTPrivates\<Hotfix_BuildVersion_IncidentNumber>" 4. Run the following command to install the hotfix: VxHF.exe /install:<Hotfix_BuildVersion_IncidentNumber> /silent Here, <Hotfix_BuildVersion_IncidentNumber> is the name of the hotfix file excluding the OS, platform, and .exe extension. 5. Follow the instructions displayed in the command prompt to complete the hotfix installation. 6. If this is a clustered configuration (VCS or MSCS), please perform steps 1-5 on all additional nodes in the cluster. REMOVING THE PATCH ------------------ Additional Notes ---------------- - To confirm the installation of the hotfix, view the Windows Installed Updates list (Start > Programs > Programs and Features > View Installed Updates), or run the following command: vxhf.exe /list By default, vxhf.exe is located at: "%programfiles(x86)%\Common Files\Veritas Shared\WxRTPrivates\<Hotfix_BuildVersion_IncidentNumber> " The output of this command lists the hotfixes installed on a system. - The hotfix installer (vxhf.exe) creates and stores logs at: "%allusersprofile%\Veritas\VxHF" - 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 SPECIAL INSTRUCTIONS -------------------- 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. OTHERS ------ NONE |
Why Register?
Get notifications about ASLs/APMs, HCLs, patches, and high availability agents
As a registered user, you can create notifications to receive updates about NetBackup Future Platform and Feature Plans, NetBackup hot fixes/EEBs in released versions, Array Support Libraries (ASLs)/Array Policy Modules (APMs), hardware compatibility lists (HCLs), patches and high availability agents. In addition, you can create system-specific notifications customized to your environment.
Compare configurations
The Compare Configurations feature lets you compare different system scans by the data collector. When you sign in, you can choose a target system, compare reports run at different times, and easily see how the system's configuration has changed.
Save configurations
After logging in, you can retrieve past reports, share reports with colleagues, review notifications you received, and retain custom settings. Anonymous users cannot access these features.
Bulk uploader
As a registered user,you can upload multiple reports, using the Bulk Uploader.