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
Deploying the virtual appliances in AWS through AWS Marketplace
Veritas Resiliency Platform enables you to deploy the virtual appliances in AWS through AWS Marketplace using CloudFormation templates. There are six offerings available for deploying the virtual appliances using CloudFormation templates:
Veritas Resiliency Platform Express Install: Installs Resiliency Manager, IMS, and Replication Gateway appliances in AWS. This template also provides options to install Veritas Data Gateway appliance in AWS.
Veritas Resiliency Platform Gateway Install: Installs an additional Replication Gateway appliance in AWS.
Veritas Resiliency Platform Resiliency Manager Install: Installs an additional Resiliency Manager appliance in AWS.
Veritas Resiliency Platform Infrastructure Management Install : Installs the Infrastructure Management server in AWS.
Veritas Resiliency Platform Resiliency Manager Upgrade : Upgrades the Resiliency Manager appliance in AWS.
Veritas Resiliency Platform Infrastructure Management Upgrade : Upgrades the Infrastructure Management server in AWS.
To deploy the virtual appliances in AWS using CloudFormation templates
- Prerequisites:
1. Create Amazon Virtual Private Cloud (VPC):
See Configuring Amazon VPC for deployment using CloudFormation Templates.
2. Refer IAM permission required:
See Permissions required in AWS Marketplace for IAM roles RM, IMS and Replication Gateway .
- Go to the AWS Marketplace and locate Veritas Resiliency Platform product.
- Select the fulfillment option from the options available: Express Install, Gateway Install, Resiliency Manager, or Infrastructure Management Server.
- AWS Marketplace lets you launch the selected option through CloudFormation Templates interface. You are redirected to the Create Stack page of AWS CloudFormation Template. The template URL is pre-populated for you. Click Next.
- On the next page, provide the values for the input fields:
See Providing inputs for Resiliency Platform CloudFormation Templates.
- Click Next and review the additional options for your stack. Select the check box in the Capabilities section.
- Click Next and review the summary displayed on the Review page.
- Click Create to create the instances. This step creates the EC2 instances, staging volume for Replication Gateway appliance, and required Security Groups. This step also completes the bootstrap for all the appliances.
- For multiple Network Interface card (NIC) instances, every NIC created is associated with a different security group.
- For security reasons, the CloudFormation template disables the SSH communication to the instances. Once the stack deployment completes, you need to enable the SSH communication to the instances for setting the admin password. This password is required for logging in to the Resiliency Manager console. A password is also required for adding the IMS, Replication Gateway appliances to Resiliency Manager.
Modify the security groups of each instance to include the inbound SSH port (TCP port 22) for the required source IP or security group.
Note:
The instances go through some automatic configuration steps immediately after deployment. If you connect to the instance via SSH and if the configuration is still in-progress, wait until all steps are completed and reconnect to the instance.
- Log in to the Resiliency Manager console and setup the initial infrastructure through Getting Started wizard.
Note:
For Express install, if creation of stack fails and rollback is enabled on failure, AWS takes care of all the clean-up required in this situation. However, to enable this clean-up, you need to manually delete the Elastic Network Interface (ENI) associated with the security group that is attached with ZipFileUploaderLambda function.
Note:
Instance Metadata Service v2 (IMDSv2) is introduced by AWS as security enhancement over IMDSv1. While using AWS CloudFormation template, there is no way to disable the IMDSv1 option. So this limits the AWS MarketPlace deployment to have IMDSv2 enabled. It can be changed later using AWS CLI.
See Getting started with a new Resiliency Platform configuration.