Veritas CloudPoint Release Notes
- Getting help
- Known issues
- Fixed issues
During a policy run, a snapshot failure of one of the assets causes the other successful snapshots to be orphaned (14760)
This issue may occur when a CloudPoint protection policy is assigned to two or more assets. If the CloudPoint on-host plug-in that manages the asset is not online on the host when the policy is run, then the application-consistent snapshot creation for that asset might fail. If the snapshot operation for at least one of the assets in the policy fails, the policy run is marked as failed even if the snapshots for all the other remaining assets get created successfully.
As a result, the snapshots that get created successfully are no longer associated with the policy that triggered those snapshots. These snapshots are not accounted for in the snapshot retention count defined in the policy. These snapshots do not get deleted automatically during subsequent policy runs and remain in an orphaned state.
This behavior is applicable only in case of application-consistent snapshots. For host and disk-level snapshots, even if snapshot creation fails for one of the assets, the policy run is not marked as failed and the policy retention count works as intended.
There is no known workaround for this issue. You may have to troubleshoot the snapshot failure and then manually remove such orphaned policy-based snapshots from the CloudPoint configuration.