Veritas™ Resiliency Platform 2.2 Solutions for VMware
- Section I. Overview of Resiliency Platform
- Overview of Resiliency Platform
- Overview of Resiliency Platform Data Mover
- Overview of recovery to on-premises data center
- Managing assets protected by NetBackup
- Overview of Amazon Web Services
- Overview of vCloud
- Section II. Preparing your environment
- Using array-based replication
- Using Veritas Resiliency Platform Data Mover
- Managing disaster recovery network mapping
- Managing Replication Gateway pairs
- 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) using Resiliency Platform Data Mover
- Managing virtual machines for remote recovery (DR) in Amazon Web Services
- Managing resiliency groups
- Section IV. Managing disaster recovery
- Rehearsing DR operations to ensure DR readiness
- Performing disaster recovery operations
- Rehearsing DR operations to ensure DR readiness
- Managing resiliency plans
- Creating a new resiliency plan template
- Monitoring risks, reports, and activities
- Managing evacuation plans
- Appendix A. General troubleshooting
- Resolving the Admin Wait state
- Appendix B. Sample policy and trust relationships for AWS
Setting up network mapping between production and recovery data centers
The network mapping operation eliminates the need to manually apply an IP address for each virtual machine at the recovery (DR) data center. After you have mapped the networks successfully, the IP addresses are computed programmatically, and applied to the virtual machines.
For VMware virtual machines, ensure that the mapping of all the concerned port groups (VLANs) across the data centers is configured before performing migrate, takeover, or rehearsal operations.
Else, network adapters of the virtual machines are not connected to any network after the operation. Similarly, ensure that the subnets are mapped across the data centers when IP customization is required.
If subnets are mapped and IP customization option is selected during the DR operation and if the port groups are not mapped, then IP customization fails for the concerned network adapters, causing the DR operations to fail.
This is not applicable if the recovery data center is Amazon Web Services (AWS). For AWS, subnet to subnet mapping is sufficient.
Note that the subnets are discovered only when the virtual machines are running.
If the recovery data center is AWS, then ensure that the production subnet and the rehearsal subnet are in the same virtual private cloud (VPC).
Note:
When you clone your virtual machines, ensure that you assign the appropriate host name and IP address to the cloned virtual machines.
To set up network mapping between production and recovery data centers
- Navigate
Disaster Recovery Settings (navigation pane)
Do one of the following:
On Overview tab, click + New Network Pair.
On Network tab, click + Create Pair.
Previously created network pairs are listed in the table. You can create a new pair or delete an existing pair.
- In the Network Mapping page, select the source and the target data centers, and the network types that should be the part of your network pair.
If recovery is in AWS, select subnets.
- Click Choose selected or drag and drop the selections in the drag area at the bottom.
- Click Next to submit your selections.
- To remove a network pair, right-click the pair and select Delete Pair.
You cannot edit a network pair. Instead you need to delete the pair and create another.