Veritas CloudPoint Release Notes

Last Published:
Product(s): CloudPoint (2.2)
Platform: Linux
  1. Getting help
    1.  
      About this document
    2.  
      CloudPoint resources
  2. Limitations
    1.  
      CloudPoint support for AWS regions and GCP zones (14446)
    2.  
      Delete snapshot operation not visible on the Recent Activity tab (3928828)
    3.  
      An error message occurs for a snapshot using a policy until the retention count is reached (3931139)
    4.  
      Limitations on replicating and restoring assets
    5.  
      If two snapshot operations are performed on an instance at the same time, the second one fails
    6.  
      You cannot delete snapshots created by an Amazon snapshot policy
    7.  
      CloudPoint cannot snapshot LUNs which are under a consistency group for Dell EMC Unity arrays (3977)
  3. Known issues
    1.  
      Azure instance image cleanup failed (7253)
    2.  
      Agent services restarting continuously (8030)
    3.  
      CloudPoint does not support 'Overwrite existing' restore option for file system and application's host-level snapshot (8924)
    4.  
      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)
    5.  
      When AWS is configured with different regions in parallel, stacks are added in the logs (7481)
    6.  
      Some errors are logged in the nginx_error.log file (6593)
    7.  
      CloudPoint is not able to find Google cloud network configuration (3254)
    8.  
      Cannot connect to the instance created by restore of a replicated host snapshot (3010)
    9.  
      Signing out from a non-admin account and signing in as an admin gives limited access (2862)
    10.  
      Issue with the CloudPoint Windows on-host agent on Google Cloud Platform (12357)
    11.  
      Configuring multiple plug-ins may cause an error (6562)
    12.  
      Assets (instances) are not getting discovered for Azure (6953)
    13.  
      CloudPoint incorrectly allows snapshot operations on operating system native file systems (12285)
    14.  
      MongoDB database application snapshot creation might fail (12286)
    15.  
      Application-consistent snapshot operations for ext2 file system assets fail (12948)
    16.  
      Indexing or classification jobs may fail in an Azure environment (13940)
    17.  
      Indexing or classification appears as completed but the actual operation may have failed (13502)
    18.  
      Snapshot operations might hang if CloudPoint host restarts (14757, 9039)
    19.  
      Indexing may fail if snapshot is not local to the CloudPoint host (14127)
    20.  
      Disk-level snapshot restore to the same location fails if an application was previously added and removed on the same disk (13196)
    21.  
      Disk-level snapshot restore fails if MongoDB configuration file is at a non-default location (13130)
    22.  
      Removing a plug-in fails to delete assets if an asset discovery is already in progress (15063)
    23.  
      Multiple simultaneous restore operations on the same AWS instance may fail (14286)
    24.  
      During a policy run, a snapshot failure of one of the assets causes the other successful snapshots to be orphaned (14760)
    25.  
      Classification job may fail with a partition detection error (15554)
    26.  
      CloudPoint UI incorrectly displays internal storage objects (15611)
  4. Fixed issues
    1.  
      Fixed issues

Indexing or classification jobs may fail in an Azure environment (13940)

This issue occurs when CloudPoint is running in an Azure cloud environment.

When multiple indexing or classification operations are run simultaneously, then one of the jobs might fail and the other jobs remain stuck in a queued state.

The following error appears in the logs:

flexsnap-coordinator: GenericError: The maximum number of data disks 
allowed to be attached to a VM of this size is 4. [src/azure/azure.py:131]

When an indexing or classification job is triggered on a disk-level snapshot, CloudPoint attaches the disk snapshot to the CloudPoint host instance to perform the operation. The disk is detached from the host after the operation is completed. This process is repeated for each indexing or classification operation.

In a case where multiple simultaneous operations are triggered, it is observed that some times CloudPoint fails to detach the snapshot disk from the CloudPoint host. As a result, the disk attach operation for the next indexing or classification job remains in a queued state and may eventually fail.

Workaround:

If you encounter such an issue, verify if there are any snapshot disks attached to the CloudPoint host instance and are currently not in use. If you see any such disks, detach them from the instance.

This will ensure that subsequent indexing or classification jobs do not fail.