* * * README * * *
       * * * Veritas Resiliency Platform Hot Fix 7 (3.4.0.7) * * *                         
                     Hotfix Date: 2020-01-31


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 7 (3.4.0.7)

APPLIANCES SUPPORTED BY THE HOTFIX
----------------------------------------
Resiliency Manager

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

SUMMARY OF ISSUES FIXED BY THE HOTFIX
---------------------------------------
Hotfix 3.4.0.7:
* STESC-4088 (VRP-27863) - VRP outage created a memory leak in NBU master due to multiple login API requests.			

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

* STESC-4088 (Fix Tracking ID - VRP-27863)

SYMPTOM: Resiliency Manager(RM) outage causes multiple successful login API requests to the NBU master if the user does not confirm the outage before the NBU token expires in VRP (max 1 day).

DESCRIPTION: During outage of one of the RM the other RM database goes into the read only mode for all the domain object updates. As the NBU configuration object which stores the NBU token and the token expiry time was a domain object hence VRP failed to update the new received token from the NBU master to this database. Due to this for each Image notification from NBU, VRP request a login API to get a new token.

RESOLUTION: We have made the NBU configuration object to a local object(as it is a datacenter specific object), so that any update to it can be persisted into the database and VRP avoids the multiple login call to NBU master. 

INSTALLING THE HOTFIX
--------------------
  1. Contact Veritas Technical Support for this Hot Fix 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. Make sure there is no operation in progress while the hotfix is being applied.
  4. Perform the following steps to upload the hotfix
    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 hotfix
  5. 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.4.0.7
  6. Verify hotfix is applied successfully from clish
     hotfix> list-applied-hotfixes
  7. Close the SFTP session opened earlier
     utilities> sftp-session stop
  8. Repeat the steps 4 to 7 for all the VRP RM appliances.
    

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

NOTE
----
Make sure that hotfix 3.4.0.1 and 3.4.0.2 is installed before installing this hotfix.