* * * READ ME * * * * * * Veritas Resiliency Platform Hot Fix 16 (3.4.0.4) * * * Hotfix Date: 2019-11-19 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 4 (3.4.0.4) APPLIANCES SUPPORTED BY THE HOTFIX ---------------------------------------- Resiliency Manager and 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.4: * STESC-3851 (VRP-26920) - Azure to On-Prem is failing at reverse replication step. * STESC-3687 (VRP-26072) - Custom script execution failed with error "Custom script execution failed" DETAILS OF ISSUES FIXED BY THE HOTFIX -------------------------------------------- This hotfix fixes the following JIRA issues: * STESC-3851 (Fix Tracking ID - VRP-26920) SYMPTOM: Migrate Operation from Azure to On-Prem is failing at reverse replication step in the converter. DESCRIPTION: The vm_id attribute was missing on the Gateway VM object. The azure discovery was intermittently reporting deletes of Gateway VM. This was causing the failure to migrate operation. RESOLUTION: Azure discovery is enhanced to handle the corner case of VM discovery to ensure that all VM in clouds get to discover. * STESC-3687 (Fix Tracking ID - VRP-26072) SYMPTOM: Custom script execution failed with error "Custom script execution failed". DESCRIPTION: Custom script execution failed with error "Custom script execution failed" because VRP tries to find an IMS server instead of VOM server to process the request. RESOLUTION: Send the appropriate imsType for the given host object selected for the script execution. INSTALLING THE HOTFIX -------------------- 1. Contact Veritas Technical Support for this Hot Fix and check if the hotfix is relevant to the 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.4 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 VRP RM and IMS appliances. 9. If the DR site is Azure. Refresh the Azure cloud Discovery from VRP UI using the "Refresh Cloud Discovery" option in Azure Datacenter. KNOWN ISSUES ----------- None NOTE ---- Make sure that hotfix 3.4.0.1 is installed before installing this hotfix.