* * * READ ME * * * * * * Veritas Resiliency Platform 3.3 * * * * * * Maintenance Release 2 * * * Patch Date: 2019-02-01 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 Resiliency Platform 3.3 Maintenance Release 2 OPERATING SYSTEMS SUPPORTED BY THE PATCH ---------------------------------------- CentOS 6.9 x86-64 BASE PRODUCT VERSIONS FOR THE PATCH ----------------------------------- * Veritas Resiliency Platform 3.3 SUMMARY OF INCIDENTS FIXED BY THE PATCH --------------------------------------- Patch ID: 3.3.2.0 * 3969695 (3969694) List of issues fixed in 3.3.2 DETAILS OF INCIDENTS FIXED BY THE PATCH --------------------------------------- This patch fixes the following incidents: Patch ID: 3.3.2.0 * 3969695 (Tracking ID: 3969694) SYMPTOM: Issues fixed in VRP 3.3.2 DESCRIPTION: JIRA IDs ------------- 12946 DNS customization changes are not updated while editing resiliency group. 19305 Data availability missing for some resiliency groups after a DR operation. 19885 Scheduled scan does not clear the risk when the vCenter server is removed and re-added into the IMS. 19859 IMS disconnected risk does not get resolved immediately after adding new IMS. 19949 Windows host may appear to be disconnected after migrate back to on-premises data center. 7407 Some DHCP enabled NICs are not present on Cloud after migrate. 8232 Sometimes network comes up on only one NIC on virtual machines having multiple NICs. 8326 Resiliency group details in the console displays stale vCloud virtual machine entries after migrating back a resiliency group to the premises site. 13024 Recovery data center details are not displayed after upgrade if the disk name is greater than 128 characters. 19818 Sometimes replication gets stuck after upgrade or restart of Replication Gateway. 5181 Virtual machine protection using Resiliency Platform Data Mover has a few policy related limitations. 5183 Data Mover virtual machine in no op mode risk cannot be resolved. 10821 Newly added Resiliency Manager cannot remove the existing offline Resiliency Manager. RESOLUTION: Not applicable INSTALLING THE PATCH -------------------- DOWNLOADING THE UPDATE This Update is applicable for VRP 3.3 1. Download repository bundle using 'Setup Repository Bundle Download' link on update page * Veritas_Resiliency_Platform_Setup_Repository_3.3.2.0.tar.gz This zip contains the setup_conf_repo.pl and other files to be used for setting up the update on repository server 2. Download the update/patch bundle file vrp-centos69_x86_64-Update-3.3.2.0.tar.gz on your repository server 3. Unzip the update/patch bundle file vrp-centos69_x86_64-Update-3.3.2.0.tar.gz on your repository server 4. Multiple files will be extracted within patches folder * Veritas_Resiliency_Platform_RM_Upgrade_Bundle_3.3.2.0.tar.gz The file to be configured using setup_conf_repo.pl on repository server for RM fixes * Veritas_Resiliency_Platform_DataMover_Upgrade_Bundle_3.3.2.0.tar.gz The file to be configured using setup_conf_repo.pl on repository server for DataMover fixes * Veritas_Resiliency_Platform_IMS_Upgrade_Bundle_3.3.2.0.tar.gz The file to be configured using setup_conf_repo.pl on repository server for IMS fixes * VRTSsfmitrp-3.3.2.0.sfa This addon is to be uploaded on VIOM management server UI in case of InfoScale support from VRP INSTALLATION INSTRUCTIONS -------------------------------- Refer to Veritas Resiliency Platform's Deployment Guide for detailed instructions on updating the resiliency platform and its components. Note: If automatic DRS is not enabled, you need to put the ESX hosts into maintenance mode to go ahead with the bundle update. REMOVING THE PATCH ------------------ Not Supported SPECIAL INSTRUCTIONS -------------------- NONE OTHERS ------ NONE