Device backup critical
Instructor, no.
Incydr Professional, Enterprise, Horizon, and Gov F2, no.
Incydr Basic, Advanced, and Gov F1, yes.
Overview
This article explains how to interpret and respond to the following email alert:
"<Device name and GUID> has not backed up for a critically long time."
Priority
Low - This alert indicates a condition that should ideally be corrected, although it does not pose an immediate threat to user data, system security, or service availability.
Cause
This alert is triggered when an endpoint device has not backed up in a critically long period of time. The threshold, in days, for triggering the alert can be configured by an administrator.
The most common benign cause for this alert is that a device is powered off, often due to vacation or other absence.
Potential effects
- Device is not backed up, resulting in user data being placed at risk
- Problems with the Code42 agent that prevent endpoint backup
Recommended solution
To resolve this alert:
- Record the GUID of the affected device, as given by the notification message.
- Search in the Code42 console for this GUID to determine which user and device has not been backing up.
- Verify that the Code42 agent is running on the user device, and that the device is configured properly to back up to the Code42 cloud. If necessary, troubleshoot the Code42 agent on the endpoint device.
Alternatively, if you wish to adjust the warning threshold for receiving this alert, edit the settings for the organization associated with the device:
- Sign in to the Code42 console.
- Select Administration > Environment > Organizations.
- Select the organization associated with the device.
- Select Actions > Edit organization info.
- Select Reporting.
- If currently selected, deselect Inherited reporting settings from parent to edit the organization's settings.
- Under the Alerts section, change the value for critical alert.