Backup and Restore Alerts
CE00608002 MissingVMBackup
Missing VM backup.
This alert is triggered when a descriptor VMDK file has been backed up, but the corresponding flat VMDK file is missing from the backup.
No action is required.
Critical
3600 seconds
CE00610016 ObjectBackupSlaViolated
The SLA for the backup of an object is violated.
The alert can be triggered when the load on the Cohesity DataProtect as a Service is higher than anticipated, or the primary source is loaded, and the Cohesity DataProtect as a Service cannot back it up fast enough.
Verify if a new workload is recently added to the Cohesity cluster or if the primary source is throttling Cohesity APIs/calls.
Warning
CE00610006 PolicyFieldsDeprecated
The policy settings in a policy have been deprecated
The alert is raised after the Cohesity cluster is upgraded from a 4.x release to a 5.x release and the cluster detects that some policy settings used in the current policies on the cluster have been deprecated.
Open the listed policy in the Cohesity Dashboard, verify the current settings, and make any necessary adjustments. See the ALERT: CE00610006 POLICYFIELDSDEPRECATED KB article.
Warning
86400 seconds
CE00610005 ProtectedObjectFailed
The backup of an object that is part of a protection run failed with an error.
The alert is raised when the Cohesity cluster detects that an object (such as a VM) failed to be backed up during a Protection Run. One alert is raised for each object (such as a VM) that failed to be backed up. For instructions on how to enable this alert, contact Cohesity Support. A protection run can fail to back up an object for the following reasons:
- There is an issue with the primary environment, such as a removed VM or a Snapshot failure.
- The primary storage is full. (The primary storage contains the objects backed up by the Cohesity cluster.)
- The Cohesity Agent is unreachable while attempting to back up physical servers.
See the CE00610005 | BackupRestore - BackupObjectFailed KB article for a resolution.
Critical
86400 seconds
CE00610009 ProtectedObjectSlaViolated
The service level agreement violation (SLA) of an object in the protection run was violated.
The alert is triggered when the service level agreement violation (SLA) occurs for an individual object in a Protection run. A Protection run may take longer than the specified SLA for the following reasons:
- If the primary storage is slow.
- The network is slow.
- You specified SLA that is too short.
Investigate why the Protection run took longer than the specified SLA. If appropriate, adjust the time period specified in the SLA.
Warning
86400 seconds
CE00608003 VMCrackingSkipped
The VM contents are not indexed.
The alert is triggered when the Cohesity DataProtect as a Service detects 5 consecutive unsuccessful attempts to index a VM. The alert can be caused by the following conditions:
- The Cohesity DataProtect as a Service is not able to mount the VMDK.
- The VM Snapshot has an issue.
No action is required.
Warning
3600 seconds
CE00610014 VMMigrationIdentified
The VM(s) present in the vCenter have been identified to be migrated from other VCenter(s).
The alert is triggered when the Cohesity DataProtect as a Service identifies a VM in a vCenter that was earlier part of another vCenter registered on Cohesity DataProtect as a Service.
No action is required if the migrated VMs are mentioned in the alert. If not, contact Cohesity Support.
Critical
86400 seconds
CE00610021 ProtectionPolicyModified
The Protection Policy was modified by a user.
This alert is triggered when a Protection Policy is modified. The modification might include any changes apart from DataLock-related changes in the policy.
No action is required.
Informational
86400 seconds
CE00610019 PolicyDatalockChanged
Datalock settings were changed in the Protection Policy.
This alert is triggered if you enable or disable DataLock for a Protection Policy.
No action is required. Using this alert, you can validate if the DataLock was enabled or disabled by a valid user.
Informational
86400 seconds
CE00610020 PolicyDatalockDurationChanged
Datalock retention for the Protection Policy was changed.
This alert is triggered when you change the DataLock duration for a Protection Policy.
No action is required. Using this alert, you can validate if a valid user modified the DataLock configuration.
Informational
86400 seconds
CE00610017 ProtectionPolicyDeleted
A Protection Policy was deleted.
This alert is triggered when you delete a Protection Policy.
No action is required. Using this alert, you can validate if a valid user deleted the Protection Policy.
Warning
86400 seconds
CE00610023 ProtectionRunModified
A protection run was modified.
This alert is triggered when a Protection run is modified. The modification might include deleting a Protection run, enabling a legal hold, etc.
No action is required.
Informational
86400 seconds
CE00610027 ObjectDeletionRejected
A protection run was modified.
This alert is triggered when the user deletes a specific snapshot for an object instead of deleting the entire view. The deletion is rejected because the view is marked immutable, and therefore individual object deletion can not be performed.
Evaluate if the user can delete the entire view instead of individual snapshots.
Warning
3600 seconds
