* * * READ ME * * *
                 * * * Veritas Risk Advisor 7.2.1 * * *
                         * * * Patch 001 * * *
                         Patch Date: 2017-04-26


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.1 Patch 001


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



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


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: 7.2.1_HF1
* 3916869 (3916863) *Veritas Risk Advisor 7.2.1 HF1


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

Patch ID: 7.2.1_HF1

* 3916869 (Tracking ID: 3916863)

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

DESCRIPTION:
*Scan and data collection issues
 *Invalid SRM URL - SRM Fails to Scan [P-8396]
 *OEM Exception - ASMMapping [P-8414]
 *NetApp DFM scanning issues [N-1062]
 *MSCS dependencies issue [N-1073]
 *OEM - Exadata hosts creation issue [N-1033]
 *NetFS of NFS4 don't return from Linux [N-974]
 *Infinidat devices on AIX not recognized [N-961]
 *Incorrect Infinidat replication information [N-929]
 *Linux host reported as successfully scanned when in fact it was not [N-797]

*Risk detection issues
 *Collection for Gap 350 enhanced to support additional cases [G-2058]
 *Gap 310 enhanced to avoid false tickets in specific scenario [G-1956]
 *Gap 1097 enhanced to avoid false tickets in specific scenario [G-1960]
 *Gap 529 enhanced to avoid false tickets in specific scenario [G-1955]
 *Gap 554 enhanced to avoid false tickets in specific scenario [G-1933]

*Application and user interface issues
 *Response RequestFinalizer post plugin performance issue [A-951]
 *CMDB Import - FQDN dropped under HOST_IP column [A-919]
 *Ticket Details Report Fails - "0xb" Invalid XML character [A-893]

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



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

1. Download the patch VRA_7.2.1.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.1.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 41929.


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

1. Make sure you still have the backed up copy of the pre-patched, version 7.2.1 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