Product Documentation
- Section I. Overview and planning
- Introduction to Resiliency Platform
- About Resiliency Platform features and components
- Replication in a Resiliency Platform deployment
- About Veritas Resiliency Platform Data Mover
- About Elastic Networking Adapter (ENA) support in Resiliency Platform
- Recovery to cloud data center
- Recovering virtual machines to AWS
- Recovering virtual machines to Azure
- Recovering virtual machines to Google Cloud Platform
- Recovering virtual machines to vCloud Director
- Recovering virtual machines to Orange Recovery Engine
- Recovering physical machines using Resiliency Platform
- Recovery to on-premises data center
- Deployment checklist
- Checklist for recovery of virtual machines to AWS
- Checklist for recovery of virtual machines to Azure
- Checklist for recovery of virtual machines to Orange Recovery Engine
- Checklist for recovery of virtual machines to Google Cloud Platform
- Checklist for recovery of virtual machines to vCloud Director
- Checklist for recovery to on-premises data center using Resiliency Platform Data Mover
- Checklist for recovery of virtual machines using NetBackup
- Checklist for recovery of virtual machines using third-party replication technology
- Checklist for recovery of application using third-party replication technology
- Checklist for recovery of virtual machines to AWS
- System requirements
- Manage licenses
- Using the Web Console
- Introduction to Resiliency Platform
- Section II. Deploying and configuring the virtual appliances
- Deploy and configure
- Deploy and download the Resiliency Platform virtual appliances
- About deploying the Resiliency Platform virtual appliances
- Downloading the Veritas Resiliency Platform virtual appliances
- Deploying virtual appliances in AWS
- Deploying virtual appliances in Azure
- Deploying virtual appliances in Google Cloud Platform
- Deploying the virtual appliances in Google Cloud Platform using OVA files
- Prerequisites for deploying the virtual appliances in Google Cloud Platform
- Deploying the virtual appliances in Google Cloud Platform using OVA files
- Deploying virtual appliances in vCloud Director
- Deploying the virtual appliances in Orange Recovery Engine
- About configuring the Resiliency Platform components
- Virtual appliance security features
- About hotfixes
- Deploy and download the Resiliency Platform virtual appliances
- Depoly virtual appliances through Marketplace
- Deploying the virtual appliances in AWS through AWS Marketplace
- Prerequisites for deploying the virtual appliances in AWS
- Deploying the virtual appliances in Azure through Azure Marketplace
- Deploying the virtual appliances in AWS through AWS Marketplace
- Apply Updates
- About applying updates to Resiliency Platform
- Step 1: Prepare for upgrade
- Step 2: Upgrading the Resiliency Platform (Detach / attach the disk)
- About applying updates to Resiliency Platform
- Deploy and configure
- Section III. Setting up and managing the resiliency domain
- Managing the resiliency domain
- Getting started with a new Resiliency Platform configuration
- Managing Resiliency Managers
- Managing Infrastructure Management Servers
- Managing on-premises data centers
- Managing cloud configurations
- Managing private cloud configurations
- Integrating with NetBackup
- Recovering virtual machines to premises target data center
- Recovering virtual machines to cloud target data center
- Support for NetBackup Cloud Recovery Server configured with Veritas Alta Recovery Vault as storage account
- Integrating with InfoScale clusters
- Prerequisites for supporting InfoScale cluster node in Veritas Resiliency Platform
- Configuring InfoScale clusters in Resiliency Platform
- Managing the custom application or replication type in Resiliency Platform
- Managing the resiliency domain
- Section IV. Adding the asset infrastructure
- Manage Resiliency Platform host assets
- Prerequisites for adding hosts
- Removing hosts
- Preparing host for replication
- Manage VMware assets
- Managing VMware virtualization servers
- Prerequisites for adding VMware virtualization servers
- Prerequisites for adding VMware virtualization servers
- Managing VMware virtualization servers
- Manage Veritas Replication VIB
- Manage Hyper-V assets
- Manage Gateways
- About Replication Gateway pair
- Managing Data Gateway
- Manage enclosure assets
- Adding a discovery host
- Configuration prerequisites for adding storage enclosures to an IMS
- Adding storage enclosures
- Adding RecoverPoint appliance for replication
- Manage NetBackup primary pairing
- Manage Recovery Readiness Bundle
- Manage Resiliency Platform host assets
- Section V. Managing networks
- Manage networks
- Managing network objects in Resiliency Platform
- Network objects in Resiliency Platform
- DNS server configuration settings
- Managing network pairs
- Mapping network objects (Production and Rehearsal mapping)
- Manage networks
- Section VI. Managing settings
- Manage settings
- Managing settings for alerts and notifications and miscellaneous product settings
- Throttling the notifications
- Managing user authentication and permissions
- Configuring authentication domains
- Managing settings for alerts and notifications and miscellaneous product settings
- Manage settings
- Section VII. Working with resiliency groups
- Organize assets
- Editing a resiliency group
- Deleting a resiliency group
- Viewing resiliency group details
- Manage virtual business services
- About virtual business services
- Organize applications
- Managing service objectives
- Organize assets
- Section VIII. Configuring for disaster recovery
- Configure using Resiliency Platform Data Mover
- Managing virtual machines for remote recovery (DR) in Amazon Web Services
- Prerequisites for configuring VMware virtual machines for recovery to AWS
- AWS Customization options panel
- Managing virtual machines for remote recovery (DR) from AWS region to AWS region
- Managing virtual machines for remote recovery (DR) to Azure
- Managing virtual machines for remote recovery (DR) from Azure to Azure
- Managing virtual machines for remote recovery (DR) to Orange Recovery Engine
- Managing virtual machines for remote recovery (DR) in vCloud Director
- Managing virtual machines for remote recovery (DR) to Google Cloud Platform
- Managing virtual machines for remote recovery (DR) using Resiliency Platform Data Mover
- Managing physical machines for remote recovery (DR) using Resiliency Platform Data Mover
- Configure using NetBackup
- Managing the virtual machines for recovery to Azure using NetBackup MSDP-C.
- Configure using 3rd party replication technology
- Preparing VMware virtual machines for using array-based replication
- Preparing Hyper-V virtual machines for using array-based replication
- Managing virtual machines for remote recovery (DR) using 3rd party replication technology
- Managing applications for remote recovery (DR)
- Preparing VMware virtual machines for using array-based replication
- Configure using Resiliency Platform Data Mover
- Section IX. Managing disaster recovery
- Perform DR operations for virtual machines
- About Rehearse operation
- Performing the rehearsal operation for virtual machines
- Performing the recover operation for resiliency group
- Recovering virtual machines with multiple recovery points
- About Rehearse operation
- Perform DR operations on a VBS
- Perform DR operations for applications
- Evacuate assets
- Manage Resiliency Plans
- About custom script
- Perform DR operations for virtual machines
- Section X. Managing certificates
- Section XI. Product settings
- View activities
- Manage reports
- View logs
- Manage Risk Notifications
- Managing settings for alerts and notifications and miscellaneous product settings
- Throttling the notifications
- Section XII. Using Resiliency Platform APIs
- Section XIII. Troubleshooting and Using command line interface
- Troubleshoot
- Recovery of Resiliency Platform components from disaster scenarios
- Troubleshooting: NetBackup issues
- Resolving the Admin Wait state
- Troubleshooting: IP customization
- Use klish menu
- Use Application Enablement SDK
- Troubleshoot
Network pairs for recovering machines to on-premises data center (For NetBackup, third-party replication or Resiliency Platform Data Mover)
This topic mentions about the network pairs for recovering VMware or Hyper-V virtual machines to on-premises data centers if you are using NetBackup, third-party replication technologies or Resiliency Platform Data Mover.
You can map the networks in the source data center with networks in the DR data center. The Resiliency Platform uses this information to create appropriate VNICs in the recovered virtual machine and connect them to the appropriate networks according to the mappings.
Network pairs for VMware environment:
If on-premises data center is VMware, you can also create network group using port group/VLAN for VMware environment. When you pair network groups and perform a disaster recovery operation, virtual machines connected to different port groups can be migrated to same network on target data center.
For NSX-T type networks: Create NSX-T VLAN/Port Group to any of the standard, distributed, NSX -T type network or network group pair.
VMware vLAN/Port Group to vLAN/Port Group
With clustered ESX servers:
Distributed vLAN: Create vLAN/Port Group to vLAN/Port Group pair
Standard vLAN:
For each ESX standard vLAN, create vLAN/Port Group to vLAN/Port group pair
Create network group of vLAN/Port Group and create vLAN/Port Group network group to vLAN/Port Group network group pair
Without Cluster ESX servers: Create vLAN/Port Group to vLAN/Port Group pair
Subnet to Subnet (Optional, if no IP customization is done)
Network pairs for Hyper-V environment:
Hyper-V vSwitch to vSwitch
Hyper-V vLAN to vLAN (Optional)
Subnet to Subnet (Optional, if no IP customization is done)
To create network pairs, refer to the following topic
Creating network pairs between source and target data centers
Table: Network Mapping types for on-premise datacenters
Virtualization Technology | Network Mapping Type | Mandatory? | Purpose |
---|---|---|---|
VMware | vLAN to vLAN | Yes | To connect the VNIC of the recovered virtual machine to the Port Group |
HyperV | vSwitch to vSwitch | Yes | To connect the VNIC of the recovered virtual machine to the Port Group |
HyperV | vLAN to vLAN | Optional | To connect the VNIC of the recovered virtual machine to the Port Group |
In addition, if IP customization of the virtual machines is required, following mapping is also required to be defined:
Table: IP customization of the virtual machines
Virtualization Technology | Network Mapping Type | Mandatory | Purpose |
---|---|---|---|
VMware/HyperV | Subnet to Subnet | Yes | If IP customization is required |
If network mappings are not defined as per above table, the Resiliency Platform is unable to set the correct network configuration for the virtual machines after recovery. Following table identifies the effect of mappings on recovered virtual machines :
Table: Effect of mapping on recovered virtual machines
NIC configuration in source datacenter | Mapping done for NIC's vLAN/vSwitch | Mapping done for NIC's Subnet? | NIC status after recovery to remote datacenter | |
---|---|---|---|---|
Connectivity status | IP status | |||
Connected with IP address | Yes | Yes | NIC is created with same MAC address and is connected to the vLAN/vSwitch | New IP address is plumbed |
Connected with IP address | Yes | No | NIC is created with same MAC address and is connected to the vLAN/vSwitch | IP configuration is untouched |
Connected with IP address | No | * | NIC is created with same MAC address and is disconnected from vLAN/vSwitch | IP configuration is untouched |
Disconnected | * | * | NIC is not created | N/A |
* denotes that mapping may be defined or not defined