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 deploying virtual appliances through Azure Marketplace
You need to provide inputs for creating instances using Azure Resource Manager (ARM) templates. 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.
To create the appliance images, you need to provide inputs in following three sections:
Table: Basic settings for Azure deployment
Input field | Description |
---|---|
Select Deployment Type | Select the appropriate deployment type from the given options. By default, all the appliances are selected which will deploy a Resiliency Manager, an IMS, a Replication Gateway, Resiliency Manager upgrade and IMS upgrade appliance. You can select other option as per the requirement. |
Password for admin user | Set the password for admin user. The admin user and password is later used for configuring the appliances. |
Confirm password | Provide same password for confirmation. |
NTP Servers | Resiliency Platform requires NTP servers for synchronizing time across all the appliances. Specify FQDN or IP addresses of one or more (space separated) NTP servers. It is recommended to use 3 or more (an odd number) NTP servers. |
Timezone | Timezone to be set for all the Resiliency Platform appliances. |
Subscription | Select the subscription of Azure account, to be used for deploying the virtual appliances. |
Resource group | Specify the name of an existing resource group or a new resource group to be created. |
Location | Select the location where you want to create the appliances. |
Table: Advanced settings for Azure deployment
Input field | Description |
---|---|
Resiliency Manager Settings | |
Instance Name | Name of the appliance instance |
Host name | Hostname of the appliance. This is changed and allocated from DHCP details |
Instance Size | Size of the appliance instance |
Data Disk Size in GB | Additional disk of minimum 100 GB required for Resiliency Manager |
Infrastructure Management Server (IMS) Settings | |
Instance Name | Name of the appliance instance |
Host name | Hostname of the appliance. This is changed and allocated from DHCP details |
Instance Size | Size of the appliance instance |
Data Disk Size in GB | Additional disk of minimum 40 GB required for IMS |
Replication gateway Settings | |
Instance Name | Name of the appliance instance |
Host name | Hostname of the appliance. This is changed and allocated from DHCP details |
Instance Size | Size of the appliance instance |
Staging disk size in GB | Additional disk of minimum 50 GB required for Replication Gateway |
Staging disk type | Choose staging disk type for Replication Gateway. Learn more about the managed disk types. Managed disk types |
Enable Ultra disk compatibility | Choose this check box if you want to support ultra disks on your Replication Gateway instance |
Availability Zone | Specify an availability zone if the selected region for deploying the Replication Gateway has availability zones. Keep this field empty if the region does not support availability zones. The deployment can fail if an incorrect input is provided. See Using Azure ultra disks |
Table: Network settings for Azure deployment
Input field | Description |
---|---|
Is Multi-NIC Deployment? | You can deploy Resiliency Manager, IMS, or Replication Gateway with multiple network interfaces. These interfaces can be used for different communication purpose. Select if required.. |
Are Both NICs in Same Subnet | Select if multiple interfaces are part of same subnet of a virtual network. |
Network Name | Specify the name of an existing network. |
Select Subnet | Select a subnet to be associated with the virtual appliance. |
Role of NICs' | In case of multiple interfaces, select NIC for its communication purpose. Make sure you select 'eth0' for at least one intent. If it is single NIC deployment then same NIC is used. |
Is the NIC eth0 behind NAT? | Select if NAT is used in your network setup and provide NAT IP and fully qualified NAT hostname. |
Similar input is required for configuring IMS, Replication Gateway.