* * * READ ME * * *
                 * * * Veritas Risk Advisor 7.2.2 * * *
                         * * * Patch 001 * * *
                         Patch Date: 2017-10-31


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


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



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


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: 7.2.2_HF1
* 3932933 (3932932) *Veritas Risk Advisor 7.2.2 HF1


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

Patch ID: 7.2.2_HF1

* 3932933 (Tracking ID: 3932932)

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

DESCRIPTION:
*Scan and data collection issues
 *Add VM to Port Group connection + Distributed Port Group to VMNIC connection [P-8429]
 *Timed-out requests are written the to log instead of just writing their IR [P-8439]
 *Unspecified command error in Linux VM scanning [P-8427]
 *Incorrect PVs generated when ZFS status is degraded [P-8413]
 *NetApp SnapMirror replication state not collected - Impact RPO calculation [P-8459]
 *False positive and negative for SnapMirror replication lag [G-2094]
 *Missing data for RecoverPoint replication - SLA, false tickets opened [N-1235]
 *Bug - Incorrect RecoverPoint lag time information reported in SLA tickets [N-1070]
 *Paths are considered as standalone PVs and false tickets are opened (single path) [P-8461]
 *BNA Scan doesn't manage to correlate the switches it found [N-1198]
 *Cluster resource dependency collection issue leads to false 01032MSCSRD tickets [P-8456]
 *ESXi PV does not connect to VPLEX virtual volume [P-8480]
 *Scan Issue: PV2SV on Windows [N -1351]
 *Greyed out duplications of HDS storage arrays, false tickets opened [N-1253]
 *Add support for Infinidat 3.0 [N-1325]
 *SRM scanning issues - unsupported symbols in raw data [P-8435]
 *Agent SYMCLI scan issue [P-8454]
 *Corrupted response file load causing Java heap on Master server [P-8452]
 *General error while scanning probe vCenter [P-8438]
 *Unable to scan vCenter with newer VI API with error: Requested array size exceeds VM limit [P-8277] 

*Risk detection issues
 *Gap 00335SANSSPOF logics enhancement to avoid false tickets [G-2103]
 *Exception in gap 00447SuboptimalNFSMaxQueueDepth fixed [G-1868]
 *Do not compare Linux Kernel parameter net.core.netdev_rss_key [G-2028]
 *Exception in gap 00700SLA fixed [G-2117]
 *Exception in gap 00512VCSReplicationResource fixed [G-2118]
 *Tickets of Gap00242HostAccessingRemoteDevices should not be closed [G-2119]
 *Exception in gap 00447SuboptimalNFSMaxQueueDepth fixed [G-2120]
 *Exception in gap 00280DatabaseBP fixed [G-2127]
 *Infinite loop in Gap00887OracleClusterware fixed [N-1393]

*Application and user interface issues
 *EXP files aren't directed to the DailyDump/WeeklyDump folders [A-815]
 *Generic ticketing connector enhancements [N-815]
 *Failure to manage host scan when there are multiple Solaris zones with the same name [A-963]
 *SAPI_VM_TO_REPLICATION_GROUP has incorrect data [A-1023]
 *Out of memory failure [N-1381]
 *Exception during "SLA Definition" [N-1230] 
 *Failure to un-suppress numerous gaps [A-1029]
 *External Ticket queue reached limit - add ability to control queue size [A-1060] 
 *Add ability to prevent overriding BEs while import from CMDB [A-1059]
 *Support package sent by AG through email is corrupt (partial) [A-1014]
 *SymptomsRunner couldn't finish successfully [A-1011]
 *Disksets failed to run [N-1175]
 *"Load all tickets on Tickets tab select" doesn't load tickets [A-1071]
 *Exception during upgrading object model [A-1082]
 *Add Labels Misaligned  Firefox [N-1197]
 *Tab Alignment  Firefox [N-1196]
 *Small field on ticket notes after upgrade to 7.2.1.1 [A-1006]
 *Typing characters in "Labels" not issuing an error message [A-996]

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



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

1. Download the patch VRA_7.2.2.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.2.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 42703.


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

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