vrp-centos69_x86_64-Patch-3.3.2.6

 Basic information
Release type: Patch
Release date: 2019-05-29
OS update support: None
Technote: None
Documentation: None
Popularity: 203 viewed    downloaded
Download size: 37.11 KB
Checksum: 1695953162

 Applies to one or more of the following products:
Resiliency Platform 3.3.2 On CentOS 6.9 x86-64

 Obsolete patches, incompatibilities, superseded patches, or other requirements:
None.

 Fixes the following incidents:
3979293

 Patch ID:
None.

Readme file
                          * * * READ ME * * *
                 * * * Veritas Resiliency Platform Hot Fix 6 (3.3.2.6) * * *                         
                         Hotfix Date: 2019-05-21


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.3.2.6

APPLIANCES SUPPORTED BY THE HOTFIX
----------------------------------------
Data Mover Appliances

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


SUMMARY OF ISSUES FIXED BY THE HOTFIX
---------------------------------------
Hotfix 3.3.2.6:
* STESC-2928 (VRP-24091) - Resync operation fails as Abort Replication hangs

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

* STESC-2928 (VRP-24091)

SYMPTOM: Resync operation fails as Abort Replication hangs

DESCRIPTION: Scheduler does not handle the error code for US advance

RESOLUTION: Handled the missing error code for US advance

INSTALLING THE HOTFIX
--------------------
  1. Contact Veritas Technical Support for this hotfix 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. Extract the downloaded tar ball. Hotfix files for all applicable components will be extracted into the patches directory.
  4. Make sure there is no operation in progress while the hotfix is being applied.
  5. Perform the following steps to upload the hotfix on each of the applicable components.
    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 corresponding hotfix file for this component.
  6. 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.3.2.6
  7. Verify hotfix is applied successfully from clish
     hotfix> list-applied-hotfixes
  8. Close the SFTP session opened earlier
     utilities> sftp-session stop
  9. Repeat the steps 5 to 8 on all applicable components. The hotfix functionality can fail if even one component is skipped. 

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

NOTE
----

Make sure that hotfix 3.3.2.1 is installed before installing this hotfix.