Date: 2011-02-10
OS: Windows
OS Version: 2003, 2008
Packages: vxvm.dll ddlprov.dll vxconfig.dll
Etrack Incidents: 2218963, 2225878

Overview
---------
This hotfix adds thin provisioning support for HP XP arrays to SFW 5.1 SP2.
This hotfix also fixes a data corruption problem that can happen while
moving subdisks of a volume when the Smart Move mirror resync feature is enabled.

Errors/Problems Fixed
----------------------+ 
Hotfix_5_1_20005_87_2218963 adds thin provisioning support for HP XP arrays
to SFW 5.1 SP2.

When there are multiple subdisks on a disk and the subdisk that is being moved
is not aligned to 8 bytes, then there is a possibility of missing some disk
blocks while syncing with the new location. This may result in data corruption.

Hotfix_5_1_20005_87_2218963 fixes the starting Logical Cluster Numbers
used while syncing subdisk clusters so that no block is left out.


Known Issues with this Hotfix
-----------------------------
1. Changing the drive letter of a volume when a reclaim task for that volume is
in progress will abort the reclaim task. The reclaim task will appear to have
completed successfully, but not all of the unused storage will be reclaimed.
If this happens, perform another reclaim operation on the volume to release the
rest of the unused storage.

2. Reclaim operations on a striped volume that resides on thin provisioned disks
in HP XP arrays may not reclaim as much space as you expect. Reclaiming is done
in contiguous allocation units inside each stripe unit. The allocation unit size
for XP arrays is large compared to a volume's stripe unit size, so free
allocation units are often split across stripe units. In that case they
are not contiguous and can't be reclaimed.

3. If you use the SFW installer to change the enabled feature set after SFW is
already installed, reclaiming free space from a thin provisioned disk no
longer works. The installer incorrectly changes the Tag variable in the vxio
service registry key from 8 to 12. That allows LDM to intercept and fail the
reclaim requests SFW sends to the disks. This is a problem only on W2K8.
To work around this problem, manually change the value of
          HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\vxio\Tag
back to 8 and reboot after changing the enabled SFW features on W2K8.


Fixes Applied for Products
--------------------------+
Storage Foundation 5.1 SP2 for Windows


Install/Uninstall Instructions
------------------------------+
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.

==============================================================================
Operating System	Platform	File Name
==============================================================================
Windows Server 2003	IA64		Hotfix_5_1_20005_87_2218963_w2k3_ia64.exe	
			x64		Hotfix_5_1_20005_87_2218963_w2k3_x64.exe
			x86		Hotfix_5_1_20005_87_2218963_w2k3_x86.exe
------------------------------------------------------------------------------
Windows Server 2008	IA64		Hotfix_5_1_20005_87_2218963_w2k8_ia64.exe	
			x64		Hotfix_5_1_20005_87_2218963_w2k8_x64.exe
			x86		Hotfix_5_1_20005_87_2218963_w2k8_x86.exe
------------------------------------------------------------------------------

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.

Each self-extracting file includes the following updated file(s):

================================================================
Filename     | Version 	     |  Windows 2003   | Windows 2008  |
================================================================
vxvm.dll     | 5.1.20005.87 |  x86, x64, ia64 | x86, x64, ia64 |
----------------------------------------------------------------
ddlprov.dll  | 5.1.20005.87 |  x86, x64, ia64 | x86, x64, ia64 |
----------------------------------------------------------------
vxconfig.dll | 5.1.20005.87 |  x86, x64, ia64 | x86, x64, ia64 |
----------------------------------------------------------------


Before you begin
-----------------
[1] This is applicable only for Windows Server 2003.

This hotfix requires Microsoft Core XML Services (MSXML) 6.0 pre-installed in your setup.
Download and install MSXML 6.0 before installing the hotfix.
Refer to the following link for more information:
http://www.microsoft.com/downloads/details.aspx?FamilyId=993c0bcf-3bcf-4009-be21-27e85e1857b1&displaylang=en

Microsoft posted service pack and/or security updates for Core XML Services 6.0.
Please contact Microsoft or refer to Microsoft website to download and install latest updates to Core XML Services 6.0.
Refer to the following link for more information:
http://www.microsoft.com/downloads/details.aspx?FamilyId=70C92E77-9E5A-41B1-A9D2-64443913C976&displaylang=en

[2] The hotfix installation requires stopping the Storage Agent (vxvm) 
service which will cause the 'Volume Manager Disk Group' (VMDg) resources 
in a cluster environment (MSCS or VCS) to fault. If this hotfix is 
being applied to a server in cluster, make sure any cluster groups 
containing a VMDg resource are taken offline or moved to another node in 
the cluster before proceeding.


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.
On 32-bit systems, the files are extracted to:
"%commonprogramfiles%\Veritas Shared\WxRTPrivates"

On 64-bit systems, the files are extracted to:
"%commonprogramfiles(x86)%\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

For example, to extract this hotfix on a 32-bit Windows 2003 system, the command is:
C:\temp>Hotfix_5_1_20005_87_2218963_w2k3_x86.exe /x

2. From the command prompt, navigate to the default location where the hotfix files are extracted.
On 32-bit systems, the files are extracted to:
"%commonprogramfiles%\Veritas Shared\WxRTPrivates\<Hotfix_BuildVersion_IncidentNumber_OS_Platform>"

On 64-bit systems, the files are extracted to: 
"%commonprogramfiles(x86)%Veritas Shared\WxRTPrivates\<Hotfix_BuildVersion_IncidentNumber_OS_Platform>"

3. At the command prompt, run the following command to install the hotfix:
VxHF.exe /install:<Hotfix_BuildVersion_IncidentNumber_OS_Platform> /silent

Here, <Hotfix_BuildVersion_IncidentNumber_OS_Platform> is the name of the hotfix file excluding the OS,
platform, and .exe extension.

For example, to install this hotfix on a 32-bit Windows 2003 system, the command is:
VxHF.exe /install:Hotfix_5_1_20005_87_2218963 /silent

Hotfix Executable Name is Hotfix_5_1_20005_87_2218963_w2k3_x86.exe.
When installing the hotfix, the <Hotfix_BuildVersion_IncidentNumber_OS_Platform> name is Hotfix_5_1_20005_87_2218963.
(note how the "_w2k3_x86.exe" is excluded).

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.


Additional Notes
----------------------+
- To confirm the installation of the hotfix, run the following command:
vxhf.exe /list

The output of this command lists the hotfixes installed on a system.

- For details about a particular hotfix, run the following command:
vxhf.exe /display:<HotfixName>

Here, <HotfixName> is the name of the hotfix file without the platform and the .exe extension.

- 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://seer.entsupport.symantec.com/docs/329713.htm

- To view a list of hotfixes already installed on a system, please refer to the steps mentioned
in the following technote: 
http://seer.entsupport.symantec.com/docs/329704.htm

- For information on uninstalling a hotfix, please refer to the steps mentioned in the following technote: 
http://seer.entsupport.symantec.com/docs/329709.htm


DISCLAIMER
------------------+
This fix has not been fully tested. 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.