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
- Recovery options using Resiliency Platform
- Deployment checklist
- System requirements
- Manage licenses
- Using the Web Console
- Introduction to Resiliency Platform
- Section II. Deploying and configuring the virtual appliances
- Deploy and configure
- Deploying the virtual appliances in AWS through AWS Marketplace
- Deploying the virtual appliances in AWS using OVA files
- Deploying the Data Gateway in AWS
- Deploying the virtual appliances in Azure using PowerShell script
- Deploying the virtual appliances in Azure through Azure Marketplace
- Deploying the virtual appliances in vCloud
- Deploying the virtual appliances in HUAWEI CLOUD
- Deploying the virtual appliances in Orange Recovery Engine
- About configuring the Resiliency Platform components
- Virtual appliance security features
- About hotfixes
- Apply Updates
- About applying updates to Resiliency Platform
- Setting up the YUM server
- 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
- Integrating with InfoScale Operations Manager
- 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 Resiliency Platform host assets
- Section V. Managing networks
- Manage networks
- About network objects
- Manage settings
- Managing user authentication and permissions
- Configuring authentication domains
- Managing user authentication and permissions
- Manage networks
- Section VI. Working with resiliency groups
- Organize assets
- Viewing resiliency group details
- Manage virtual business services
- Organize applications
- Managing custom applications
- Managing service objectives
- Organize assets
- Section VII. 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) to Azure
- Managing virtual machines for remote recovery (DR) to OpenStack
- Managing virtual machines for remote recovery (DR) to HUAWEI CLOUD
- 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) using Resiliency Platform Data Mover
- Managing physical machines for remote recovery (DR) using Resiliency Platform Data Mover
- Configure using NetBackup
- 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 VIII. Managing disaster recovery
- Perform DR operations for virtual machines
- Performing the rehearsal operation for virtual machines
- 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 IX. Product settings
- View activities
- Manage reports
- View logs
- Manage Risk Notifications
- Managing settings for alerts and notifications and miscellaneous product settings
- Section X. Using Resiliency Platform APIs
- Section XI. Troubleshooting and Using command line interface
- Troubleshoot
- Recovery of Resiliency Platform components from disaster scenarios
- Resolving the Admin Wait state
- Use klish menu
- Use Application Enablement SDK
- Troubleshoot
About NAT support in Veritas Resiliency Platform
Network Address Translation (NAT) is a process in which one or more computers inside a private network are assigned a public address. NAT reduces the need for IPv4 public addresses and hides private network address ranges.
Resiliency Platform 3.3 provides support for NAT to enable communication from a private network to an external network. If there is a non-routable network between the source data center and the target data center, then You need to configure NAT only using IPv4 address for communication between Resiliency Platform appliances.
Resiliency Platform supports NAT only for the communication between Resiliency Platform components deployed in different data centers. These components need to communicate with each other over public IP address. NAT can exist in both the data centers or in any one of the data centers.
Resiliency Platform does not support NAT for communication between components deployed in the same data center. The components based in the same data center can communicate with each other over private IP address.
If a communication channel has been setup in a way that private IP address of the Resiliency Platform components is accessible in the other data center, then you need not configure NAT during the bootstrap process. For example, if you have setup VPN for communication between on-premises data center to AWS datacenter, then you need not configure NAT for Resiliency Platform components .
If there are multiple Resiliency Managers in one data center, then either NAT configuration should be done for all of them or for none of them. A mix of NAT configured Resiliency Managers and non-NAT configured Resiliency Managers within a single data center is not supported.
Following are the scenarios in which NAT configuration is required for Resiliency Platform virtual appliances:
Table: Scenarios in which NAT configuration is required
Communication between | Description | NAT configuration |
---|---|---|
Replication Gateway with Peer Replication Gateway | A Replication Gateway can communicate with the peer Gateway only over Public IP. | Required |
IMS with Resiliency Manager | If an IMS reports to a Resiliency Manager within the same data center, then it can communicate over private IP. | Not required |
If an IMS reports to a Resiliency Manager deployed in another data center, then it can communicate only over public IP. | Required | |
Resiliency Manager with another Resiliency Manager | If there are multiple Resiliency Managers in one data center and no Resiliency Manager in another data center, then all of the Resiliency Managers within the data center can communicate with each other over private IP. | Not required |
If there are multiple Resiliency Managers in one data center and at least one Resiliency Manager in another data center, then all of the Resiliency Managers need to communicate with each other only over public IP. In this case, you need to enable NAT reflection (Loopback NAT) for the data center where multiple Resiliency Managers are located. | Required |