Please enter search query.
Search <book_title>...
Product Documentation
Last Published:
2019-11-21
Product(s):
Resiliency Platform & CloudMobility (3.4)
- 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
Example IAM policies
Following is an example of permissions that are required for creating bucket and deploying the Data Gateway in Amazon Web Services (AWS).
{ "Version": "2012-10-17", "Statement": [ { "Action": [ "lambda:CreateFunction", "lambda:AddPermission", "lambda:CreateAlias", "lambda:GetFunction", "lambda:GetFunctionConfiguration", "lambda:InvokeFunction", "lambda:ListVersionsByFunction", "lambda:PublishVersion", "s3:CreateBucket", "s3:PutBucketNotification", "iam:CreateRole", "iam:CreatePolicy", "iam:PutRolePolicy", "iam:GetRole", "iam:PassRole", "sqs:CreateQueue", "sqs:GetQueueAttributes", "sqs:SetQueueAttributes" ], "Effect": "Allow", "Resource": "*" }, { "Action": [ "events:DescribeRule", "events:PutRule", "events:PutTargets" ], "Effect": "Allow", "Resource": [ "*" ] }, { "Action": [ "cloudwatch:PutMetricAlarm" ], "Effect": "Allow", "Resource": [ "*" ] }, { "Action": [ "sns:ListTopics", "sns:CreateTopic", "sns:SetTopicAttributes", "sns:Subscribe" ], "Effect": "Allow", "Resource": [ "*" ] }, { "Action": [ "s3:ListBucket" ], "Effect": "Allow", "Resource": [ "arn:aws:s3:::deployment_bucket_1", ] }, { "Action": [ "s3:GetObject", "s3:PutObject" ], "Effect": "Allow", "Resource": [ "arn:aws:s3:::deployment_bucket_1", ] }, { "Action": [ "apigateway:POST", "apigateway:PATCH", "apigateway:GET", "apigateway:PUT" ], "Effect": "Allow", "Resource": [ "arn:aws:apigateway:AWS_region::/restapis", "arn:aws:apigateway:AWS_region::/restapis/*", "arn:aws:apigateway:AWS_region::/account" ] }, { "Action": [ "dynamodb:CreateTable", "dynamodb:DescribeTable", "dynamodb:PutItem" ], "Effect": "Allow", "Resource": "arn:aws:dynamodb:AWS_region:AWS_account_ID:table/Veritas-DGW-*" }, { "Action": [ "cloudformation:GetTemplateSummary", "cloudformation:ListStacks", "cloudformation:CreateStack", "cloudformation:DescribeStackEvents", "cloudformation:DescribeStacks", "cloudformation:UpdateStack" ], "Effect": "Allow", "Resource": "*" } ] }
Following is an example of permissions that are required for deleting the Data Gateway in Amazon Web Services (AWS).
{ "Version": "2012-10-17", "Statement": [ { "Action": [ "lambda:DeleteFunction", "lambda:RemovePermission", "lambda:DeleteAlias", "s3:DeleteBucket", "iam:DeleteRole", "iam:DeletePolicy", "iam:DeleteRolePolicy", "sqs:DeleteQueue" ], "Effect": "Allow", "Resource": "*" }, { "Action": [ "apigateway:DELETE" ], "Effect": "Allow", "Resource": "*" }, { "Action": [ "dynamodb:DeleteTable", "dynamodb:DeleteItem" ], "Effect": "Allow", "Resource": "arn:aws:dynamodb:AWS_region:AWS_account_ID:table/*" }, { "Action": [ "cloudwatch:DeleteAlarms" ], "Effect": "Allow", "Resource": "*" }, { "Action": [ "sns:DeleteTopic", "sns:GetTopicAttributes" ], "Effect": "Allow", "Resource": "*" }, { "Action": [ "events:RemoveTargets", "events:DeleteRule" ], "Effect": "Allow", "Resource": "*" }, { "Action": [ "cloudformation:DeleteStack" ], "Effect": "Allow", "Resource": "*" } ] }
In the above examples, deployment_bucket_1 is the deployment bucket that contain the stack templates. AWS_account_ID is the account ID of your AWS account and AWS_region is the region where you are deploying the Data Gateway.
Note:
The deployment permission and the delete permission can also be combined into a single policy.