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
Deploying the Data Gateway in AWS
If you want to use Object Storage replication for migrating your data center assets to AWS, you need to deploy and configure a Data Gateway in AWS environment.
See About Object Storage mode replication.
This Data Gateway is then added to the Resiliency Manager using the Resiliency Manager console.
To deploy the Data Gateway in AWS
- Prerequisites
- Download the zip file required for deploying the Data Gateway.
See Downloading the Veritas Resiliency Platform virtual appliances.
- Extract the zip file to a location of your choice. The following directories are extracted:
CloudFormation_Templates
Lambda_Function_Zip_Files
- Upload both the directories to an S3 bucket of your choice. Ensure that the S3 bucket is in the region where you want to deploy the Data Gateway.
Upload the directories at the root level of the bucket. Do not upload them to any subdirectory within the bucket.
- Open the CloudFormation service on the AWS web console.
- Click Create Stack.
- In the Select Template page, choose a stack template by using one of the following options:
Upload a template to Amazon S3: Select the
veritas-dgw-deployer-nested.yaml
file within theCloudFormation_Templates
directory from your local computer. This is the location where you have extracted the zip file.Specify an Amazon S3 template URL: This URL is the link to the file in the S3 bucket where you have uploaded the directories. To get this URL, go to Amazon S3 service, click on the bucket name, and then click the
CloudFormation_Templates
directory. Copy the URL displayed for theveritas-dgw-deployer-nested.yaml
file. This URL looks similar to the following:https://s3.amazonaws.com/S3_bucket_name/
CloudFormation_Templates/veritas-dgw-deployer-nested.yaml
Where, S3_bucket_name is the name of your S3 bucket.
- In the Specify Details page, enter the following information:
Stack name.
Deployment bucket name.
Data Gateway bucket name.
For Does the Data Gateway bucket exist field, select Yes to use an existing S3 bucket. Select No to create a new S3 bucket. Ensure that the bucket is in the same region where you want to deploy the data gateway.
Enter your choice for the SNS topic protocol and SNS topic endpoint fields to create an SNS topic and subscription. This topic and subscription is used for monitoring the Data Gateway.
See About Data Gateway monitoring through CloudWatch alarms.
- On the Options page, provide information for the Tags, Permissions, and Advanced fields. These are optional fields and you can skip providing information here. If you have chosen an IAM role, ensure that the role has all the permissions that are required to deploy the Data Gateway.
- Review the selection and select the acknowledgment check box for IAM resource creation. Click Create.
- When the stack status changes to CREATE_COMPLETE, you can view the resources that get created.
- From the Outputs of the main Data gateway stack, note down the value displayed for the APIGatewayRootUrl key. This is the root URL of the API component of the Data Gateway. You need to provide this root URL for adding the Data Gateway to the Resiliency Manager. The root URL looks similar to the following:
https://REST_api_resource_ID.execute-api.eu-west-1.amazonaws.com/VDGW
Where, REST_api_resource_ID is the resource ID of the REST API and eu-west-1 is the name of the region.
More Information