* * * READ ME * * *
              * * * Veritas Resiliency Platform 2.2 * * *
                         * * * Patch 300 * * *
                         Patch Date: 2017-07-17


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 2.2 Patch 300


OPERATING SYSTEMS SUPPORTED BY THE PATCH
----------------------------------------
CentOS 6.7 x86-64



BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------
   * Veritas Resiliency Platform 2.2


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: 2.2.0.300
* 3924064 (3924065) List of issues fixed in Update 2.2U3.
* 3921242 (3921243) List of issues fixed in Update 2.2U2.


DETAILS OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
This patch fixes the following incidents:

Patch ID: 2.2.0.300

* 3924064 (Tracking ID: 3924065)

SYMPTOM:
Update U3 fixes issues in VRP 2.2

DESCRIPTION:
JIRA IDs
-------------
10162 DR operation fails if the password of the target vCenter server contains
special character such as '$'
9350 Configuration files and Veritas Replication Set information on the ESX
server does not get cleaned up after deletion of resiliency group
containing VMware VAIO virtual machines
9917 Resiliency Platform Applications add-on gets pushed to Veritas InfoScale
Operations Manager as part of upgrade
9999 Lookup entries for IMS in the Resiliency Manager memory local cache
do not get refreshed after deletion of IMS
9377 VCS cluster node gets powered off after migration of Resiliency group
containing InfoScale applications if a virtual machine gets discovered
from vCenter server as well as by Veritas InfoScale Operations Manager
9933 Add host operation fails if you uninstall the ITRP add-on from the host
and then try to add the host again
9267 Assets Lookup service has multiple mappings if a virtual machine gets
discovered from vCenter server as well as by Veritas InfoScale
Operations Manager
9918 Secure SMTP configuration not validated before passing the user
information for email alert configuration
9608  Stale entries for NIC objects in the database do not get deleted
9607  Stale entries for LUNs in the database do not get deleted
10047 Hosts that have underscore in names not blocked during bootstrap
9675 If Veritas Resiliency Platform is removed after being installed and
configured for VMware VAIO recovery, subsequent fresh installation in
the same environment may fail as vCenter server retains the metadata
of the previous data mover bundle installation.
9998 Custom Script Execution fails if a virtual machine gets discovered from
vCenter server as well as by Veritas InfoScale Operations Manager, or
if some of the hosts belonging to an ESX server are added as host while
others get discovered by the vCenter server
10046 Resiliency Manager upgrade from console is not supported and needs
to be blocked
9251 IP customization fails after the timeout of one minute
10063 User needs to be notified that running loggather command with full
option stops the IMS services
8762 No option to automatically cleanup loggather files
9854 Risks raised before upgrade do not get cleared after upgrade

RESOLUTION:
Not applicable

* 3921242 (Tracking ID: 3921243)

SYMPTOM:
Update U2 fixes issues in VRP 2.2

DESCRIPTION:
JIRA IDs
-------------
7709 Refresh operation for EMC SRDF enclosure does not work
7704 Remove DNS operation fails if DNS customization done by editing
resiliency group
7717 VLAN pairing for distributed port group gets deleted after upgrade
8735 Custom script execution as part of resiliency plan fails intermittently
8730 Create resiliency group operation fails with the error: No gateway pair
found for the assets
8661 Migration fails due to HP 3PAR discovery issue
8599 Virtual machines do not get powered on due to missing VLAN
configuration after failback
8240 Resiliency group creation using VAIO fails due to failure in fetching
virtual machine profile from VCenter
8095 Network mapping for VLAN gets deleted after upgrade
8094 Web UI performance slow after upgrade
8093 After upgrade to 2.1, VMware migration fails with the error: Invalid
technology workflow
8074 Create resilience group operation with Resiliency Platform data mover
fails with not enough space available error, even tough enough space
is available on the data store
7982 Orchestration workflow fails due to error in fetching information for
VMware
7861 Resiliency group using VAIO replication gets created without name if
ESX runs out of memory
7756 VCS applications in a resiliency group cannot be brought online or taken
offline
6309 VRP and VIOM disconnected state displayed in the risk section
6297 Migration of resiliency group fails with the error: Invalid technology
6133 Distributed vSwitch not available after re-adding vCenter
6092 Virtual machines on the replicated storage are not included in the
disaster recovery configuration
9500 Access profile service fails to restart in first attempt
9471 keytab does not get passed correctly to IMS
9348 Entries in /etc/krb5.conf file keep on increasing
9385 DNS operation shows success even when kinit fails and actual
operation fails
9384 HyperV ITRP_NR discovery triggers unnecessary full HyperV discovery
if HyperV virtual machine name is longer
9126 IP customization fails with the error: unable to create VRP directory
9388 Filter IO throttling option needs to be provided
9258 After Upgrade to Resiliency Platform 2.2, Hyper-V virtual machines are
not discovered
9053 VRP Subnet network pair gets deleted from list after DR Rehearsal
network is changed
9269 VIOM side APIs getting directed to IMS instead of VIOM since VIOM
server was treated as addressable object
9351 Recovery Operations on resiliency group using VAIO replication fails if
resiliency group is edited on recovery data center
9278 IOTAP virtual machine configured for recovery to AWS gets crashed
9345 Retry count for Datastore unmount operation should be configurable
9556 In case of VMware VAIO, if there are multiple clusters and datastores,
the traget cluster selection page becomes unresponsive
9268 Upgrade should work even if there are some stale resiliency group
entries exist
6764 Resiliency plan becomes unresponsive if you edit the plan while it is
getting executed
8899 InfoScale operations should not become unresponsive even if entire
cluster is down
8636 Create resiliency group operation fails for HyperV virtual machines if
the LUN size is greater than 1 TB
9018 Show appropriate error if user generating keytab does not have enough
privileges to update DNS
8752 After restarting the gateway appliance, the gateway state remains faulted
and the gateway pair in disconnected state

RESOLUTION:
Not applicable



INSTALLING THE PATCH
--------------------
DOWNLOADING THE UPDATE

This Update is applicable for VRP 2.2

1. Download repository bundle using 'Setup Repository Bundle Download' link on update page

* Veritas_Resiliency_Platform_Setup_Repository_2.2.0.300.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 file vrp-centos68_x86_64-Update-2.2.0.300.tar.gz on your repository server
3. Unzip the file vrp-centos68_x86_64-Update-2.2.0.300.tar.gz on your repository server
4. Multiple files will be extracted within patches folder

* Veritas_Resiliency_Platform_RM_Upgrade_Bundle_2.2.0.300.tar.gz
      The file to be configured using setup_conf_repo.pl on repository server for RM fixes

* Veritas_Resiliency_Platform_DataMover_Upgrade_Bundle_2.2.0.300.tar.gz
      The file to be configured using setup_conf_repo.pl on repository server for DataMover fixes

* Veritas_Resiliency_Platform_IMS_Upgrade_Bundle_2.2.0.300.tar.gz
      The file to be configured using setup_conf_repo.pl on repository server for IMS fixes

* VRTSsfmitrp-2.2.0.300.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