* * * READ ME * * *
                 * * * Veritas Resiliency Platform Hot Fix 3 (3.3.2.3) * * *                         
                         Hotfix Date: 2019-06-3


This document provides the following information:

   * HOTFIX NAME
   * APPLIANCES SUPPORTED BY THE HOTFIX
   * BASE PRODUCT VERSION FOR THE HOTFIX
   * SUMMARY OF ISSUES FIXED BY THE HOTFIX
   * DETAILS OF ISSUES FIXED BY THE HOTFIX
   * INSTALLING THE HOTFIX
   * KNOWN ISSUES
   * NOTE


HOTFIX NAME
----------
Veritas Resiliency Platform Hotfix 3.3.2.3

APPLIANCES SUPPORTED BY THE HOTFIX
----------------------------------------
Infrastructure Management Server

BASE PRODUCT VERSION FOR THE HOTFIX
-----------------------------------
Veritas Resiliency Platform 3.3.2


SUMMARY OF ISSUES FIXED BY THE HOTFIX
---------------------------------------
Hotfix 3.3.2.3:
* STESC-3066 (VRP-24360) - Large number of RGs suddenly At Risk; Storage Policy Detached
* STESC-3035 (VRP-24356) - DR rehearsal failed in HyperV using shadow image
* STESC-2796 (VRP-23902) - On Korean Windows10 does now show VBS and RGs on first load only
* STESC-2829 (VRP-23802) - Clean up rehearsal fails and the RG gets stuck in cleanup rehearsal state
* VRP-23566 - VMware Storage policy discovery fails on Spanish locale of VC
* VRP-23871 (VRP-23879) - SR service queue pile up in scale environment
* STESC-2762 (VRP-23826) - Data mover page takes a long time to load
* VRP-23510 - Refresh Cloud API fails with xprtld exception and do not retry.

DETAILS OF ISSUES FIXED BY THE HOTFIX
--------------------------------------------
This hotfix fixes the following JIRA issues:

* STESC-3066 (Fix Tracking ID - VRP-24360)

SYMPTOM: Large number of RGs suddenly At Risk; Storage Policy Detached

DESCRIPTION: Failure of discovery of ESX from VC leads to delete for the policy being sent which eventually leads to Storage policy detached risk being raised

RESOLUTION: Do not report delete of storage policy if the ESX cannot be contacted due to any reason as part of VMWare discovery. 
This does not lead to cascade effect of policy delete triggering Risk to be raised.

* STESC-3035 (Fix Tracking ID - VRP-24356)

SYMPTOM: DR rehearsal failed in HyperV using shadow image

DESCRIPTION: DR Rehearsal fails on a HyperV setup where the cluster configuration is not symetric across both datacenters.
VRP assumes that the cluster configuration is exactly same.

RESOLUTION: Enhanced the logic so that we take into account any asymettric cluster configuration across the datacenters.

* STESC-2796 (Fix Tracking ID - VRP-23902)

SYMPTOM: On Korean Windows10 does now show VBS and RGs on first load only

DESCRIPTION: VBS and RG listing page do not get loaded on first time. Reloading the page lists out the entries.
VRP does not support Korean locale but the 3rd party UI library which are used supports Korean.
These try to load the localized keys for Korean and fail during first load of page.

RESOLUTION: Handled the korean language in the 3rd party library used to default to English. 
This does not lead to failed call to fetch Korean localized keys and pages are loaded in first load properly.

* STESC-2829 (Fix Tracking ID - VRP-23802)

SYMPTOM: Clean up rehearsal fails and the RG gets stuck in cleanup rehearsal state.

DESCRIPTION: IF MQ call gets timeout then never used to raise event to clean the operation in progress flag on RG.

RESOLUTION: MQ timeout issue is now addressed and the cleanup rehearsal flag is set properly now.

* VRP-23566

SYMPTOM: VMware Storage policy discovery fails on Spanish locale of VC

DESCRIPTION: Version check for doing policy discovery was incorrect. We were checking for text build along with build version number.

RESOLUTION: While doing the vCenter version check we are now ignoring the text build and just checking for build version number.

* VRP-23871 (Fix Tracking ID - VRP-23879)

SYMPTOM: SR service queue pile up in scale environment

DESCRIPTION: Replication lag shown in UI keeps on increasing due to SR queue pile up

RESOLUTION: Introduced caching in processing of replication lag information so that multiple updates for same CG gets clubbed as single update periodically.
This makes sure that there is no piling of SR queue in a large environment

* STESC-2762 (Fix Tracking ID - VRP-23826)

SYMPTOM: Data mover page takes a long time to load

DESCRIPTION: Data mover listing page takes a long time to load when the number of data movers are high.

RESOLUTION: Improved the queries of data mover listing page. The page now loads much faster than earlier.

* VRP-23510

SYMPTOM: Refresh Cloud API fails with xprtld exception and do not retry.

DESCRIPTION: When the Cloud API failed there operation used to fail as there was no retry.

RESOLUTION: Retrying the Cloud API in case of intermittent failure in network.

INSTALLING THE HOTFIX
--------------------
  1. Contact Veritas Technical Support for this hotfix and check if the hotfix is relevant to issue seen in your environment.
  2. Download the hotfix and copy it to any server having access to VRP appliances.
  3. Extract the downloaded tar ball. Hotfix files for all applicable components will be extracted into the patches directory.
  4. Make sure there is no operation in progress while the hotfix is being applied.
  5. Perform the following steps to upload the hotfix on each of the applicable components.
    a) Open the SFTP session from clish
	   utilities> sftp-session start put hotfix
	b) Provide the password for this temporary SFTP session
	c) Open SFTP session using the above created user information and upload the corresponding hotfix file for this component.
  6. Perform the following steps to install the hotfix
    a) Verify that the hotfix is uploaded from clish
	   hotfix> list-available-hotfixes
	b) Apply the hotfix from clish
	   hotfix> apply-hotfix 3.3.2.3
  7. Verify hotfix is applied successfully from clish
     hotfix> list-applied-hotfixes
  8. Close the SFTP session opened earlier
     utilities> sftp-session stop
  9. Repeat the steps 5 to 8 on all applicable components. The hotfix functionality can fail if even one component is skipped. 
    
    

KNOWN ISSUES
-----------
None

NOTE
----
 a)Make sure that hotfix 3.3.2.1 is installed before installing this hotfix. 
 b)Rollback of hotfix is not supported.