Veritas™ Resiliency Platform 2.2 Update 3 Release Notes

Last Published:
Product(s): Resiliency Platform & CloudMobility (2.2)
  1. Overview
    1.  
      About Veritas Resiliency Platform
    2.  
      About Resiliency Platform features and components
    3. New features and changes in Veritas Resiliency Platform 2.2
      1.  
        Updates released for Veritas Resiliency Platform 2.2
      2.  
        Recovery of assets in vCloud
      3.  
        Introducing two new service objectives
      4.  
        NetBackup integration enhancements in Veritas Resiliency Platform 2.2
      5.  
        Heterogeneous Virtual Business Service (VBS)
      6.  
        Internationalization support for Veritas Resiliency Platform
    4.  
      Deprecated support in Resiliency Platform 2.2
    5.  
      What is not supported?
    6.  
      Using the product documentation
  2. System requirements
    1.  
      Supported hypervisors for deploying Resiliency Platform virtual appliance
    2.  
      System resource requirements for Resiliency Platform
    3.  
      Network and firewall requirements
  3. Fixed issues
    1.  
      Fixed issues
  4. Known issues
    1.  
      Disaster recovery (DR) configuration for resiliency group fails if Microsoft Hyper-V Replica is configured after you add a virtual machine in Resiliency Platform
    2.  
      In the VM Inventory report, instead of allocated memory, Resiliency Platform shows the total memory of the virtual machines
    3.  
      Certain validations do not work while creating a resiliency group of applications (3721289)
    4.  
      Rehearsal does not work after being aborted
    5.  
      The configure DR operation fails if virtual machines in the resiliency group belong to different servers
    6.  
      For resiliency groups containing VMware virtual machines with NFS datastore mounted from a NetApp volume with substring vol, Migrate or takeover operations may fail
    7.  
      The license expiry status is inconsistent on Resiliency Managers configured on different time zones
    8.  
      In the Hyper-V guest environment, the writable disk is shown in the Read-Only state (3785911)
    9.  
      Long SRDF device group names are not discovered (3786826)
    10.  
      Multiple repository paths on the same host are not allowed for the repository server (3734149)
    11.  
      Unknown state displayed for the Resiliency groups of dark sites that are part of VBS (3794650)
    12.  
      An Oracle custom application is not discovered if the instance names do not match (3796579)
    13.  
      VBS DR operations fail when an application resiliency group with unconfigured DR is added in VBS (3794105)
    14.  
      Expired resiliency plan cannot be executed even after editing the schedule (3861955)
    15.  
      Resiliency groups for Hitachi enclosures are not displayed on dashboard under Top RG by replication lag chart (3861173)
    16.  
      Snapshot disk is read only after rehearse operation is performed in Hyper-V with SRDF replication (3862088)
    17.  
      Static IP customization may not work under certain conditions (3862916, 3862237)
    18.  
      Need to manually refresh all assets after a site recovery (3861929)
    19.  
      Disk utilization risk not resolved after DR operations
    20.  
      Migrate operation becomes unresponsive if the operation is initiated from an unavailable site (3862253)
    21.  
      Remote cluster group dependencies not validated before migrate (3863082)
    22.  
      VBS migrate operation cannot be performed after failure (3862124)
    23.  
      Resiliency group state does not get updated when production site is down (3863081)
    24.  
      Replication information error (5170)
    25.  
      DNS customization does not work if FQDN is not defined (5037)
    26.  
      Previously configured network mapping may not work after re-adding a VMware vCenter server
    27.  
      Some versions of VMware Tools are not supported (4969)
    28.  
      Login to the Resiliency Manager console fails at times
    29.  
      Resiliency group and VBS names in charts are displayed incorrectly in Japanese and Chinese (8465)
    30.  
      Warning message may be displayed for network mapping (8644)
    31.  
      Cannot edit application discovery frequency for the uploaded application bundles from console (8433)
    32.  
      Metering report does not work for third-party replication technologies (8617)
    33.  
      Replication information not discovered for Hyper-V virtual machines configured in Microsoft Failover Clustering environment using Non-English characters in the CSV path (8697)
    34.  
      An operation may fail if invoked at a time when virtual machine is being migrated using Vmotion (6476)
    35.  
      vLan mapping compulsory for DRS enabled Vmware virtual machines (10322)
    36. Known issues: Resiliency Platform Data Mover
      1.  
        Virtual Machine protection using Data Mover has a few policy related limitations (5181)
      2.  
        Iofilter bundle not removed from ESX hosts even after unconfiguring virtual machines (5178)
      3.  
        Storage policy needs to be manually removed after all the virtual machines are unconfigured (5180)
      4.  
        VMDK and VMX files need to be in the same folder(5167)
      5.  
        Edit resiliency group operation may fail after rehearsal or cleanup rehearsal (5092)
      6.  
        Replication gets paused if you perform add disk operation (5182)
      7.  
        Cannot perform any operation after deleting disk from virtual machine (5182)
      8.  
        Data Mover virtual machine in no op mode risk cannot be resolved (5183)
      9.  
        Risks not generated after taking snapshot of virtual machine replicated using Data Mover(6886)
    37. Known issues: Recovery to Amazon Web services (AWS)
      1.  
        Some DHCP enabled NICs are not present on Cloud after migrate (7407)
      2.  
        One or more NICs of a migrated Windows virtual machine may not be visible (7718)
      3.  
        Cloud IPs get added to on-premise NICs after migrate back to the on-premise site and reboot (7713)
      4.  
        Migrate or takeover operations fail at the Add Network for AWS task and Create Network Interface sub-task (7719)
      5.  
        Sometimes network comes up on only one NIC although there are multiple NICs (8232)
    38. 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.  
        Operations for virtual machine do not work if the remote master server gets reconfigured (8600)
    39. Known issues: Recovery to vCloud
      1.  
        Resiliency group details in the console displays stale vCloud virtual machine entries after migrating back a resiliency group to the premises site (8326)
  5. Limitations
    1.  
      Rehearsal is not supported if volume is configured using asynchronous replication in IBM XIV enclosure
    2.  
      Limitations for on-premises Windows hosts for Resiliency Platform Data Mover replication
    3.  
      Hyper-V hosts having snapshots not supported for recovery to AWS
    4.  
      Computer name of virtual machine on vCloud differs if the name exceeds permitted character limit
    5.  
      Localization of adding application type is not supported
    6.  
      Datastore name with special characters
  6. Appendix A. Virtual appliance security features
    1.  
      Operating system security
    2.  
      Management Security
    3.  
      Network security
    4.  
      Access control security
    5.  
      Physical security

One or more NICs of a migrated Windows virtual machine may not be visible (7718)

After migration, one or more network interface cards (NIC) associated with a Windows virtual machine may not be visible from the operating system. You may not be able to connect to the migrated virtual machine using the IP address assigned to these invisible NICs.

Workaround:

In device manager, under network connections, all the NICs are listed. The NICs that are not visible in Network Connections are also listed here, but they show an error similar to the following:

Windows could not load drivers for this interface.

Right click on the network interface that is showing the error and click on Uninstall Device.

After the uninstallation, scan for hardware changes in the device manager. The NIC gets installed properly and is visible.