* * * READ ME * * *
                 * * * Veritas Resiliency Platform Hot Fix 17 (3.4.0.3) * * *                         
                         Hotfix Date: 2019-10-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 3.4.0.3

APPLIANCES SUPPORTED BY THE HOTFIX
----------------------------------------
Resiliency Manager, Infrastructure Management Server

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


SUMMARY OF ISSUES FIXED BY THE HOTFIX
---------------------------------------
Hotfix 3.4.0.3:
STESC-3424 : During VMware snapshot related operation on protected VM's the VM gets hang

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

Symptoms: In VMware to VMware environment when using VRP 3.4 release:
1) VM may hang for long duration or may panic in some cases.
2) VM Snapshot may fail or consolidation of snapshot may fail.
3) VM may experience a hang like situation for long duration.
4) On vm reboot, following error could occur in vmware.log file of the VM
"E110: vxtap(partners/samples/iofilter/build_prod_vrp_master/dbdrl.c:sr_dbdrl_read_drl_table:1096) ERR Failed to read DRL table at offset = 8192, size = 16384 from sidecar with  error (1)"
"E110: vxtap(partners/samples/iofilter/build_prod_vrp_master/filter.c:sr_li_open_for_business:2767) ERR handle F9ECA5D5F0: failed to read DRL table from active sidecar with error (1)"

Description: In VMware to VMware environment it is observed that VRP configuration may get corrupted, due to this replication becomes inactive and above mentioned symptoms are observed. 
This behavior will not cause any corruption w.r.t to VM data.

Resolution: Veritas VIB is now enhanced to serialize the sidecar access to avoid corruption

INSTALLING THE HOTFIX
--------------------
Note: This patch is applicable for RM and IMS.

Contact Veritas Technical Support for this hotfix and check if the hotfix is relevant to issue seen in your environment.

# Use the following steps to apply the patch on all RM:

1. Login to the source and target RM using the admin user and go to the root shell from the support menu.

2. Copy STESC-3424.tar.gz under /tmp

3. Extract STESC-3424.tar.gz under /tmp using command: tar -xvf STESC-3424.tar.gz

4. Go inside STESC-3424 folder and apply the patch on both RM using the command: ./rm.sh

5. Update HF registry by command: /opt/VRTSsfmh/bin/perl update_hf_reg.pl 

# Use the following steps to apply the patch on all IMS:

1. Login to the source and target IMS using admin user and go to the root shell from the support menu.

2. Copy STESC-3424.tar.gz under /tmp

3. Extract STESC-3424.tar.gz under /tmp using command: tar -xvf STESC-3424.tar.gz

4. Go inside STESC-3424 folder and apply the patch on both IMS using the command: ./ims.sh

5. Update HF registry by command: /opt/VRTSsfmh/bin/perl update_hf_reg.pl 

# Now upgrade VIB on source and target site ESXi cluster:

1. Login to the RM using UI.

2. Click on ‘Settings’ --> ‘Infrastructure’ --> ‘Data Mover’ --> ‘Upgrade Veritas Replication VIB’ --> Select ‘ESXi cluster’ to upgrade VIB.

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

NOTE
----
 a)Rollback of hotfix is not supported.