Veritas™ Resiliency Platform 2.2 Solutions for Microsoft Hyper-V
- Section I. Overview of Resiliency Platform
- Section II. Preparing your environment
- Using array-based replication
- Managing disaster recovery network mapping
- Using array-based replication
- Section III. Working with resiliency groups
- Managing resiliency groups
- Configuring resiliency groups for remote recovery
- Managing virtual machines for remote recovery (DR) using 3rd party replication technology
- Managing virtual machines for remote recovery (DR) in Amazon Web Services
- Section IV. Managing disaster recovery
- Managing resiliency plans
- Creating a new resiliency plan template
- Monitoring risks, reports, and activites
- Managing evacuation plans
- Appendix A. General troubleshooting
- Appendix B. Sample policy and trust relationships for AWS
Prerequisites for network customization
Ensure the following prerequisites are met before you customised the IP addresses and the DNS settings.
IP, Gateway, Netmask, DNS, Domain Name, Mac address etc. information should present in the respective files of each network interface for which you want to customize the IP and DNS.
If multiple network interfaces (NICs) are assigned to a virtual machine, then you need to apply IP customization to all the NICs.
For virtual machines that are running on Linux ensure that NetworkManager and libvirtd service is in off state.
Virtual machines which are running on Hyper-V platform ensure that FQDN is set for each virtual machine.
The mac address configuration should be set as Manual/Static so that it does not change after the DR operation is performed. This is applicable only for recovery to premises data center.
For Windows virtual machines, ensure that user access control (UAC) is disabled on the hosts.