Release Notes

Last Published:
Product(s): Resiliency Platform & CloudMobility (3.4)
  1. Release Overview
    1. New features and changes in Veritas Resiliency Platform 3.4
      1.  
        Support for NetBackup Instant Access to recover a resiliency group
      2.  
        Support for NetBackup CloudCatalyst for recovery of virtual machines to AWS
      3.  
        Support for Orange Recovery Engine
      4.  
        Support for recovery from physical to virtual/cloud environment
      5.  
        Enhancements for preparing hosts for replication
    2.  
      Using the product documentation
    3.  
      More information
  2. System requirements
    1.  
      System resource requirements for Resiliency Platform
    2.  
      Network and firewall requirements
  3. Known issues
    1. General known issues
      1.  
        A network group becomes faulted if any of its network member is unavailable (VRP-25636)
      2.  
        HTML format is not supported for large sized reports (VRP-25649)
      3.  
        RG creation for Virtual machines that replicated by NetApp SnapMirror, fails with error (23189)
      4.  
        Rehearsal virtual machine Identifier is not same as workload virtual machine Identifier on an upgraded setup (22369)
      5.  
        Replication becomes inactive after performing the Replace Gateway operation when the gateway has workload's snapshot disks attached (25722)
      6.  
        Certain links in the help point to an older help version
    2. Known issues: Recovery from physical environment to virtual machines
      1.  
        The sequence of NICs is not maintained during recovery from a physical environment to a virtual machine (VRP-25439)
    3.  
      Known issues: Recovery to Amazon Web services (AWS)
    4. Known issues: Recovery to Azure
      1.  
        Re-sync operation failed with error (25625)
    5. Known issues: Recovery to vCloud
      1.  
        Migrate or takeover operation may fail due to unavailability of independent disks on the vCloud Director (14639)
      2.  
        After migrating back, the storage profile selection for the existing virtual machine may be incorrect (16901)
      3.  
        After migrating back, the IP and MAC addresses assigned to a NIC are displayed incorrect on using Customize Network intent (16458)
    6. Known issues: Resiliency Platform Data Mover
      1.  
        Configuring resiliency group for remote recovery fails during Add disk task (16245)
      2.  
        If DRL disk gets deleted from a protected asset, then edit RG and delete RG gets stuck stop replication on iotap. (23266)
      3.  
        State of Replication Gateway is incorrectly reflected in Veritas Resiliency Platform (22888)
    7. Known issues: Resiliency Platform Data Mover used for recovery to on-premises data center
      1.  
        vtstap storage policy may be displayed as Incompatible (18287)
      2.  
        Configuring resiliency group for remote recovery fails during Add disk task (16245)
      3.  
        Veritas Replication VIB installation, Upgrade, Resolve & Verify, Create RG, or any DR operation may fail on ESX with errors (22585)
    8. Known issues: Recovery from physical environment to virtual machines
      1.  
        The sequence of NICs is not maintained during recovery from a physical environment to a virtual machine (VRP-25439)
    9. Known issues: Recovery using third-party replication
      1.  
        Migrate and resync operations fail when there are stale objects on the source data center (13775)
      2.  
        Hyper-V Replica does not replicate any new assets (19084)
    10. Known issues: NetBackup integration
      1.  
        A virtual machine backed up by multiple NBU master servers gets mapped with only one master server in the console (7608)
      2.  
        Resiliency group task name shows TAKEOVER during evacuation (16466)
      3.  
        Issue with support for restoring of UEFI-enabled virtual machines from Netbackup
      4.  
        Restoring of virtual machines through Veritas Resiliency Platform may fail under certain conditions
    11. Known issues: Upgrade
      1.  
        Replace gateway configuration may not get updated in virtual machine's configuration after Veritas Resiliency Platform is upgraded from 3.3.2 to 3.4 (VRP-25508)
      2.  
        "Asset disk configuration changed" risk with description "New disk is attached to virtual machine" may come for RBT disk after upgrade to 3.3.2.0 (23118)
      3.  
        Kernel RPM package cannot be recovered if partially installed on VSA during upgrade (22625)
      4.  
        For VC 6.5, VIB upgrade fails because of ESX maintenance mode (22493)
      5.  
        New UI alignment is not updated after upgrade in same tab or session (22240)
      6.  
        False risk of GW is not upgraded popup is shown while performing DR operation after upgrade (22768)
  4. Limitations
    1.  
      General limitations
    2.  
      Limitations: Recovery to vCloud Director
    3.  
      Limitations: Recovery of physical machines to VMware virtual machines
    4.  
      Limitations: Recovery of VMware virtual machines to on-premises data center using Resiliency Platform Data Mover
    5.  
      Limitations: Recovery of VMware virtual machines to on-premises data center using third party replication
    6.  
      Limitations: Windows hosts for Resiliency Platform Data Mover replication
    7.  
      Limitations: Localization
    8.  
      Limitations: Support for OpenStack configuration

Kernel RPM package cannot be recovered if partially installed on VSA during upgrade (22625)

Consider a scenario in which the appliance is rebooted or shut down at Started upgrade from current_version to update_version step and new kernel RPM package is partially installed on the appliance. In this scenario, bootstrap loader fails to load kernel in memory and the appliance fails to boot and directly grub command line is shown to user. All other partially installed RPM packages except kernel package on the appliance can be recovered during upgrade at system start time. If kernel RPM package gets corrupted due to system reboot or shutdown during upgrade, we cannot recover it as boot process of the system fails. Appliance goes in unrecoverable state due to corrupt kernel in it.