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
Instance failures and Auto Scaling Group behavior
The Amazon EC2 Auto Scaling Group (ASG) monitors the CloudPoint EC2 instance periodically. The ASG determines the status of the instance using the default status checks or via custom health checks. After the instance passes the status checks, the instance is marked as healthy.
If the state of the instance changes due to an external event, for example--if a disaster causes a loss of the instance, or if you manually stop the instance, the ASG immediately marks the instance as unhealthy and schedules it for a replacement.
The ASG creates a new instance from the same Amazon Machine Instance (AMI) and uses the same configuration as that of the original instance that was configured earlier. The ASG creates a new EBS volume using the snapshot, attaches that volume to the new EC2 instance, and then brings CloudPoint up on that instance.
You can suspend the health check process if you do not want ASG to replace the instance, for example in cases where you want to stop the instance for maintenance purposes.
For more information on how the Amazon EC2 Auto Scaling works, refer to the following Amazon AWS documentation:
https://docs.aws.amazon.com/autoscaling/ec2/userguide/healthcheck.html