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
Cross-account snapshot replication limitations
Make a note of the following limitations:
Cross-account replication support is not available for host-level snapshots.
Cross-account replication support is not available for Amazon Machine Instances (AMI).
The time required for the snapshot replication to complete is entirely dependent on the size and the target region's location. If the status of the replication job in the CloudPoint dashboard remains static, Veritas recommends that you verify the replication status in the target region using the AWS Management Console.
AWS has default limits defined for AWS services, accounts, and regions. The number of simultaneous operations that you can perform on a region are therefore restricted by these default settings. If you trigger multiple snapshot replication operations on a region, those jobs may appear queued in the CloudPoint dashboard, if the number of jobs cross the predefined limits for that region.
You must also note that snapshot replication utilizes AWS resources and that may involve an additional cost. Ensure that you consider the total cost involved and plan snapshot replication tasks accordingly.
https://docs.aws.amazon.com/general/latest/gr/aws_service_limits.html
After a snapshot is replicated between AWS accounts, you cannot remove the source account configuration using the CloudPoint UI.
The only way to remove the source account configuration is by using the following methods:
First, delete all the snapshots that are replicated to another AWS account region and then remove the source account configuration.
Use the following CloudPoint REST API to remove the source account configuration:
/v3/agents/{agendId}/plugins/{pluginName}/configs/{configId}?force=True