* * * READ ME * * *
              * * * Veritas Storage Foundation 6.0.1 * * *
                          * * * Hot Fix * * *
                         Patch Date: 2012-04-19


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.1 Hot Fix


OPERATING SYSTEMS SUPPORTED BY THE PATCH
----------------------------------------
Windows 2008 X64
Windows Server 2008 R2 X64



BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------
   * Veritas Storage Foundation High Availability 6.0.1


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: Hotfix_6_0_10004_308_3124269
* 3124269 (3155620) Tagging of snapshot disks fails during the fire drill operation, because of which disk import also fails


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

Patch ID: Hotfix_6_0_10004_308_3124269

* 3124269 (Tracking ID: 3155620)

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

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

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


File Name / Version:
vxconfig.dll / 6.0.10004.308



INSTALLING THE PATCH
--------------------
This package contains self-extracting files that are specific to the processor architecture and operating system version. Choose the appropriate file for your computer's configuration. Download the appropriate hotfix executable to a temporary location on your system. 

You can install this hotfix using the GUI or from the command line. Instructions for both options are provided below.


To install the hotfix using the GUI
-----------------------------------
1. Double click the hotfix executable file to extract the contents to a default location on the cluster node.
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 prompted to restart the server, do so.

6. If this is a clustered configuration (VCS or MSCS), please perform steps 1-5 on all additional nodes in the cluster.


To install the hotfix using the command line
--------------------------------------------
1. At the command prompt, run one of the following commands to extract the hotfix files to the default location:
C:\temp>  <Hotfix_BuildVersion_IncidentNumber_OS_Platform> .exe/x
or
C:\temp>  <Hotfix_BuildVersion_IncidentNumber_OS_Platform> .exe/extract

2. From the command prompt, navigate to the default location where the hotfix files are extracted.
The files are extracted to: 
"%programfiles(x86)%\Common Files\Veritas Shared\WxRTPrivates\<Hotfix_BuildVersion_IncidentNumber>  "

3. At the command prompt, 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.

4. Follow the instructions displayed in the command prompt to complete the hotfix installation.

5. If prompted to restart the server, do so at this time.

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, run the following command:
vxhf.exe /list
On the system, 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%\Application Data\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