Translation Notice
Please note that this content includes text that has been machine-translated from English. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information.
Veritas Resiliency Platform Hotfix 1
Abstract
Description
* * * READ ME * * *
* * * Veritas Resiliency Platform Hotfix 1 (3.5.0.1) * * *
Hotfix Date: 2020-08-31
This document provides the following information:
* HOTFIX NAME
* APPLIANCES SUPPORTED BY THE HOTFIX
* BASE PRODUCT VERSION FOR THE HOTFIX
* SUMMARY OF THE HOTFIX
* DETAILS OF THE HOTFIX
* INSTALLING THE HOTFIX
* KNOWN ISSUES
* NOTE
HOTFIX NAME
----------
Veritas Resiliency Platform Hotfix 1 (3.5.0.1)
APPLIANCES SUPPORTED BY THE HOTFIX
----------------------------------------
Resiliency Manager
BASE PRODUCT VERSION FOR THE HOTFIX
-----------------------------------
Veritas Resiliency Platform 3.5
SUMMARY OF THE HOTFIX
----------------------------------------------------
Hotfix 3.5.0.1 includes a new license scheme 'Front-End Terabyte'(FETB), a NetBackup license which is now applicable to Veritas Resiliency Platform.
DETAILS OF THE HOTFIX
--------------------------------------------
Description: This 'Front-End Terabyte'(FETB) is a NetBackup license which would be applicable to Veritas Resiliency Platform once the customer installs hotfix 3.5.0.1.
Resolution: With the addition of this new FETB license the following would be the applicability of different Veritas Resiliency Platform licenses-
Veritas Resiliency Platform FETB (Per-FETB): This license is consumed when the resiliency group is created using virtual machines or applications.
Veritas Resiliency Platform Compute (Per-Core): This license is consumed when resiliency group is created using applications that are deployed on the physical hosts and no Per-FETB license is available.
Veritas Resiliency Platform Compute (Per-VM): This license is consumed when resiliency group is created using virtual machines or applications that are deployed on the virtual machines and no Per-FETB license is available.
Veritas Resiliency Platform Compute InfoScale per core (x86): This license is consumed when resiliency group is created using InfoScale applications that are deployed on the Windows or Linux physical hosts.
Veritas Resiliency Platform Compute InfoScale per core (unix): This license is consumed when resiliency group is created using InfoScale applications that are deployed on the Unix or AIX or HP-UX physical hosts.
NOTE:
Calculation of FETB consumption:
For protecting virtual machine: The size of the disks attached to virtual machine would be considered for consumption against FETB license irrespective of the disk type like thin or thick.
For protecting application: The application size discovered by Veritas Resiliency Platform would be used to calculate the consumption of FETB license. For example: For Oracle Data Guard one can check the DB size (total size of the data files) using sqlplus query.
SELECT sum(bytes) from v$datafile;
INSTALLING THE HOTFIX
--------------------
1. Contact Veritas Technical Support for this hotfix. Check whether the hotfix is relevant to the issue seen in your environment.
2. Download the hotfix and copy it to any server having access to Veritas Resiliency Platform appliances.
3. Extract the downloaded tar ball. Hotfix files for the applicable appliance will be extracted into patches directory.
4. Make sure no operation is in progress while the hotfix is being applied.
5. Perform the following steps to upload the hotfix on the applicable appliance:
a) Open the SFTP session from Klish command:
utilities> sftp-session start put patch
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 appliance
into the 'upload' directory.
6. Perform the following steps to install the hotfix:
a) Verify that the hotfix is uploaded using Klish command:
hotfix> list-available-hotfixes
b) Apply the hotfix using Klish command:
hotfix> apply-hotfix 3.5.0.1
7. Verify that the hotfix is applied successfully using Klish command:
hotfix> list-applied-hotfixes
Output: List of hotfixes installed on the system are:
3.5.0.1
8. Close the SFTP session opened earlier.
utilities> sftp-session stop
9. Repeat the steps 5 to 8 on applicable appliances. The hotfix functionality may fail even if any one of the appliance is skipped.
KNOWN ISSUES
-------------
None
NOTE
-----
a) Rollback of this hotfix is not supported.
Applies to the following product releases
Update files
|
File name | Description | Version | Platform | Size |
---|