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
Policy retention count is not honored for file system and application assets if there is an issue with the CloudPoint plug-in
During a policy run, if there are issues with a CloudPoint plug-in or if there are any transient errors with the application or a file system asset on a protected host, then the corresponding asset is marked with a failure message in the UI. Because of the issue, the snapshot that is created is not application-consistent and the snapshot is also not included for calculating the retention count parameter value set for the policy.
This process is repeated for every policy execution cycle. As long as the issue exists, every policy run ends up creating snapshots that are not application consistent and that do not get included in the policy retention count.
Workaround:
To resolve the issue of multiple snapshots getting created by a policy but not getting deleted as per the same policy's retention settings, you must first resolve the issue with the CloudPoint plug-in or the application on the protected host. You may also want to unassign the policy from such an asset, until the underlying issue is resolved.
Once the issue is resolved, reassign the policy to the asset.