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.
sfw-win-Hotfix_5_1_00035_398_1742444a
Sign in if you want to rate this patch.

 Basic information
Release type: Hot Fix
Release date: 2009-08-12
OS update support: None
Technote: TECH73611 - Filesystem corruption is seen on volumes after performing a "Disk Evacuate" or "Hot Relocation" operation in Storage Foundation for Windows (SFW) 5.1
Documentation: None
Popularity: 882 viewed    133 downloaded
Download size: 4.74 MB
Checksum: 2824660192

 Applies to one or more of the following products:
Storage Foundation 5.1 On Windows 32-bit
Storage Foundation 5.1 On Windows IA64
Storage Foundation 5.1 On Windows x64

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

 Fixes the following incidents:
1742444

 Patch ID:
None.

 Readme file  [Save As...]
Etrack Incidents: 1742444
CONTENTS
-----------+
I.   OVERVIEW
II.  RESOLUTION
III. INSTALLING THE PRIVATE
     - Prerequisites
     - GUI Install
     - Command Line Install
     - Additional Notes
IV.  DISCLAIMER
I. OVERVIEW
------------+
Following a Disk Evacuate or a subdisk move operation, NTFS corruption is seen. This is only seen when the SmartMove option is enabled, and this feature is enabled by default. In addition, this issue only occurs when multiple subdisks are moved.
II. Resolution
--------------+
An issue was found where blocks of data could be mistakenly omitted during the evacuate process when the SFW SmartMove feature is enabled, which it is by default. Engineering has released a private fix to resolve this issue.
A workaround for this issue is to disable the SmartMove feature. SmartMove helps reduce the resynchronization time for mirror operations and subdisk moves. It accomplishes this by using NTFS file system metadata to determine all populated regions of a disk, and only synchronizing these regions. This avoids SFW having to replicate empty (blank) space on a volume that is not being used. Disabling this feature will increase the amount of time operations such has FlashSnap Snapshots, Mirrors, Subdisk Moves, and Evacuate take to complete as they will need to copy all data, even blank space.
To disable this feature, perform the following steps:
1. Open the Veritas Enterprise Administrator (VEA)
2. Select the "Control Panel" option from the far leftpane.
3. Expand the host name from the middle pane and select the "StorageAgent" option.
4. Select the "System Settings" from the far right pane.
5. In the "System Settings" window, select the SmartMove tab.
6. Uncheck the "Enable SmartMove" option and choose "OK" to save.
For a permanent solution that allows the use of the SmartMove feature, please follow the instructions below to install the downloaded private fix.
III. INSTALLING THE PRIVATE
----------------------------+
Note: This process requires stopping the Storage Agent (vxvm) service which will cause issues with the "Volume Manager Disk Group" (VMDg) resoures in an MSCS cluster. If this private fix is being applied to a server in an MSCS cluster, make sure any Groups containing a VMDg resource are taken offline or moved to another node in the cluster before proceeding.
The private fix archive contains a hotfix installer for the following Windows Server 2008 architectures. 
   Operating System		    Platform    File Name
   -----------------------------------------------------------------------------------------
   Microsoft Windows Server 2003    IA64	Private_5_1_00035_398_1742444_w2k3_ia64.exe	
   Microsoft Windows Server 2003    x64	        Private_5_1_00035_398_1742444_w2k3_x64.exe
   Microsoft Windows Server 2003    x86	        Private_5_1_00035_398_1742444_w2k3_x86.exe
   Microsoft Windows Server 2008    IA64	Private_5_1_00035_398_1742444_w2k8_ia64.exe
   Microsoft Windows Server 2008    x64	        Private_5_1_00035_398_1742444_w2k8_x64.exe
   Microsoft Windows Server 2008    x86	        Private_5_1_00035_398_1742444_w2k8_x86.exe
Please extract the contents to a temporary location and proceed with the instructions below:
Prerequisites
-------------
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 web-site to download and install latest updates to Core XML Services 6.0.
To install the hotfix using the GUI
------------------------------------
a. 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 all the files are extracted.
b. Click "Next" on the Welcome screen. The Hotfix Installation Tasks panel lists the tasks that are performed by the installer.
c. Click "Install Private" to install the hotfix. The status of each task is updated as it gets completed.
d. After the tasks are complete, click "Next" and then click "Finish" to complete the installation process.
e. Repeat these steps for all the cluster nodes.
To install the hotfix using the command line
---------------------------------------------
a. At the command prompt run any of the following commands to extract the hotfix files to the default location:
C:\temp><PrivateName_Platform.exe> /x
or
C:\temp><PrivateName_Platform.exe> /extract
For example, to extract this hotfix on a 32-bit cluster node, the command is:
C:\temp>Private_5_1_00025_1652239.exe /x
b. 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"
On 64-bit systems, the files are extracted to: "%commonprogramfiles(x86)%\Veritas Shared\WxRTPrivates"
c. At the command prompt, run the following command to install the hotfix: VxHF.exe /install:<PrivateName> /silent
Here, <PrivateName> is the name of the private file without the platform and the .exe extension.
For example, to install this hotfix on a 32-bit cluster node, the command is:
VxHF.exe /install:Private_5_1_00025_1652239.exe /silent
d. Follow the instructions displayed in the command prompt to complete the hotfix installation.
e. If this server is part of an MSCS/Windows Failover Cluster or a Veritas Cluster Server (VCS), please perform the installation steps on all nodes in the cluster.
Additional Notes
----------------
- VxHF.exe logs are located at the following location: "%allusersprofile%\Application Data\Veritas\VxHF"
- For information on a list of hotfixes installed on the node, use the following command: VxHF.exe /List
IV. 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.
Additional note: 
---------------
Please note that this patch name has been corrected. Its old name was "sfw-win-Private_5_1_00035_398_1742444a" and we removed the term "Private" as this was misleading.



Read and accept Terms of Service