* * * READ ME * * *
                  * * * Veritas Risk Advisor 7.2 * * *
                           * * * Patch * * *
                         Patch Date: 2017-01-23


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 Risk Advisor 7.2 Patch


OPERATING SYSTEMS SUPPORTED BY THE PATCH
----------------------------------------
Windows



BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: 7.2_HF1
* 3909326 (3909324) *Veritas Risk Advisor 7.2 HF1


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

Patch ID: 7.2_HF1

* 3909326 (Tracking ID: 3909324)

SYMPTOM:
*Scan and data collection issues
*Risk detection issues
*Application and user interface issues

DESCRIPTION:
*Scan and data collection issues
*A lengthy search process invoked by HDS collection script did not end within
the expected time and was invoked again after a timeout, which leads to multiple
processes running on a server [G-1934]
*Frame ID representation when scanning HDS storage through HiCommand and HPUX is
incompatible, which leads HPUX scan to falsely discover un-scanned array [P-8334]
*An error occurs when connecting ASMDiskGroup to PV on Linux [P-7890]
*Wrong HDS ShadowImage RPE calculation on Solaris [P-8350]
*Case-sensitive MS-SQL databases are not supported [N-773]
*Solaris private zones are not discovered following Global zone scan [P-8356]
*RPO measurement for RecoverPoint 4.1 is incorrect [P-8308]
*RecoverPoint version 4 and higher is not supported with Symmetrix [N-682]

*Risk detection issues
*Gap 310 enhanced to detect additional specific cases of incorrect LV mirroring
for AIX hosts [G-1919]
*Gap 595 enhanced to avoid false tickets on UNIX when exclusion system property
is set with multiple values [G-1879]
*Exception in Gap 242 [G-1898]
*Gap 1300 enhanced to avoid false tickets in specific scenario [G-1903]
*Gap 446 enhanced to avoid false tickets in specific scenario [N-534]
*Gap 554 enhanced to avoid false tickets in specific scenario [G-1911]

*Application and user interface issues
*Very slow filtering of screens with large number of items [A-791]
*When adding specific Business Entities, "null" BE created [A-823] [A-850]
*Importing BEs using CSV file with special characters causes BE tab unresponsive
[A-825]
*"Last Successful Scan" is not updated after a successful scan [P-8163]
*Export to Excel does not work from Ticket Details tab when table contains a
hyperlink [N-521]
*Logo does not appear in Ticket Details report [N-508]
*Bad appearance of the Topology screen [N-535]
*Collector configuration file are not updated upon update of the server
configuration [P-6479]
*Changing host policy via the new "Host Associations" button doesn't work [A-747]
*Search field does not work on all columns in Management Console Scope [A-457]
*Host Comparison Tab  missing scroll bar [P-8330]
*Exception when retrieving top 5 tickets in specific scenario [A-744]
*Exception in data response handler [A-785]
*Rules for Automatic Association does not work [P-8220]

RESOLUTION:
*Veritas has modified the code to resolve these issues.



INSTALLING THE PATCH
--------------------
You can upgrade to VRA 7.2.0.1 only from version 7.2. If a system has an earlier version of the product installed, you must upgrade to version 7.2 before upgrading to this patch.

1.    Download the patch VRA_7.2.0.1.exe and copy it to the master VRA server.
2.    On the master VRA server, stop the VRA web server using the following steps:
    a.Open a command line window running with administrator privileges
    b.Enter the following commands: 
# net stop TomcatWatchDog
# net stop tomcat8
3.    Locate the VRA folder. By default, it is in the path: 
C:\Program Files\Apache Software Foundation\Tomcat 8.0\webapps\ 
4.    Make a copy of the VRA folder and store it in another location (do not store the copy under the tomcat tree). The patch updates files in this folder, so if you need to revert to the unpatched version of VRA, you will need the original folder.
5.    Go to the folder where you downloaded the patch. Find VRA _7.2.0.1.exe and double-click it.
6.    Follow the steps in the wizard to install the patch. 
7.    On the master VRA server, start the VRA web server using the following steps:
    a.Open a command line window running with administrator privileges
    b.Enter the following commands: 
# net start tomcat8
# net start TomcatWatchDog
8.    Login to VRA. 
9.    Verify that the build number is correct. On the VRA main screen, click "About". The build number should be 41444.


REMOVING THE PATCH
------------------
If after installing it you need to revert to the unpatched version of VRA 7.2, use the following procedure:

1.    Make sure you still have the backed up copy of the pre-patched, version 7.2 VRA folder
2.    On the master VRA server, stop the VRA web server using the following steps:
    a.Open a command line window running with administrator privileges
    b.Enter the following commands: 
# net stop TomcatWatchDog
# net stop tomcat8
3.    Locate the VRA folder. By default, it is in the path:
C:\Program Files\Apache Software Foundation\Tomcat 8.0\webapps\ 
4.    Delete the "VRA folder"
5.    Copy the backed up folder to its original location.  If you have changed the name of the copied folder, make sure to rename it to "VRA" (not including the quotes).
6.    On the master VRA server, start the VRA web server using the following steps:
    a.Open a command line window running with administrator privileges
    b.Enter the following commands: 
# net start tomcat8
# net start TomcatWatchDog


SPECIAL INSTRUCTIONS
--------------------
NONE


OTHERS
------
NONE