Veritas CloudPoint Release Notes
- Getting help
- New features, enhancements, and changes
- Tag-based asset protection for production environments
- Support for AWS nitro-based instances that use NVMe devices
- Single File Restore (SFR) supported on Linux root file system
- Support for Hitachi storage arrays
- Support for InfiniBox storage arrays
- CloudPoint REST API version updated to /v3
- Updates to the CloudPoint plug-in for Microsoft Azure
- Unconfigure plug-in and disconnect host option now available from the CloudPoint user interface (UI)
- Support for AWS GovCloud (US)
- Limitations
- CloudPoint support for AWS regions and GCP zones (14446)
- Limitations on replicating and restoring assets
- If two snapshot operations are performed on an instance at the same time, the second one fails
- You cannot delete snapshots created by an Amazon snapshot policy
- CloudPoint cannot snapshot LUNs which are under a consistency group for Dell EMC Unity arrays (3977)
- Known issues
- Azure instance image cleanup failed (7253)
- Agent services restarting continuously (8030)
- CloudPoint does not support 'Overwrite existing' restore option for file system and application's host-level snapshot (8924)
- If a snapshot creation policy is run in parallel with in-place restore, the policy may fail. When the policy is run again, it succeeds (8142)
- When AWS is configured with different regions in parallel, stacks are added in the logs (7481)
- Some errors are logged in the nginx_error.log file (6593)
- CloudPoint is not able to find Google cloud network configuration (3254)
- Signing out from a non-admin account and signing in as an admin gives limited access (2862)
- Configuring multiple plug-ins may cause an error (6562)
- Assets (instances) are not getting discovered for Azure (6953)
- CloudPoint incorrectly allows snapshot operations on operating system native file systems (12285)
- Application-consistent snapshot operations for ext2 file system assets fail (12948)
- Snapshot operations might hang if CloudPoint host restarts (14757, 9039)
- Indexing may fail if snapshot is not local to the CloudPoint host (14127)
- Disk-level snapshot restore to the same location fails if an application was previously added and removed on the same disk (13196)
- Disk-level snapshot restore fails if MongoDB configuration file is at a non-default location (13130)
- Multiple simultaneous restore operations on the same AWS instance may fail (14286)
- During a policy run, a snapshot failure of one of the assets causes the other successful snapshots to be orphaned (14760)
- Classification fails if the snapshot contains encrypted files (15858)
- CloudPoint upgrade may stall if the Docker version is not 18.03 (15846)
- Classification job may fail with a partition detection error (15554)
- CloudPoint UI incorrectly displays internal storage objects (15611)
- Fixed issues
Known issues
When AWS is configured with different regions in parallel, stacks are added in the logs (7481)
CloudPoint is not able to find Google cloud network configuration (3254)
Signing out from a non-admin account and signing in as an admin gives limited access (2862)
Assets (instances) are not getting discovered for Azure (6953)
CloudPoint incorrectly allows snapshot operations on operating system native file systems (12285)
Application-consistent snapshot operations for ext2 file system assets fail (12948)
Snapshot operations might hang if CloudPoint host restarts (14757, 9039)
Indexing may fail if snapshot is not local to the CloudPoint host (14127)
Disk-level snapshot restore fails if MongoDB configuration file is at a non-default location (13130)
Multiple simultaneous restore operations on the same AWS instance may fail (14286)
Classification fails if the snapshot contains encrypted files (15858)
CloudPoint upgrade may stall if the Docker version is not 18.03 (15846)
Classification job may fail with a partition detection error (15554)
CloudPoint UI incorrectly displays internal storage objects (15611)