Who is this article for?
CrashPlan for Small Business, no.
Code42 for Enterprise, yes.
Link: Product plans and features.
This article explains how to interpret the following alert, and how to respond to the alert.
The table below displays where the alert appears and where it can be configured. The alert text is different on the configuration page than on the alerts page or email.
|"Device name & GUID has not backed up for a critically long time."|
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.
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.
- Device is not backed up, resulting in user data being placed at risk
- Problems with the CrashPlan app that prevent endpoint backup
To resolve this alert:
- Record the GUID of the affected device, as given by the notification message.
- Search in the administration console for this GUID to determine which user and device has not been backing up.
- Verify that the CrashPlan app is running on the user device, and that the device is configured properly to back up to your destination. If necessary, troubleshoot the CrashPlan app 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 administration console.
- Click Organizations.
- Select the organization associated with the device.
- Click the action menu.
- Select Edit.
- 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.