Release Notes

Last Published:
Product(s): Resiliency Platform (10.4)
  1. Release Overview
    1.  
      New features and changes in Veritas Resiliency Platform 10.4
    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.  
        Certain links in the help point to an older help version
      2.  
        On replacing the target side Replication Gateway, the replication may become inactive after migrate operation for the workloads having snapshots (25722).
      3.  
        Abruptly powering off the Resiliency Manager resulted into services going in stopped state (27740)
      4.  
        Replication lag exceeding RPO risk getting raise/clear frequently (30234)
      5.  
        DR operations fail if ESXi server is moved from one vCenter server to another (16287)
      6.  
        On performing the recover operation when the risk Existing disk is detached from virtual machine is present on the resiliency group, resync operation may fail.(33645)
      7.  
        Migrate operation failed in Post register(veritassr) task (34078).
      8.  
        Notification bell icon is not getting updated automatically when risks are raised. (36054)
      9.  
        Creating resiliency group for the first time on Windows 2012 and Windows2012 R2 failed.(35858, 35600)
      10.  
        Resiliency Platform Datamover operations may fail on the ESXi with error. (36121)
      11.  
        While executing reports in pdf format, the reports are stuck. (35885)
      12.  
        Resync operation after recovering the virtual machine may fail with error. (36136)
      13.  
        Maintenance mode issue for Suse 12.5 & 15.2. (35454)
      14.  
        Risk History report for large amount of data might show errors in the report and count of new or/and closed risks data might be blank. (36080)
      15.  
        Enabling secure boot mode after creating the resiliency group is not supported. (36654)
      16.  
        Resiliency group with in-guest replication and addition of 100GB disk hits memory cap issue. (9985)
      17.  
        Some DR operations for resiliency group like rehearsal, migrate or recovery operations failed for RHEL 8.x and 9.0. (36921)
      18.  
        Activity of adding Cloud Recovery Server (CRS) to Resiliency Manager is not displayed under Activity tab.
      19.  
        Veritas Resiliency Platform integration with Recovery vault version 10.2 and above is not supported. (36923)
      20.  
        Prepare host failed for RHEL version 9.1. (36077)
      21.  
        Performed RabbitMQ major version upgrade for version 10.4 (PVM-3772)
      22.  
        Session times out in the between the bootstrap process. (36986)
    2. Known issues: Recovery to Amazon Web services (AWS)
      1.  
        Resiliency group remains offline even after deep start at target data center. (31786)
      2.  
        Resync is failed at Start Replication on Windows Host. (34091)
      3.  
        After migrating Hyper-V virtual machines to AWS cloud data center with ENA based flavour, resync operation failed. (36177)
      4.  
        After migration, on AWS based virtualization target region, you may see inactive replication state for RHEL9.0 workloads. (9984)
      5.  
        Create RG fails on AWS for SLES 12.5 with older version of kernel. (36675)
      6.  
        Windows 22 IOTAP exited into critical condition after migrate back from AWS to premise data center.
    3. Known issues: Recovery from AWS region to AWS region
      1.  
        Reverse replication is not working after migrate back if the instance type is selected as ENA. (146721)
      2.  
        After migration, inactive replication state is seen on AWS based virtualization.(8575)
    4. Known issues: Recovery to Azure
      1.  
        Routing tables are not getting updated properly, hence the host is not getting added to IMS.(33994 )
      2.  
        On upgrading Resiliency Platform to version 10.0 and above, refresh cloud operations fails.
      3.  
        The agent on Linux host that was hosted on Azure and VMware failed after upgrading to Veritas Resiliency Platform 10.3.
    5. Known issues: Recovery to Azure using NetBackup MSDP-C
      1.  
        Restore operation might fail if NetBackup Cloud Recovery Server has version less that 10.1.
      2.  
        Risks related to config drift disk and NetBackup Cloud Recovery Server readiness bundle do not resolve automatically.
    6. Known issues: Google Cloud Platform
      1.  
        Creating resiliency group for the first time on Windows 2012 and Windows2012 R2 failed.(35858, 35600)
    7. Known issues: Resiliency Platform Data Mover
      1.  
        If Replication Block Tracking (RBT) disk gets deleted from a protected asset, then edit resiliency group and delete resiliency group gets stuck stop replication on IOTAP. (23266)
      2.  
        Hyper-V virtualization: State of Replication Gateway is incorrectly reflected in Veritas Resiliency Platform (22888)
      3.  
        Refresh VCenter discovery if inaccessible or template virtual machines are present (27564)
      4.  
        Cloned virtual machine configured for DR operation, leads to data corruption on the target data center. (30176)
      5.  
        False risk may appear for all the configured disks of the resiliency group after Resiliency Manager is upgraded from version 3.4 to 3.6. (31827)
      6.  
        Duplicate risks are removed after successful Resiliency Manager and IMS upgrade.
      7.  
        VIB installation fails on vLCM enabled cluster on vSphere 7.0.(31266)
      8.  
        Replication Gateway pair may appear in Faulty state even if the individual Replication Gateway state is Healthy. (31898)
      9.  
        No validation message occurs in edit wizard if the Replication Gateway disk capacity exceeds.(118855)
    8. Known issues: Resiliency Platform Data Mover used for recovery to on-premises data center
      1.  
        Veritas Replication VIB installation, Upgrade, Resolve & Verify, Create RG, or any DR operation may fail on ESX with errors (22585)
      2.  
        Replace Gateway fails at suspend replication task with error cg-admin error. (29597)
      3.  
        After correcting virtual mode RDM disk paths, VMware NRT causes false updates (30201)
      4.  
        Recover operation failed while configuration drift on the resiliency group. (33735)
      5.  
        Unable to apply IP customization for resiliency group due to subnet for IP not found error. (36184)
    9. 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)
    10. 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)
      3.  
        Hyper-V with 3rd party replication: After creating or editing the resiliency group, immediate DR operations may fail. (28704)
      4.  
        Error occurred for while migrating resiliency group configured with IBM replication array.(36971)
      5.  
        Error occurred for resiliency group configured with IBM replication array. (36978)
    11. Known issues: NetBackup integration
      1.  
        A virtual machine backed up by multiple NetBackup primary servers gets mapped with only one primary server in the console (7608)
      2.  
        Resiliency group task name shows TAKEOVER during evacuation (16466)
      3.  
        Avoid creating or editing the resiliency group for the virtual machines on which backup jobs are running in NetBackup (30210)
      4.  
        Avoid executing migrate, recover using replicated data, resync, rehearsal using replicated data or cleanup rehearsal operation for the virtual machines on which backup jobs are running in NetBackup. (36061)
      5.  
        In case of multiple active data centers for a resiliency group, only single data center name is displayed instead of showing names of all the active data centers in the UI. (36183).
      6.  
        Resiliency Plan scheduled execution failed at Clear Outage for VBS task.(36182)
    12. Known issues: Upgrade
      1.  
        For VC 6.5, VIB upgrade fails because of ESX maintenance mode (22493)
      2.  
        Notifications of some events that are generated during upgrade process are not shown in the UI. (36204)
      3.  
        During upgrade process, upgrade of hosts of SLES 12.4 may hang for more than 3 hours. (36150)
    13. Known issues: InfoScale clusters
      1.  
        Due to the application dependency changes and the discovered top level application service group are no longer at the top level on the InfoScale cluster, the application goes in deleted or unavailable state. (29475)
      2.  
        Dashboard view card displays incorrect information for OS count on Hosts by Platform and OS card. (33766)
      3.  
        Sometimes there are no risk/notifications if the cluster name configuration is changed. (7156)
      4.  
        Adding InfoScale 8.x cluster in Resiliency Platform failed with error.
    14. Known issues : Continuous Data Protection (CDP)
      1.  
        Recover operation of CDP enabled resiliency groups may fail at takeover replication step with error - Could not find recovery point with UUID. (29618)
    15. Known issue: VMware vSphere 7.0 support
      1.  
        On creating resiliency group using VMware VAIO on vSphere 7.0, make sure there are no snapshots of protected virtual machines. (30216)
      2.  
        Installation of VIB on vLCM enabled cluster on VMware vSphere 7.0 fails (31266)
      3.  
        Storage vMotion fails for Resiliency Platform appliances.(33880)
    16. Known issue: Managing security certificates and SSH host keys
      1.  
        Add storage enclosure may fail with error "Unable to fetch SSH host key for the host HOSTNAME". (31790)
    17. Known issues: Recovery of resiliency groups configured using multiple recovery points
      1.  
        Delete VM directory task in recover operation using Copy (NetBackup) may fail.
  4. Fixed issues
    1.  
      Fixed issues list
  5. Limitations
    1.  
      General limitations
    2.  
      Limitations: Recovery to AWS
    3.  
      Limitations: Recovery from AWS region to AWS region
    4.  
      Limitations: Recovery to Azure
    5.  
      Limitations: Recovery to Azure using NetBackup MSDP-C
    6. Limitations: Recovery of resiliency groups configured using multiple recovery points
      1.  
        Limitations: Recovery of resiliency groups configured using multiple recovery points with Instant Access
      2.  
        Limitations: Resync/repair replication for resiliency groups
      3.  
        Limitations: For selective disk restore operation on local and remote data centers.
      4.  
        Limitation: For NetBackup CDP protected virtual machines
    7.  
      Limitations: Recovery of physical machines to VMware virtual machines
    8.  
      Limitations: Recovery of VMware virtual machines to on-premises data center using Resiliency Platform Data Mover
    9.  
      Limitations: Recovery of VMware virtual machines to on-premises data center using third party replication
    10.  
      Limitations: Windows hosts for Resiliency Platform Data Mover replication
    11.  
      Limitations: InfoScale
    12.  
      Limitations: Localization
    13.  
      Limitation: NetBackup

Resync operation after recovering the virtual machine may fail with error. (36136)

Description: This issue may occur when you add or remove(s) disks on source center, migrate resiliency group to the target data center, again add or remove the disks on target data center and migrate or recover back to the different ESX in cluster other than source data center.

This issue may occur in case of multi-node cluster. This scenario is very rare and may hit only in case of you modify the disk configuration on both data center. This issue may not occur in case of single node cluster.

Workaround: Delete the resiliency group and create it again.