Please enter search query.
Search <book_title>...
Veritas CloudPoint Release Notes
Last Published:
2019-11-28
Product(s):
CloudPoint (2.2)
Platform: Linux
- Getting help
- Limitations
- CloudPoint support for AWS regions and GCP zones (14446)
- Delete snapshot operation not visible on the Recent Activity tab (3928828)
- An error message occurs for a snapshot using a policy until the retention count is reached (3931139)
- 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)
- Cannot connect to the instance created by restore of a replicated host snapshot (3010)
- Signing out from a non-admin account and signing in as an admin gives limited access (2862)
- Issue with the CloudPoint Windows on-host agent on Google Cloud Platform (12357)
- 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)
- MongoDB database application snapshot creation might fail (12286)
- Application-consistent snapshot operations for ext2 file system assets fail (12948)
- Indexing or classification jobs may fail in an Azure environment (13940)
- Indexing or classification appears as completed but the actual operation may have failed (13502)
- 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)
- Removing a plug-in fails to delete assets if an asset discovery is already in progress (15063)
- 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 job may fail with a partition detection error (15554)
- CloudPoint UI incorrectly displays internal storage objects (15611)
- Fixed issues
Application-consistent snapshot operations for ext2 file system assets fail (12948)
If you try to create application-consistent snapshots of ext2 file system assets, either from the CloudPoint user interface (UI) or using the CloudPoint API, the snapshot operation fails.
The following errors appear in the CloudPoint log file:
ERROR - Failed to freeze filesystem: ext2 on device <device>. ERROR: fsfreeze: /ext2mnt: freeze failed: Operation not supported
While creating a snapshot, CloudPoint attempts to freeze the file system. But the fsfreeze command itself is not supported on ext2 file systems and therefore the operation fails.
Workaround:
There is no known workaround at the moment. Veritas recommends that if you wish to create application-consistent snapshots for file system assets, you use only the supported file systems such as ext3, ext4, or XFS.