Release Notes

Last Published:
Product(s): Resiliency Platform & CloudMobility (3.3.2)
  1. Release Overview
    1. New features and changes in Veritas Resiliency Platform 3.3.2
      1.  
        Removal of Windows Install Hosts
      2.  
        Monitoring API support
      3.  
        Replace faulty or healthy gateway
      4.  
        Simplified licensing
      5.  
        Extended In-Guest IOTAP
      6.  
        Mark Resiliency Group in maintenance mode
      7.  
        Collect logs from Veritas Resiliency Platform appliances from the user interface
      8.  
        Service pack delivery mechanism
      9.  
        Localization support is extended to Chinese language
      10.  
        Improved user interface
      11.  
        Separate Security Group for rehearsal and disaster recovery operations
      12.  
        Introduced new risk signatures
    2.  
      Using the product documentation
    3.  
      More information
  2. System requirements
    1.  
      System resource requirements for Resiliency Platform
    2.  
      Network and firewall requirements
  3. Fixed issues
    1.  
      Fixed issues
  4. Known issues
    1. General known issues
      1.  
        Migrate operation in VMware environment may sometimes fail due to timeout (12642)
      2.  
        RG creation for Virtual machines that replicated by NetApp SnapMirror, fails with error (23189)
      3.  
        Rehearsal virtual machine Identifier is not same as workload virtual machine Identifier on an upgraded setup (22369)
    2. Known issues: Recovery to Amazon Web services (AWS)
      1.  
        Delete resiliency group operation fails at Detach volume sub task (12804)
      2.  
        Configuring resiliency group for disaster recovery fails at Attach Disk to Replication Gateway sub task (12804)
    3. 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)
    4. 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)
    5. 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)
    6. 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)
    7. Known issues: NetBackup integration
      1.  
        MAC address starting with 00:0c:29 not supported for VMware virtual machines (7103)
      2.  
        A virtual machine backed up by multiple NBU master servers gets mapped with only one master server in the console (7608)
      3.  
        A transient virtual machine remains in the ESX server in one scenerio (7413)
      4.  
        Resiliency group task name shows TAKEOVER during evacuation (16466)
    8. Known issues: Recovery of InfoScale applications
      1.  
        Remote cluster group dependencies not validated before migrate (3863082)
    9. Known issues: Upgrade
      1.  
        Upgrade of Replication Gateway fails if a Veritas Replication Set is in stopping state (19976)
      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)
  5. Limitations
    1.  
      General limitations
    2.  
      Limitations: Recovery to AWS
    3.  
      Limitations: Recovery to vCloud Director
    4.  
      Limitations: Recovery of physical machines to VMware virtual machines
    5.  
      Limitations: Recovery of VMware virtual machines to on-premises data center using Resiliency Platform Data Mover
    6.  
      Limitations: Recovery of VMware virtual machines to on-premises data center using third party replication
    7.  
      Limitations: Windows hosts for Resiliency Platform Data Mover replication
    8.  
      Limitations: Localization

Upgrade of Replication Gateway fails if a Veritas Replication Set is in stopping state (19976)

While upgrading a Replication Gateway, the operation fails if one or more Veritas Replication Sets are in 'stopping' state.

Workaround

Identify the Veritas Replication Sets associated with the Replication Gateway which are in 'stopping' state. Abort the replication for these sets and then retry to upgrade the gateway. You can abort the process using the KLISH menu: Datamover->Operation-> Abort.