Please enter search query.
Search <book_title>...
Release Notes
Last Published:
2019-11-21
Product(s):
Resiliency Platform & CloudMobility (3.4)
- Release Overview
- System requirements
- Known issues
- General known issues
- A network group becomes faulted if any of its network member is unavailable (VRP-25636)
- HTML format is not supported for large sized reports (VRP-25649)
- RG creation for Virtual machines that replicated by NetApp SnapMirror, fails with error (23189)
- Rehearsal virtual machine Identifier is not same as workload virtual machine Identifier on an upgraded setup (22369)
- Replication becomes inactive after performing the Replace Gateway operation when the gateway has workload's snapshot disks attached (25722)
- Certain links in the help point to an older help version
- Known issues: Recovery from physical environment to virtual machines
- Known issues: Recovery to Amazon Web services (AWS)
- Known issues: Recovery to Azure
- Known issues: Recovery to vCloud
- Migrate or takeover operation may fail due to unavailability of independent disks on the vCloud Director (14639)
- After migrating back, the storage profile selection for the existing virtual machine may be incorrect (16901)
- After migrating back, the IP and MAC addresses assigned to a NIC are displayed incorrect on using Customize Network intent (16458)
- Known issues: Resiliency Platform Data Mover
- Known issues: Resiliency Platform Data Mover used for recovery to on-premises data center
- Known issues: Recovery from physical environment to virtual machines
- Known issues: Recovery using third-party replication
- Known issues: NetBackup integration
- A virtual machine backed up by multiple NBU master servers gets mapped with only one master server in the console (7608)
- Resiliency group task name shows TAKEOVER during evacuation (16466)
- Issue with support for restoring of UEFI-enabled virtual machines from Netbackup
- Restoring of virtual machines through Veritas Resiliency Platform may fail under certain conditions
- Known issues: Upgrade
- 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)
- "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)
- Kernel RPM package cannot be recovered if partially installed on VSA during upgrade (22625)
- For VC 6.5, VIB upgrade fails because of ESX maintenance mode (22493)
- New UI alignment is not updated after upgrade in same tab or session (22240)
- False risk of GW is not upgraded popup is shown while performing DR operation after upgrade (22768)
- General known issues
- Limitations
- General limitations
- Limitations: Recovery to vCloud Director
- Limitations: Recovery of physical machines to VMware virtual machines
- Limitations: Recovery of VMware virtual machines to on-premises data center using Resiliency Platform Data Mover
- Limitations: Recovery of VMware virtual machines to on-premises data center using third party replication
- Limitations: Windows hosts for Resiliency Platform Data Mover replication
- Limitations: Localization
- Limitations: Support for OpenStack configuration
The sequence of NICs is not maintained during recovery from a physical environment to a virtual machine (VRP-25439)
This issue is applicable if the recovery is from a physical environment to a virtual machine.
In case of recovering from a physical environment to a virtual machine, when multiple NIC IOTAP are migrated to VMware, then there is a possibility that the sequence of NIC is not as same as it was on the on-premise device.
Workaround:
To rectify this issue, do the following:
Provide the appropriate routes after the migration of IOTAP to VMware is complete.
Remove the existing gateway rule, if any, and add a rule for default gateway with appropriate NIC.
For example:
ip route del default via {default_gateway}
ip route add default via {default_gateway}