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
Providing inputs for Resiliency Platform CloudFormation Templates
You need to provide inputs for creating instances using CloudFormation templates (CFT). Some of the fields get auto populated with the default value, you can change the values if required. For rest of the parameters, you need to enter a valid value.
Table: EC2 Instance Configuration
Field | Description |
---|---|
Resiliency Manager Instance Name | Enter the name of the Resiliency Manager instance. |
IMS Instance Name | Enter the name of the IMS instance. |
Replication Gateway Instance Name | Enter the name of the Replication Gateway instance. |
EC2 Instance Type | This field is auto-populated with the best fit instance type. You can change the default value, if required. |
Key Pair for SSH access | Select the appropriate SSH key pair. While selecting the SSH key pair, ensure that you already have access to the pair. This is critical because SSH key pair is the only way to log in to the system and you cannot change the SSH key pair after the EC2 instance gets created. |
Create 'ImportSnapshotRole' AWS IAM Role for VRP? | Resiliency Platform requires ImportSnapshotRole for recovery of assets to AWS. Select Yes to create the role. Make sure that you haveNo if you already have ImportSnapshotRole role. permission. Select |
Staging Disk size for the Replication Gateway | Enter the size of the staging disk for Replication Gateway in the unit of GB. The minimum supported disk size of 50GB lets you protect up to 8 virtual machines and to protect more virtual machines an additional staging storage of 6 GB per virtual machine is required. |
Data Volume Type | Select the appropriate Volume Type for the data volume. This field has default value selected as 'gp2' volume type. You can change and select another as per your requirement. |
Resiliency Manager Data volume IOPS (Required only when selected Volume Type is IO1 from IO1 and IO2) | This value will be used when selected Volume Type is IO1 only .IOPS value must be between 100 to 64000. |
Infrastructure Management Server Data volume IOPS (Required only when selected Volume Type is IO1 from IO1 and IO2) | This value will be used when selected Volume Type is IO1 only. IOPS value must be between 100 to 64000. |
Replication Gateway Staging Disk IOPS (Required only when selected Volume Type is IO1 from IO1 and IO2) | This value will be used when selected DataVolumeType is IO1. The maximum ratio of provisioned IOPS to requested volume size (in GiB) is 50:1. For example, a 100 GiB volume can be provisioned with up to 5,000 IOPS. If appropriate IOPS value is not selected , the deployment fails. This value will be used when selected DataVolumeType is IO2. The maximum ratio of provisioned IOPS to requested volume size (in GiB) is 500:1. For example, a 100 GiB volume can be provisioned with up to 50,000 IOPS. If appropriate IOPS value is not selected , the deployment fails. |
KMS Key ARN for Staging Disk encryption | If you want to encrypt staging disks attached to the gateways using the KMS key, then select ARN of the respective KMS from the KMS Key drop-down. Else keep the default value as 'Not Encrypted'. |
Table: Resiliency Manager Network Configuration
Field | Description |
---|---|
Network Interface to be used for communication with other Resiliency Managers | Select the network interface that can be used to communicate with other Resiliency Managers in the resiliency domain. NAT settings are applicable for this role. If you want to use this network interface in a NAT environment, provide NAT details in the form. |
Network Interface to be used for communication with Infrastructure Management Servers | Select the network interface that can be used to communicate with Infrastructure Management Servers. NAT settings are applicable for this role. If you want to use this network interface in a NAT environment, provide NAT details in the form. |
Network Interfaces to be used for accessing the User Interface | Select the network interfaces that can be used to access the Resiliency Manager web user interface. NAT settings are applicable for this role. If you want to use this network interface in a NAT environment, provide NAT details in the form. |
Network Interface to be used as the default gateway | Select the network interface that can be used by default for outgoing communication. |
Resiliency Manager eth0 Subnet | Select the subnet which can be connected to the eth0 network interface. |
Resiliency Manager eth1 Subnet | Select the subnet which can be connected to the eth1 network interface. This input is only relevant if you have selected eth1 for one of the communication roles. You should provide a valid subnet always. |
Is the eth0 Network Interface behind NAT? | If NAT settings are applicable for the communications you have selected for eth0 and if you wish to use NAT with eth0, select Yes. |
Resiliency Manager eth0 NAT Hostname (Optional) | Provide the NAT hostname for eth0 if applicable |
Resiliency Manager eth0 NAT IP (Optional) | Provide the NAT IP for eth0 if applicable |
Is the eth1 Network Interface behind NAT? | If NAT settings are applicable for the communications you have selected for eth1 and if you wish to use NAT with eth1, select Yes. |
Resiliency Manager eth1 NAT Hostname (Optional) | Provide the NAT hostname for eth1 if applicable |
Resiliency Manager eth1 NAT IP (Optional) | Provide the NAT IP for eth1 if applicable |
Table: Infrastructure Management Server Network Configuration
Field | Description |
---|---|
Network Interface to be used for communication with Resiliency Managers | Select the network interface that can be used to communicate with Resiliency Managers. NAT settings are applicable for this role. If you want to use this network interface in a NAT environment, provide NAT details in the form. |
Network Interface to be used for communication with Replication Gateways | Select the network interface that can be used to communicate with Replication Gateways. NAT settings are applicable for this role. If you want to use this network interface in a NAT environment, provide NAT details in the form. |
Network Interface to be used as the default gateway | Select the network interface that can be used by default for outgoing communication. |
IMS eth0 Subnet | Select the subnet which can be connected to the eth0 network interface. |
IMS eth1 Subnet | Select the subnet which can be connected to the eth1 network interface. This input is only relevant if you have selected eth1 for one of the communication roles. You should provide a valid subnet always. |
Is the eth0 Network Interface behind NAT? | If NAT settings are applicable for the communications you have selected for eth0 and if you wish to use NAT with eth0, select Yes. |
IMS eth0 NAT Hostname (Optional) | Provide the NAT hostname for eth0 if applicable |
IMS eth0 NAT IP (Optional) | Provide the NAT IP for eth0 if applicable |
Is the eth1 Network Interface behind NAT? | If NAT settings are applicable for the communications you have selected for eth1 and if you wish to use NAT with eth1, select Yes. |
IMS eth1 NAT Hostname (Optional) | Provide the NAT hostname for eth1 if applicable |
IMS eth1 NAT IP (Optional) | Provide the NAT IP for eth1 if applicable |
Table: Replication Gateway Network Configuration
Field | Description |
---|---|
Network Interface to be used for communication with the Infrastructure Management Server | Select the network interface that can be used to communicate with the Infrastructure Management Server. NAT settings are applicable for this role. If you want to use this network interface in a NAT environment, provide NAT details in the form. |
Network Interface to be used for communication with peer gateways | Select the network interface that can be used to communicate with peer gateways. NAT settings are applicable for this role. If you want to use this network interface in a NAT environment, provide NAT details in the form. |
Network Interface to be used for communication with workload Virtual Machines | Select the network interfaces that can be used for communication with the workload Virtual Machines. NAT settings are applicable for this role. If you want to use this network interface in a NAT environment, provide NAT details in the form. |
Network Interface to be used as the default gateway | Select the network interface that can be used by default for outgoing communication. |
Replication Gateway eth0 Subnet | Select the subnet which can be connected to the eth0 network interface. |
Replication Gateway eth1 Subnet | Select the subnet which can be connected to the eth1 network interface. This input is only relevant if you have selected eth1 for one of the communication roles. You should provide a valid subnet always. |
Replication Gateway eth2 Subnet | Select the subnet which can be connected to the eth2 network interface. This input is only relevant if you have selected eth2 for one of the communication roles. You should provide a valid subnet always. |
Is the eth0 Network Interface behind NAT? | If NAT settings are applicable for the communications you have selected for eth0 and if you wish to use NAT with eth0, select Yes. |
Replication Gateway eth0 NAT Hostname (Optional) | Provide the NAT hostname for eth0 if applicable |
Replication Gateway eth0 NAT IP (Optional) | Provide the NAT IP for eth0 if applicable |
Is the eth1 Network Interface behind NAT? | If NAT settings are applicable for the communications you have selected for eth1 and if you wish to use NAT with eth1, select Yes. |
Replication Gateway eth1 NAT Hostname (Optional) | Provide the NAT hostname for eth1 if applicable |
Replication Gateway eth1 NAT IP (Optional) | Provide the NAT hostname for eth1 if applicable |
Is the eth2 Network Interface behind NAT? | If NAT settings are applicable for the communications you have selected for eth2 and if you wish to use NAT with eth2, select Yes. |
Replication Gateway eth2 NAT Hostname (Optional) | Provide the NAT hostname for eth2 if applicable |
Replication Gateway eth2 NAT IP (Optional) | Provide the NAT IP for eth2 if applicable |
Table: Common Network Configuration
Field | Description |
---|---|
VPC ID | Ensure the following while selecting the VPC:
|
CIDR block to allow inbound access | Provide CIDR block to allow inbound access to the appliances which will be set as source in Security Group. Provide a valid value considering your VPC and subnets configuration. If required, you can modify security group later according to your requirement. |
Table: Resiliency Platform Installation Parameters
Field | Description |
---|---|
NTP Server | FQDN or IP address of the NTP server to be used for the instances. In case of multiple values, enter the space-separated values. |
TimeZone | Select the timezone for the instances. |
Table: Data Gateway Deployment Information
Field | Description |
---|---|
Data Gateway deployment bucket name | Make sure that the deployment bucket pre-exists and is created in the local region where the CFT is being deployed. |
Deploy Veritas Data Gateway? | Optional parameter You need to deploy Data Gateway only if you want to use Object Storage for replication. See About Data Gateway. |
Does the Data Gateway bucket already exist? | Select Yes if the Data Gateway already exists. If you want to re-use an existing Data Gateway Bucket, that bucket should also be local to the region in which the CFT is being deployed. |
SNS Topic Protocol | Select a protocol from the list. |
SNS Topic Endpoint | Provide an endpoint that is appropriate for the selected SNS topic protocol. |
More Information
Deploying the virtual appliances in AWS through AWS Marketplace