Please enter search query.
Search <book_title>...
Release Notes
Last Published:
2024-09-29
Product(s):
Resiliency Platform (10.4)
- Release Overview
- System requirements
- Known issues
- General known issues
- Known issues: Recovery to Amazon Web services (AWS)
- Known issues: Recovery from AWS region to AWS region
- Known issues: Recovery to Azure
- Known issues: Recovery to Azure using NetBackup MSDP-C
- Known issues: Google Cloud Platform
- 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
- Known issues: Upgrade
- Known issues: InfoScale clusters
- Known issues : Continuous Data Protection (CDP)
- Known issue: VMware vSphere 7.0 support
- Known issue: Managing security certificates and SSH host keys
- Known issues: Recovery of resiliency groups configured using multiple recovery points
- General known issues
- Fixed issues
- Limitations
- Limitations: Recovery of resiliency groups configured using multiple recovery points
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 physical machines with multiple NICs 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 host.
Resolution:
To rectify this issue, do the following:
Provide the appropriate routes after the migration of physical machines with multiple NICs 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}