Please enter search query.
Search <book_title>...
Veritas™ Resiliency Platform 2.2 Deployment Guide
Last Published:
2017-04-07
Product(s):
Resiliency Platform & CloudMobility (2.2)
- Section I. Overview and planning
- Overview of Resiliency Platform
- Recovery to premises using third-party replication technologies
- Recovery to premises using Resiliency Platform Data Mover
- Recovery to AWS using Resiliency Platform Data Mover
- Recovery to vCloud Using Resiliency Platform Data Mover
- System requirements
- Section II. Deploying and configuring the virtual appliances
- Section III. Setting up and managing the resiliency domain
- Setting up the resiliency domain
- Managing Infrastructure Management Servers
- Managing NetBackup and NetBackup Appliances
- Adding NetBackup master server
- Managing Veritas InfoScale Operations Manager Server
- Managing Resiliency Platform Data Mover gateway pairing
- Setting up the resiliency domain
- Section IV. Adding the asset infrastructure
- Managing asset infrastructure
- Preparing and maintaining host assets
- Managing Hyper-V virtualization server assets
- Managing VMware virtualization server assets
- About adding a host for discovery of VMware servers
- Managing enclosure assets
- About the discovery host for enclosures
- Configuration prerequisites for adding storage enclosures to an IMS
- Adding storage enclosures
- Adding RecoverPoint appliance for replication
- Managing asset infrastructure
- Section V. Managing users and global product settings
- Managing licenses
- Managing user authentication and permissions
- Configuring authentication domains
- Managing service objectives
- Managing reports
- Managing settings
- Section VI. Updating or uninstalling the product
- Updating Resiliency Platform
- Using YUM virtual appliance as YUM server
- Uninstalling Resiliency Platform
- Updating Resiliency Platform
- Section VII. Troubleshooting and maintenance
- Troubleshooting and maintenance
- Displaying risk information
- Troubleshooting and maintenance
- Section VIII. Reference
Creating Amazon Machine Image
Once you upload the OVA files to Amazon S3 bucket, you need to use the AWS command line interface (CLI) to create an Amazon Machine Image (AMI) from the OVA files that you have uploaded. This AMI can be later used to launch the instances for deploying Resiliency Manager, Infrastructure Manager (IMS), and Replication Gateway in AWS.
To create Amazon Machine Image
- Go to the Command prompt and then go to AWS CLI.
- Refer to the AWS documentation for instructions on how to enter your AWS credentials and region and create a json file in the following format:
[ { "Description":"my description", "Format": "ova", "UserBucket":{ "S3Bucket":"my-bucket", "S3Key": "my-ova-key" } }]
Where, my-bucket is the name of your bucket and my-ova-key is the alias name that you provided for the OVA file.
- Run the following command to create an AMI:
aws ec2 import-image --description "my description" --disk-containers file://Mycontainers.json_with_path
Where, Mycontainers.json_with_path is the path and name of the json file that you have created.
- The above command displays a number of parameters and their values. Note down the value of ImportTaskId parameter.
- Run the following command to verify that the import task is complete and the AMI is ready to be used:
aws ec2 describe-import-image-tasks --import-task-ids MyImportTaskID
Where, MyImportTaskID is the task ID that you receive from the command described in the prior step.