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

 Basic information
Release type: Hot Fix
Release date: 2011-03-09
OS update support: None
Technote: TECH154448 - Storage Foundation for Windows High Availabitlity 5.1 SP2 EMC MirrorView agent fails to online
Documentation: None
Popularity: 629 viewed    47 downloaded
Download size: 1.25 MB
Checksum: 2300241970

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

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

 Fixes the following incidents:
2271435

 Patch ID:
None.

 Readme file  [Save As...]
Date: 2011-03-03
OS: Windows
OS Version: 2003, 2008
Packages: Hotfix_5_1_20012_2271435_x86.exe, Hotfix_5_1_20012_2271435_x64.exe, Hotfix_5_1_20012_2271435_ia64.exe
Etrack Incidents: 2271435

Errors/Problems Fixed
---------------------+
This hotfix addresses an issue where the VCS EMC MirrorView resource fails to come online in the cluster.

Overview
--------+
As part of its online function, the VCS MirrorView agent checks if naviseccli.exe is installed. If it does not find naviseccli, the agent checks the presence of navicli which in turn needs Java Runtime Environment (JRE).
If JRE is not installed on the node the agent fails to bring the resource online.

The agent log may contain the following messages:
V-16-20048-91 (nodename) MirrorView:<resourcename>-MirroView:clean:Can't open keys SOFTWARE\Wow6432Node\Veritas\VRTSjre

V-16-20048-92 (nodename) MirrorView:<resourcename>-MirroView:clean:Can't open keys SOFTWARE\Veritas\VRTSjre

VCS ERROR V-16-20048-94 (nodename) MirrorView:MIRRORVIEW:online:Java home is not found hence exiting

Resolution
----------+
This issue is fixed in the VCS MirrorView agent.
With the secure naviseccli, JRE is no longer required. The agent does not check for JRE on the cluster node.

Fixes Applied for Products:
---------------------------+
Storage Foundation and High Availability Solutions 5.1 SP2 for Windows


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

This hotfix includes the following updated file:
---------------------------------------
File name          | New Version number
---------------------------------------
MirrorViewAgent.pm |    --NA--
---------------------------------------


Before you begin
----------------+
In case of 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 web-site 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


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 all the files are extracted.

2. Click "Next" on the Welcome screen.
The Hotfix Installation Tasks panel lists the tasks that are performed by the installer.

3. Click "Install Hotfix" to install the hotfix.
The status of each task is updated as it gets completed.

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 (SFW-HA 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><HotfixName.exe> /x
or
C:\temp><HotfixName.exe> /extract

For example, to extract this hotfix on a 64-bit cluster node, the command is:
C:\temp>Hotfix_5_1_20012_2271435_x64.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"

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

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

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

For example, to install this hotfix on a cluster node, the command is:
vxhf.exe /install:Hotfix_5_1_20012_2271435 /silent

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 (SFW-HA 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://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 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 and HA 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.



Read and accept Terms of Service