Veritas CloudPoint Administrator's Guide
- Getting started with CloudPoint
- Section I. Installing and configuring CloudPoint
- Preparing for installation
- Deploying CloudPoint
- Deploying CloudPoint in the AWS cloud
- Using plug-ins to discover assets
- Configuring off-host plug-ins
- AWS plug-in configuration notes
- Google Cloud Platform plug-in configuration notes
- Microsoft Azure plug-in configuration notes
- HPE RMC plug-in configuration notes
- NetApp plug-in configuration notes
- Hitachi plug-in configuration notes
- InfiniBox plug-in configuration notes
- About CloudPoint plug-ins and assets discovery
- Configuring the on-host agents and plug-ins
- Oracle plug-in configuration notes
- Protecting assets with CloudPoint's agentless feature
- Preparing for installation
- Section II. Configuring users
- Section III. Protecting and managing data
- User interface basics
- Indexing and classifying your assets
- Protecting your assets with policies
- Tag-based asset protection
- Replicating snapshots for added protection
- Managing your assets
- About snapshot restore
- Single file restore requirements and limitations
- Additional steps required after a SQL Server snapshot restore
- Monitoring activities with notifications and the job log
- Protection and disaster recovery
- Section IV. Maintaining CloudPoint
- CloudPoint logging
- Troubleshooting CloudPoint
- Working with your CloudPoint license
- Managing CloudPoint agents and plug-ins
- Upgrading CloudPoint
- Uninstalling CloudPoint
- Section V. Reference
Requirements for replicating snapshots
Ensure that you add the AWS source and cross account (using the CloudPoint AWS plug-in) configuration in CloudPoint. These are the AWS accounts between which you want to replicate snapshots.
There are no additional requirements for replicating unencrypted snapshots.
Prerequisites for replicating encrypted snapshots:
Encryption key (KMS key) used for encryption must have the same name in both regions; that is, they should have the same key alias (in terms of AWS).
If encryption key with the same name is not present, then the replication fails with the following error:
KMS key <encryption_key_arn> not present in target region: <target_region>
For cross-account replication, the Customer Managed Key (CMK) that is used for encrypting the snapshot in the source region must be shared with the AWS account associated with the target region.
For cross-account replication, each CMK must grant access to the other account. Add the cross account information in the CMK of the source account and conversely, add the source account information in the CMK of the cross account (the target AWS account).
For cross-account replication, the AWS IAM user or role associated with the snapshot source region's AWS account (source AWS account) must have the following permissions:
ModifySnapshotAttribute
andCopySnapshot
on the EC2 instanceDescribeKey
andReEncrypt
on the KMS key that is used to encrypt the original snapshot
For cross-account replication, the AWS IAM user or role associated with the snapshot replication target region's AWS account (target AWS account) must have the following permissions:
CreateGrant
,DescribeKey
, andDecrypt
on the KMS key that is used to encrypt the original snapshotCreateGrant
,Encrypt
,Decrypt
,DescribeKey
, andGenerateDataKeyWithoutPlainText
on the KMS encryption key used while performing theCopySnapshot
operation on the original snapshot
More Information